FeedWordPress works nicely — thank you!
But it quickly bloats the wp_postmeta table with “syndication_item_hash” entries — like tens of thousands/week.
How can I:
1. Reduce the number of these entries in wp_postmeta?
2. Safely remove unused/unneeded entries from wp_postmeta?
If I remove all the syndication_hash_item entries, I have to go back and re-setup the feeds (they disappear). But that does enormously reduce the db size, and speeds up performance of the site.
I am using FeedWordPress to pick up content from 4 feeds, averaging a total of 5-10 items/day.
I have exactly the same question — the amount of entries is unreal!
A. How ’bout a hint: what are the hashes used for?
B. Plan B — quit using this plugin.
I had the same issue. It caused some other key plugins to fail. Additionally the post -> post all (wp-admin/edit.php) failed to load. I was getting massive memory overload. Its a useful plugin and works wells (otherwise). In a week and a half i had 38,000 entries in the wp_postmeta (table) with the syndication_item_hash reference. After deleting these entries in phpMyAdmin and disabling FeedWordPress. All seem to go back to normal. But unless this issue is resolve i can use it.
I want to use this plug-in and it really solves a key need. Maybe i am missing something in the settings.
It’s actually quite easy to limit the number of stored hashes, but the question is: what is the point of storing all the past hashes?
I’d love to know!
The reason for storing the past hashes has to do with an attempt to avoid the kind of problem you’re seeing — an ever-growing number of post revisions being stored in the database under certain conditions. (For example, one case that came up a lot in practice was when users syndicated two aggregator feeds that sometimes carried the same items — without a backlog of previously-syndicated hashes, you could get into a more or less endless “update war” between two sources, which would cause a new revision to be stored on every update). Now it sounds like in your cases something has caused the conflict-avoidance mechanism to break down, so that it is detecting far more “updates” than it should.
I’m currently making some changes and running some tests for the next public release of FWP, and if I could track down and make sure I’ve squashed the problem that y’all are running into, I’d be happy about that. So, could you (any of you, all of you) let me know:
(1) Which version of FWP you are using that gives you this problem;
(2) Which version of WordPress you’re using it with;
(3) One or more of the URL(s) for the feed or feeds where you’re seeing the problem;
and, if you know, (4) Whether the problem seems to be happening with every post on the feed(s), or only intermittently with some posts, but not with others. (And if intermittently, let me know an example of a post where you’re seeing the problem.)
I am having the same problems which accumulated in a complete stop of the site Euro2012Twitter.com . The wp_postmeta contained 7.800.000 records!
1. FWP version 2011.1019
2. WP version 3.3.1 and since today 3.3.2 (same problem)
3. feed causing hash problems:
4. feeds NOT causing hash problems:
It looks like it’s not happening with all feeds but if a feed goes wrong it affects all post.
Hope this helps you a little.
Any progress on this? or for now does anyone have the sql to remove the postmeta hash keys that arent needed or old? I can remove all hash keys for a post but dont know what impact that has
I have deleted all those item_hash meta keys, everything is fine, all rss feed links are still keep in on list and keep updating.
How 2 fast delete all these lines?
I have over a milion of these lines.
Saved me over a million lines
- The topic ‘[Plugin: FeedWordPress] remove or limit "syndication_item_hash" entries?’ is closed to new replies.