Since I wrote this post (a long, long time ago) – Office 365 now adds support for creating a trusted connector between your Linux/postfix environment and Office 365.
Much, much easier than before.
So as a reminder for me next time:
SASL for username/password
- Postfix main.cf settings
- Set up Office 365 connector and trusted IP end point
Updated to WordPress 3.4. Seven years since I started using WordPress. Time flies.
Strictly a console guy – I’ve been struggling to get the big blog database dumps up to the new hosting. phpMyAdmin claims to support zipped dumps – but that doesn’t work. There are also timeouts in the console for the upload and import.
I finally fixed it by using scp to move the non-compressed dump to the hosting server; and then using the Hosting Control Center to restore the dump as if it was a backup.
It’s running right now – so hopefully I’ll have happy blogs again soon.
Way back in the not-so-distant past the only way to update WordPress was to download (wget/ftp) updates, plugins and themes, unpack them and perform the update/install.
It is possible to pull the latest builds from subversion – but that’s really focused on the core hacker.
New in WP 2.7 was the ability to update automatically.
There were a few challenges with this – permissions, PHP modules, various host implementations – but I found it generally quite successful.
I found a great FAQ here – http://dd32.id.au/2009/02/20/wordpress-filesystem-abstraction-faq/
From the same author is a very cool plugin – core-control – it lets you enable and disable various transports – and shows the status of them.
WordPress 2.6 is live; I just updated from 2.6 RC1 to 2.6 live here.
Download from http://wordpress.org/download/
- post differencing
- support for Google Gears
There’s an offical blog post about it here: http://wordpress.org/development/2008/07/wordpress-26-tyner/ – with a great video overview.
Works well so far.