423 reputation
311
bio website
location
age
visits member for 3 years, 1 month
seen Dec 3 at 20:03

Dec
11
awarded  Popular Question
Dec
3
comment wp_insert_post not returning post ID?
FYI, the solution to our particular problem was: eddiemoya.com/plugins/incorrect-datetime-bug-fix-wordpress
Dec
3
comment wp_insert_post not returning post ID?
I'm having a similar problem - wish this weren't closed back in the day. Ours is giving errors (a warning, technically) when we try to create a new post in the admin interface. The warning can be traced back to this issue - I'm thinking it's a problem in our database somewhere... The warning message is: Warning: Creating default object from empty value in /home/xxx/public_html/wp-admin/includes/post.php on line 475
Nov
4
revised Why does dbDelta() not catch MysqlErrors?
added 121 characters in body
Nov
3
comment Why does dbDelta() not catch MysqlErrors?
Note that while this works, it only solves part of the problem. Once I implemented this core hack, another similar issue cropped up in Wordpress' blog setup code. Once I fixed that, another one cropped up. I wonder how deep this rabbit hole goes... Perhaps I can revisit this later...
Nov
3
revised Why does dbDelta() not catch MysqlErrors?
added 113 characters in body
Nov
3
accepted Why does dbDelta() not catch MysqlErrors?
Nov
3
answered Why does dbDelta() not catch MysqlErrors?
Nov
3
comment Why does dbDelta() not catch MysqlErrors?
I luckily chanced upon this SO question via a Google search and logged in to up vote because this seems to be my exact same problem. But SO won't let me upvote the question... Turns out this is my question, which I wrote 6 months ago. :P
Oct
13
awarded  Notable Question
Sep
17
awarded  Yearling
Jul
2
awarded  Curious
Apr
22
comment Why does dbDelta() not catch MysqlErrors?
Either way, sounds like a patch might be in order! :P
Apr
21
comment Why does dbDelta() not catch MysqlErrors?
Thanks for your answer! Unfortunately, the issue isn't related to errors showing or not showing. Rather, the issue is that Wordpress is not catching the related database error (regardless of whether or not it is displayed to the end user). Put succinctly, Wordpress is generating errors that appear in our error log that are not really true errors. They are (I assume), side-effects of a correctly functioning dbDelta() function. This causes our reporting systems to inaccurately conclude that there are issues with our production environment, since it is consistently generating errors.
Apr
21
asked Why does dbDelta() not catch MysqlErrors?
Apr
17
comment Detecting errors generated by $wpdb->get_results()
I suppose I could always do something nasty with intercepting the output buffer... :/
Apr
17
answered Detecting errors generated by $wpdb->get_results()
Apr
17
asked Detecting errors generated by $wpdb->get_results()
Mar
14
comment Why are simple updates to wp_postmeta's “_edit_lock” so slow?
(aka, perhaps, like you suggest, throwing more resources at the issue IS the source of the problem itself...)
Mar
14
comment Why are simple updates to wp_postmeta's “_edit_lock” so slow?
Hmm... Could be. That bug is a duplicate of bugs.mysql.com/bug.php?id=21074, which appears to be closed and included in version 5.1.23. We are running 5.1.73. :/ Regardless, it's still worth a shot - I suppose I can experiment with different cache/buffer sizes to see if there is an apparent connection. Either way, this issue certainly isn't grinding our system to a halt; it's more of a yellow flag. Perhaps the fact that this is coming up is due to our overabundance of resources and eagerness with slow query hunting and elimination... ? Still, something odd is definitely going on.