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)..

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:

Update 2011/02/05: ASO is no longer my host. As this article explains, ASO service was great at the start, but after three years quality of service has declined considerably. There are some great people at ASO, but I can no longer recommend them for serious web hosting. For more information, check out my post on switching to Media Temple.</update>

• 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 Reading

Welcome to the Perishable Press Redirection Lounge!

What?

We keep a very close eye on all 404 (resource not found) errors. Every time a legitimate 404 rears its ugly head, we take the necessary steps to solve the issue. In most cases, we use htaccess redirects to prevent 404 errors. Often, the missing resource remains available, but has been moved to another location. In this situation, we simply redirect visitors to the new location. Easy. However, there are also a relatively small number of 404 errors that are generated due to content that is no longer available. For example, temporary posts, test posts, and duplicate posts often result in 404 errors, even if they were only online for a very short time. So, rather than redirecting such requests to the home page or to the 404 page, we have created an exclusive Redirection Lounge at which roaming search engines, misguided robots, and wandering visitors may find information and reassurance.

Where?

This page is actually a post handcrafted especially for this very moment in time. The post is public, exists online, and is archived at Perishable Press. In other words, you are currently deep within the Perishable Press Archives. To escape such ancient realms, click here to return to the Perishable Press home page. Otherwise, click on some other link to fight your way out of the archive database. Otherwise, enjoy your stay here at the Perishable Press Redirection Lounge. It may not be exactly what you originally had in mind, but you have to admit, the solitude provides plenty of time to think about that interesting life of yours.

Why?

You are here because you tried accessing a resource at perishablepress.com that is no longer available. Please note that the content you are seeking has not been relocated, misplaced, or renamed — it is simply no longer available on this domain. Most likely, the content has been deleted permanently. If you are absolutely convinced that the content you are seeking is worth pursuing, please check out the Google index or the excellent Wayback Machine. Indeed, if the requested content were still available on this domain (perishablepress.com), our diligent web gimps would have redirected you swiftly to the new location of the resource. However, as the requested resource is not available, and because we try to avoid as many 404 errors as possible, we have created this Redirection Lounge to serve as our official redirect target for otherwise dead-end requests. We hope you find it as comfortable as it is informative.

Huh?

If you feel that you have arrived at the Redirection Lounge in error, or have information concerning the requested resource, please use our official contact form to drop us a line.

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..)

This is top-secret. And for “eyes only”..

Alright, so it was just a test. Password protection removed in December of 2009 because it is no longer needed. Nothing here anyway.

PayPal is too automated. The phone service is automated, slow, and worthless. Plus, the number for help is not toll-free — I had to pay for PayPal’s auto-garbage phone system. Plus, the email support is automated, slow, unresponsive, and also worthless. I received a worthless auto-reply to several very specific questions regarding my account security. Security is too important to be so disregarded by PayPal, especially with one’s financial integrity at stake. PayPal is losing the technology race with its poor record-keeping and customer-service performance. I will go elsewhere for the service once provided by PayPal. PayPal is no longer relevant, responsive, or worthwhile.

Keyword Yo

What are these trackbacks?

Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Duis ligula lorem, consequat eget, tristique nec, auctor quis, purus. Vivamus ut sem. Fusce aliquam nunc vitae purus. Aenean viverra malesuada libero. Fusce ac quam. Donec neque. Nunc venenatis enim nec quam. Cras faucibus, justo vel accumsan aliquam, tellus dui fringilla quam, in condimentum augue lorem non tellus. Pellentesque id arcu non sem placerat iaculis. Curabitur posuere, pede vitae lacinia accumsan, enim nibh elementum orci, ut volutpat eros sapien nec sapien. Suspendisse neque arcu, ultrices commodo, pellentesque sit amet, ultricies ut, ipsum. Mauris et eros eget erat dapibus mollis. Mauris laoreet posuere odio. Nam ipsum ligula, ullamcorper eu, fringilla at, lacinia ut, augue. Nullam nunc.

Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Duis ligula lorem, consequat eget, tristique nec, auctor quis, purus. Vivamus ut sem. Fusce aliquam nunc vitae purus. Aenean viverra malesuada libero. Fusce ac quam. Donec neque. Nunc venenatis enim nec quam. Cras faucibus, justo vel accumsan aliquam, tellus dui fringilla quam, in condimentum augue lorem non tellus. Pellentesque id arcu non sem placerat iaculis. Curabitur posuere, pede vitae lacinia accumsan, enim nibh elementum orci, ut volutpat eros sapien nec sapien. Suspendisse neque arcu, ultrices commodo, pellentesque sit amet, ultricies ut, ipsum. Mauris et eros eget erat dapibus mollis. Mauris laoreet posuere odio. Nam ipsum ligula, ullamcorper eu, fringilla at, lacinia ut, augue. Nullam nunc.

Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Duis ligula lorem, consequat eget, tristique nec, auctor quis, purus. Vivamus ut sem. Fusce aliquam nunc vitae purus. Aenean viverra malesuada libero. Fusce ac quam. Donec neque. Nunc venenatis enim nec quam. Cras faucibus, justo vel accumsan aliquam, tellus dui fringilla quam, in condimentum augue lorem non tellus. Pellentesque id arcu non sem placerat iaculis. Curabitur posuere, pede vitae lacinia accumsan, enim nibh elementum orci, ut volutpat eros sapien nec sapien. Suspendisse neque arcu, ultrices commodo, pellentesque sit amet, ultricies ut, ipsum. Mauris et eros eget erat dapibus mollis. Mauris laoreet posuere odio. Nam ipsum ligula, ullamcorper eu, fringilla at, lacinia ut, augue. Nullam nunc.