bad post checking
Reported by Thomas Phipps | December 15th, 2008 @ 07:42 PM
while doing the return 0; fix for the duplicates issue, came across another issue.
the insertPost function isn't doing any error checking on the return of postid. to make sure that it didn't return false or null. when the return 0; fix is in place it returns 0 for all duplicate posts. wp-o-matic then inserts all the postmeta data for that post with a postid of 0. which in turn causes "custom fields" to be inserted into the postid of 0. after awhile these will add up causing the new post page to stop loading because of thousands of custom fields having to be loaded for each post.
Comments and changes to this ticket
-
Guillermo Rauch December 15th, 2008 @ 07:46 PM
Thanks for reporting. This is fixed in the current beta.
Thanks for reporting. This is fixed in the current beta.
-
Ricardo Rauch April 15th, 2010 @ 08:50 AM
- Assigned user changed from “Guillermo Rauch” to “Ricardo Rauch”
-
otis December 13th, 2022 @ 10:20 PM
Brand among us new compilation from Bokeh Versions ft. a new track from Bad Tracking! The compilation features a whole heap of amazing artists
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
WP-o-Matic project.
Guillermo Rauch