Perishable Press

Testing new Stealth-Post plugin.. this post should not appear on the front page or in feeds..

Testing..

[ Please ignore this post ]

Just a note to announce a site upgrade to WordPress 2.3.3. The upgrade went well, but overall server performance continues to suffer. I am aware that some people are experiencing difficulties leaving comments and even accessing the site in general. Rest assured, I am working with my hosting company, A Small Orange, to get everything back on track and running smooth. In the meantime, I appreciate your patience as we work to resolve the issues, restore full functionality, and return to reliable performance.

Please share any helpful observations regarding the site here. — Thanks!

Hello! If you are seeing this page via the default WordPress theme (i.e., blue header, based on Kubrick), welcome to the new server! I recently upgraded my hosting to a virtual private server, and finally reassigned the domain name servers to resolve to the new address. So, if you are here and everything seems to be working, then everything went according to plan and I will be able to complete the transfer on Saturday (Lord willing). If, on the other hand, something is busted, throwing an error, or otherwise causing problems, then Saturday may involve more troubleshooting and fixing things.. Either way, if you are reading this, welcome! There are great things in store here at our new home ;)

Hello!

As many of you already know, the popular WordPress anti-spam plugin, Bad Behavior, caused some problems yesterday, and as a result many bloggers and users were locked out of their favorite sites, including this one. As for now, the problem seems to be fixed, however, the experience of being locked out of my own site has left a rather unpleasant taste in my mouth.

Needless to say, I will be reconsidering the continued use of Bad Behavior as a part of my long-term anti-spam strategy. In the meantime, everything is up and running fine again (with Bad Behavior disabled) — comments are working, and I can even log in to admin to write new posts :)

In other news, Perishable Press is moving to a new server! I just switched the DNS to my new VPS nameservers, so hopefully everything will propagate and transfer without a hitch. Nonetheless, if something does happen to go wrong, Perishable Press may be offline for a spell, but rest assured, I am all over it..

So — here goes nothing — I am pulling the plug on the old server — see you on the other side ;)

Just a note to let everyone know that Perishable Press will be undergoing site maintenance for the next several hours. I apologize in advance for any inconvenience this might cause. Thanks for your patience ;)

TEST POST: Plenty of challenges around here as Perishable Press is upgraded from the stone age (WP 2.0) to the modern era (WP 2.3).. Stay tuned, and ignore this post (I am really trying to avoid having to nuke and rebuild my Feedburner feed, but I may have no choice)..

[ Keywords: shared, hosting, small, orange, asmallorange, aso, cpanel, whm, server, host, excellent ]

Perishable Press switched to A Small Orange [ASO] in March of 2007. At the time, I was looking for highly recommended shared hosting with several key features:

• Solid customer service and extremely reliable server uptime
• Unlimited domains with plenty of disk space and bandwidth
• Unlimited Email accounts, MySQL databases and everything else

A Small Orange delivers all of the above in every shared hosting plan. ASO provides hosting plans perfect for any size operation:

Continue

Welcome to the Perishable Press Redirection Lounge!

Continue

This post exists entirely for the sake of tweaking time functionality in Apache, PHP, SQL, and WordPress..

Immediate findings:

• Date/time limit into the past for WordPress: December 13, 1901 @ 15:45
• WordPress will display December 13, 1901 @ 15:45 properly for all functions except wp_get_archives
• All dates prior to 12/13/1901 in MySQL will display as December 31, 1969 @ 19:00 in the WP Admin > Post Timestamp panel
• SQL timestamps of 0000-00-00 00:00:00 display as 0 via $wpdb->get_col("SELECT DISTINCT YEAR
• SQL timestamps of 0000-00-00 00:00:00 display link as the current year when permalinks are enabled
• An SQL timestamp of 1000-00-00 00:00:00 displays link as "1000" and links to the post
• An SQL timestamp of 1000-00-00 00:00:00 displays correctly in archive view, but incorrectly in Admin and post view
• An SQL timestamp of 1950-00-00 00:00:00 displays as November 30, 1949 @ 00:00 in WP Admin Post Timestamp panel and elsewhere in WordPress
• An SQL timestamp of 1950-01-01 01:01:01 displays properly in WP Admin, and elsewhere
• 0001-01-01 01:01:01 displays as January 01, 2001 @ 01:01 in Admin, links to "1" in archives (404 error)
• 1000-01-01 01:01:01 displays correctly in archive, as December 31, 1969 @ 15:59 in Admin and post view
• 3000-01-01 01:01:01 displays correctly in archive, as December 31, 1969 @ 15:59 in Admin, and 404 as post view
• 2050-01-01 01:01:01 displays correctly in archive, as December 31, 1969 @ 15:59 in Admin, and 404 as post view
• January 19, 2038 3:14:08 AM GMT is the latest date that will appear correctly in the WP Admin
• No posts with future date will appear in post view
• An SQL timestamp of 1900-01-01 01:01:01 displays correctly in daily, monthly, and yearly archive views
• An SQL timestamp of 1900-01-01 01:01:01 now displays January 18, 2038 @ 19:14 in Admin
• My head hurts..

More to come.. (much, much later..)