Soeben wurde ich gleich etwas nervös, da ich weder das Backend zu diesem WordPress Blog, noch den Blog selber laden konnte. Unter beiden Webadressen erhielt ich eine rudimentäre Seite mit der Nachricht “Briefly unavailable for scheduled maintenance”. Dies passierte, nachdem ich automatisiert, respektive im Admin-Interface einige Plug-Ins aktualisierte. Mein erster Gedanke: Jetzt ging was schief, hoffentlich sind nicht alle Inhalte verloren…
Glücklicherweise fand ich im Internet gleich hier die Lösung:
Man muss einfach kurz per FTP auf den Webserver zugreifen und ins Verzeichnis der WordPress Installation gehen.
Dort findet man eine Datei namens “.maintenance”, die man einfach umbenennen oder löschen kann.
And I’ve just installed it here and will be testing things, before it goes into action on my main page and blog for my wedding photographer existance;-)
What’s new? Well easiest is, if you quickly check the wordpress.org anouncement. Overall, it seems like news this time are more along the line of admin functions and new CMS-like functionalities. For example a cool bar on top of your blog when logged in allows direct access to most admin and editor functions.
I will check out things in the comming 1-2 weeks and then start using whatever I need.
WordPress 3.0 is out and according to the wordpress.org blog, it’s the 13th major release. Quite an achievement, congratualtions to all the developers and Matt Mullenweg, the founder of what I would call THE blogging platform per se.
I’ve been talking about some new features previously and will cover some in more detail later. Key are the merge with the multi-user MU version of wordpress, new menu system and the improved media handling. And more notably by most users will be the new default theme and a whole lot of more theme function that well slowly be adapted into various themes offered for free and commercially out there.
I’ve encountered issues with WordPress missing scheduled posts and not sending them online on various photography related websites that I run or am involved with. The ‘Missing Schedule’ issue is not unknown and mistakingly sometimes called a bug of WordPress. Various solutions have been proposed and I’ve discussed them here, to some extent.
As many others, I struggled quite a bit in understanding what’s behind and how to best handle it. Initially, when contacting the support of one of my webhosters, I got the answer that they cannot help with application specific issues, which is a very typical, but understandable. But I finally got his attention when I told them that it’s all running smoothly on hosting accounts with two of his main competitors. And we found the cause:
It’s a server-side setting issue. Overly secure server settings might prevent WordPress from accessing it’s own cron-like functions. WordPress needs to call back to itself and on this particular webhoster (not the one running this blog here) mod_secure was loaded with PHP. After deactivating it, it all worked fine. If you can’t get your hoster to change this, you probably have to go the define(‘ALTERNATE_WP_CRON’, true); way, described in my previous post.