A Simple Mistake Could Cause You Priceless Headaches

Comments

1. Athul Jayaram (2 comments.) says:

   1/9/2010 at 4:48 am

   Ohhh, So you got big Db because of your bit.ly api plugin customization.

   Dude test & research your plugins not your main site, like create a testing place somewhere, so if something weird happens doesn’t affects your techie-buzz

   I too was looking for plugin to automatically make short urls for each post & make it available below posts by php call function

   Dude share me that plugin. I prefer stumble upon links
2. Len (24 comments.) says:

   1/9/2010 at 5:05 am

   Holy crap on a cracker! 10 million rows?
3. Daniel (3 comments.) says:

   1/9/2010 at 5:21 am

   One more tip: define('WP_DEBUG', true); should be the best developer’s friend
   • Milan Petrovic (31 comments.) says:

     1/9/2010 at 6:13 am

     Yes, for development environment WordPress should always be in debug mode and with that you can clean up all minor warning and most important avoid all kinds of big errors that are not easy to spot.
   • Dave Doolin (25 comments.) says:

     1/9/2010 at 12:02 pm

     Good idea, you have reminded me to do that on my localhost installation.
4. Roseli A. Bakar (4 comments.) says:

   1/9/2010 at 6:37 am

   Thank you for posting this. Though I have never encounter this, it will make me more careful in the future.
5. scribu (42 comments.) says:

   1/9/2010 at 10:24 am

   I’ve opened a ticket to prevent WordPress from inserting rows into wp_postmeta if post_id is 0.
6. Inside the Webb (1 comments.) says:

   1/9/2010 at 4:56 pm

   This is a very interesting article. I’ve never run into this problem, but I still find it a great article and a really informative post. Thanks!
7. Mike says:

   1/9/2010 at 6:43 pm

   Isn’t that the purpose of the $unique parameter in add_post_meta? Set it to true and it won’t add a new key or over-write the old one. The function returns false in that case so you know to use update_post_meta.

   A post_id of 0 is perfectly valid and a logical way of storing default post meta values – the code that reads meta data will automatically get those default values when a new post is created (where a plug-in provides custom editing on the post editor).

   If WP removed the ability to use post_id=0 I’d open a ticket to report a bug.
8. tom-g (2 comments.) says:

   1/10/2010 at 1:14 pm

   WOW i guess it is the little thing that can become BIG problems. I am not a techie but I can see this bringing down a site.

Trackbacks/Pingbacks

1. Best Of WLTC 2010 – Part 1 « Weblog Tools Collection says:

   12/30/2010 at 3:01 pm

   […] A Simple Mistake Could Cause You Priceless Headaches […]