petercasier

If you use the latest version of FWP, it might be related to this reported bug.

@3×7: Thanks for your suggestion, but the “remove posts from this feed also” option, and the existing mass-delete plugins are too slow to execute (Over the past years, I racked up over 100,000 posts). Both hit the timeouts of my server (which are already set at very high values), and take ages to delete just 1000 posts.

Experimenting on a test database with the above script, shows a delete of 350,000 posts is done in 120 seconds. But I am not sure if it does not leave any garbage in the database…. That is really the question…

After quite a bit of debugging, it seems the MySQLserver was very busy
and gave timeouts when FWP was aggregating posts.

The strange thing is that the posts themselves are stored correctly, but there is no metadata for it.

@radgeek: would it be reasonable to suggest FWP does an error check, and when an error occurs when aggregating the post, the post itself is not stored at all, rather than stored “incorrectly”? i.e. do an error check if the metadata for the post is stored correctly?

Try https://feedvalidator.org/check.cgi to check the validity of your feed. Sometimes feeds contain posts which are not fully standard compliant.
If indeed the error is in a post, then, as the post is flushed from the feed -over time-, the error won’t continue. If the error is in the feed’s header, your problem might continue…

…If it can help, I enabled the debug to see the post metadata in “Edit Post”.

For a syndicated post, wrongly defined as “created locally”, I get the following:

ID: 	2645602886
GUID: 	https://allafrica.com/stories/201212240538.html
Custom Fields
_edit_lock: 1356443240:1

For a syndicated post, correctly stored, this is the metadata

ID: 	2645602884
GUID: 	https://www.voanews.com/content/india-prime-minister-appeals-calm/1570710.html
Custom Fields
enclosure: https://gdb.voanews.eu/9C7CA086-ED65-4407-9EFA-D4D1FDBFB764_cx0_cy0_cw0_w800_r1.jpg?nocache=1
3123
image/jpeg
syndication_source: aidnews
syndication_source_uri: https://pipes.yahoo.com/pipes/pipe.info?_id=4e203c7a0de5d4476986c85747776c83
syndication_source_id: https://pipes.yahoo.com/pipes/pipe.run?_id=4e203c7a0de5d4476986c85747776c83&_render=rss
syndication_feed: https://pipes.yahoo.com/pipes/pipe.run?_id=4e203c7a0de5d4476986c85747776c83&_render=rss
syndication_feed_id: 8
syndication_permalink: https://www.voanews.com/content/india-prime-minister-appeals-calm/1570710.html
syndication_item_hash: 76f905b2618d311ef4e78a2ed6f204a3
_edit_lock: 1356443408:1

So it looks like the metadata for the wrongly syndicated post, is not written (or not the write was not completed)

Any help on where to look what the problem is? PHP timeout for write operations?

.. and BTW: I have the same problem on several sites, all running on the same server: FastCGI, PHP Version 5.3.2, MySQL version 5.0.96 – (Hostgator VPS server)…

Peter

My feeds show up correctly, but there is something wrong in the “Syndication” screen: i can unsubscribe from a feed, operation is successfull, but the feed still shows up on the “Syndication” screen.

I have WP 3.3 running with FeedWordPress 2011.1019 – and all runs fine…

Agreed with ilyar126 – The FWP add-on plugin “Add attribution” can be used for an easy way to add a link to the original source at the end of every post.

My boiler plate setting: insert “After” the “Content”:
<a href="[original-url]" target="_blank">Read the original article...</a>

Works fine with the “Sociable” plugin.

See the single posts for this aggregator blog: https://aidnews.org

BUT, I had to hard-code the code needed into the template (single.php for my theme).

Peter

upgraded to WordPress 3.1.1 and SuperCache 0.9.9, but the problem persists…

Mmmm.. this error keeps on popping up. Any idea why this happens?

Peter

Hi.. running PHP 5.3.2

I think if there is any HTML error in the doc read in /plugins/wp-mobile-detector/functions.php on line 213, then there is a PHP warning generated.

The mobile plugin actually works beautifully, except for the nuissance of the error_log file getting filled with PHP warnings (which is a nuissance and slows down things when there is a lot of mobile access).

tnx for looking into this.

Would not be able to help you with the super-cache / wp-cache question… Donncha might answer that…

Welcome! Peter

James,

I looked at the site. It seems all pages I visited are cached, and load pretty fast.

Do you have the option “Don’t cache pages for known users” on? If so, you need to log out to test the cache. But even so, I think that it remembers that you have been logged in (or left a comment) before (maybe through a cookie).
What I do, is I have another browser (I develop in Firefox, and test in Chrome) I use to test the cache. A browser I never use to log in or comment (and which I specifically use to test .

Try that again with another browser.

Peter