WP 2.1 – Postmeta fields being deleted after comment is added

volleyballmaniac
(@volleyballmaniac)

17 years, 3 months ago

Just upgraded to 2.1 and been doing some testing.

I use Postmeta fields extensively on my blog, so I was pretty flustered when I found that when I added a new comment to a post, ALL of the Postmeta fields were being deleted.

I checked the DB PostMeta Table, and discovered that yes, all PostMeta entries in relation to that Post ID had been dropped from the database.

1. Make a comment
2. Approve comment for posting on site
3. Check your Postmeta fields (and discover they are all gone).
4. Check the DB Postmeta Table, and find that all rows for that PostID have been been dropped.

AAAARGH!

Further info: I upgraded from 2.0.7
I’m running on Dreamhost, using PHP 5.1 (Im pretty sure), and MYSQL 5.0.

Viewing 8 replies - 1 through 8 (of 8 total)

Xander
(@xander)

17 years, 3 months ago

I have the same problem to a tee. My host is running PHP version 4.4.4 and MySQL version 4.1.21. I have many plugins in use, but these are some of the more relevant ones: get custom field values, rc:custom_field_gui, related posts, post updated,

Currently I have already lost some very valuable information that will be a pain to research and replace… consequently I need to disable comments entirely. Hopefully a solution can be found soon enough.

Mark Jaquith
(@markjaquith)

17 years, 3 months ago

I was not able to reproduce this. I added a postmeta field to a post, and then tried commenting as a logged in user, as a regular visitor, and as a regular visitor with comment moderation on (which was subsequently approved). Nothing made the postmeta disappear.

I would guess that this is a plugin issue. You two should see which plugins you have in common so we can narrow it down!

Mark Jaquith
(@markjaquith)

17 years, 3 months ago

Okay, I figured out what’s going on. Bottom line is that many plugins aren’t verifying user capabilities and intention when running edit_post actions. I’ll be posting an article on the issue and how plugin authors can fix it.

Mark Jaquith
(@markjaquith)

17 years, 3 months ago

Plugin authors, check out this post.

Plugin users, you may want to consider deactivating the offending plugins until the plugin authors have had time to release updated versions. Monitor their sites.

Joshua Sigar
(@alphaoide)

17 years, 2 months ago

If you’re using rc:custom_field_gui, please upgrade to latest version.
http://rhymedcode.net/?dl=rc-custom-field-gui-1.4.zip

If you’re using rc:custom_comment_text, please upgrade to latest version.
http://rhymedcode.net/?dl=rc-custom-comment-text-1.1.zip

Xander
(@xander)

17 years, 2 months ago

The rc:custom_field_gui upgrade seems to have fixed my issue! Thanks!

Moderator Samuel Wood (Otto)
(@otto42)

WordPress.org Admin

17 years, 2 months ago

Ultimate Tag Warrior had this same problem as well. Make sure to upgrade to the latest version with the fix.

Sudar Muthu
(@sudar)

17 years, 2 months ago

Bunny’s Technorati Tag plugin also had the same problem and a fix is available here

Thanks Mark for the post explaining the actual problem and also the fix.