Bug-fix version 2.6.1 of WordPress has been released. it’s been a while since I’ve seen a release announcement say “You need not upgrade to 2.6.1 if 2.6 is getting the job done.”
Recent Comments
- Paged Comments, Friend or Foe? Usability vs SEO | BestBlogBuzz on Paged Comments and the SEO Problem: A Solution
- 大陸志 » WordPress SEO教程-5: 20個最佳WordPress SEO插件 on Paged Comments and the SEO Problem: A Solution
- Disha Hosting » SEO Plugins for Wordpress on Paged Comments and the SEO Problem: A Solution
- 15个有用的Wordpress SEO插件 : 心情日记 on Paged Comments and the SEO Problem: A Solution
- Probort.net on Paged Comments and the SEO Problem: A Solution
-
RSS Subscription Feeds
One Comment
Well, it introduced a bug with the backup-plugin that you made (I think). It doesn’t seem to send any scheduled backups to my e-mail address any more. This started – or rather stopped – after an upgrade to 2.6.1. Maybe it has to do with an error I receive with a manual backup, that seems to reveal some dodgy thing in WordPress.
Here it is:
Backup complete, sending backup via email…
The following errors were reported: date() [function.date]: It is not safe to rely on the system’s timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected ‘Europe/Berlin’ for ‘CEST/2.0/DST’ instead