tristaanogre

To answer the questions, scroll up to my previous post.

We have over 50 feeds we’re bringing in to our website and we’re doing duplicate checking on them all. It seems that there’s a performance problem somewhere that, when a feed is taking a long time to update AND do duplicate checking, if another feed tries to do so at the same time, it fails the duplicate checks. It sounds like a table lock on the SQL database with regards to the queries for duplicate checking.

So, I changed some settings to see if I could correct the timing:

1) I changed the “Updates” to check before page loads instead of after.
2) I set a time limit on updates to 30 seconds. If it takes longer than 30 seconds to update a feed, then something else is going on and we’ll skip and come back later.
3) I set the fetch timeout to 10 seconds. Again, this fetch should be pretty quick. If it’s not, move on.

Using the 2015 version and changing the settings as noted, I’ve resolved the duplicate posts. As the originator of this thread, I marked it as resolved because, for me, at least for now, it is resolved. I have heard bupkis from the developer on an actual code resolution so I’ve pretty much written that off for now…

If you are still having problems, I’d suggest you open another thread and document your problems. At this time, it’s no longer an issue for me.

OK… I think I resolved it on my own… however, I think it is still a problem in the plugin.

We have over 50 feeds we’re bringing in to our website and we’re doing duplicate checking on them all. It seems that there’s a performance problem somewhere that, when a feed is taking a long time to update AND do duplicate checking, if another feed tries to do so at the same time, it fails the duplicate checks. It sounds like a table lock on the SQL database with regards to the queries for duplicate checking.

So, I changed some settings to see if I could correct the timing:

1) I changed the “Updates” to check before page loads instead of after.
2) I set a time limit on updates to 30 seconds. If it takes longer than 30 seconds to update a feed, then something else is going on and we’ll skip and come back later.
3) I set the fetch timeout to 10 seconds. Again, this fetch should be pretty quick. If it’s not, move on.

This combination has pretty much done away with our duplicate posts. As mentioned, I THINK there still is a problem with the SQL queries where something is locking something else but, for now, I’m happy.

Bump… I see there’s a new version out… has this been addressed?

We’re using CyberSyn right now. It’s about on the level of FeedWordPress but not as robust in some of the features. It’ll do…

We replaced our plugin with a different one so, no, haven’t figured it out yet. I’m hoping that, perhaps, the FeedWordPress developer wakes up and corrects the problem.

Actually, I beg to differ.

The plugin FeedWordPress (which we replaced with CyberSyn) does it…but I’m not a good enough PHP coder to find the code that does it… otherwise, I’d do it myself. So… not impossible… Consider it a challenge, then. ??

BTW, I am using the option for Link to Source and I’m using the ####post_link#### information in the footer. But what I would like is for the actual post permalink to point to the same location as ####post_link#### so that even e-mail subscribers can be redirected to the proper source