I’ve spent most of the day fighting a WordPress install at work as it has been slow and sending various out of memory issues on a 16GB of memory VPS – so should really have enough memory to run a WordPress site. Therefore it was quite a surprise to see that 4.6 was released today for me to spend yet more time in WordPress today.
However, on this personal site, the upgrade went through smoothly with no issues (as far as I know).
Since updating to WordPress 3.0, every time I create a new post, I get an error messaging saying Page Not Found but the post is created successfully and appears in the right hand side of the screen under the recent posts. From what I can see in the forums, most people who get this message don’t get the post generated either. For me the error message shows up but the page has been created successfully.
This post will be updated as I work through the solutions – Troubleshooting consists of disabling plugins and then re-enabling them one at a time – a very time consuming process.
Typical – now I can’t reproduce the error! Seeing as though the page does actually exist I think I’m just going to not worry about it 😉
I’ve upgraded and if you are seeing this, then the process was the normal easy, couple of clicks upgrade. So far the interface looks cleaner and I’m liking the fact that finally the updates is at the top of the main dashboard menu rather than being buried in a couple of menus and not in the obvious place. It was weird that plugin upgrades were not under the upgrade option in 2.9.2
Let me know if anything isn’t working – I’ll be upgrading the other sites in the next couple of days – it will be interesting to see what is discussed at Wordcamp/Podcamp Ohio on Saturday.
I registered for PodcampOhio 3 months ago but for some reason it was not in my calendar so it’s a good job they reminded us about it on the blog.
It will be nice to take the dellmini with me next week instead of having to lug the normal laptop around. The only annoying thing is the mouse movement and smaller keyboard so I’ll have to type slower. I’m debating on loading OneNote onto the machine (restricting me to just one OS for the day or just using Onenote WebApp(but that assumes web access is always available)
If you’re going – don’t forget to say hello.
I guess I should have got my act together and submitted a session on “securely logging into your WordPress blog at conferences without needing an SSL certificate”. The most embarrassing thing is that I worked out how to do this last year before the conference and said my instructions were coming soon!
A while back I changed my twitter password – not realising how many other applications I would need to change…The first thing I had to do was go and change my tweetdeck installations which wasn’t too bad. However, this did mean changing it on three different machines.
This morning I posted a new blog post on IRL and realised that the post hadn’t made it to @helsbyhome on twitter. Checking in I realised I had to change my twitter plugins within wordpress too. These plugins haven’t been working for a couple of months now – oops!
For those of you are are interested, I’m using twitme and twitter updater with Tinyurl – any suggestions on alternatives or what do you use?
Thanks to Digging into WordPress (a blog I’ve just started reading), it’s possible to easily remove the WordPress version from the header information on a WordPress site. This (slightly) helps security in that the version of wordpress is no longer transmitted to the web browser. It would be nice if this was a toggle switch in WordPress’s admin panel though.
To implement the change, just edit the functions.php file in the Theme and add the following line.
remove_action ('wp_head', 'wp_generator');
One thing to watch is that if you upgrade your theme this change is likely to be undone. I’ve actually created a draft post in WP where I keep my theme changes listed so that they appear in the dashboard and I have a record of what changes are made to the design.
On another theme related post, I have now enabled comments on all the posts on the blog as I had issues where posts that had the enable discussion enabled were not allowing comments to be made on them. Hopefully akismet will continue to do a good job of trapping the spam. I didn’t get any help from the WordPress Support forums so this was my workaround.
My lifestream plugin in WordPress that keeps track of most of my social networking sites suddenly stopped working a few days ago and I was not sure how to kick start it back into action again. It turns out that disabling the plugin and then re-enabling the plugin adds the relevant jobs back into the wpcron system. My Lifestream (that appears on Absoblogginlutely! – IRL is now being updated correctly (and also shows my geocaching finds now too).
In common with a lot of bloggers today I upgraded my blogs to WordPress 2.8. Thankfully I didnt have any problems upgrading any of them. So far in the few minutes that I’ve used WordPress I’ve not actually noticed anything new or drastically different.
I was asked in the comments why I migrated from MovableType to WordPress. There were several reason why I decided to make the switch. The primary reason was the incredibly long time it would take to publish a post in MT. I could actually hit Post in MT, fire up a new web page, connect to my testing WP site, create a new post, enter the title, paste the content in, hit publish and then view the website. In the meantime MT would still be thinking about saving the original post.
The time taken to republish the site after a change such as a design change was so great that some of my older posts still had old styles as the republishing system would time out before it could complete the task.
One of the other things I really like about WordPress is the ease of upgrading the software to the latest version. Yes, WordPress has had more releases, but when it takes about 2 minutes to upgrade the system its really not a problem (especially now that there is an automatic upgrade function). MovableType has also just released a new security release which is one of the reasons why I made the switch *now*.
I was also hoping that the spam filtering would be better on WordPress than MovableType. I’ve had several idiots spamming the blog with russian comments in MovableType – they wouldn’t get through but I would have to go and delete them. In the one day that I’ve had WordPress up I think I’ve had more spam comments get through to the spam queue, but again it was easy to delete them all – a “select all” option and then delete, followed by an “all done” about 3 seconds later.
Themes in WordPress seem to be a lot cleaner and there are a lot more themes out there to pick from – MT’s selection was pretty small. This wasn’t that much of an issue to me as I was pretty pleased with my existing theme in MT (and have had it copied by a few people so it couldn’t have been that bad!)
The big concern about switching from MT to WP is typically due to the fact that WP is database driven and therefore doesn’t have any of the pages (by default) saved on the machine so if the database is down, then so is the website. This site doesn’t have that many visitors so I don’t see this as being that much of a problem and normally if the sql database is down, then its probably likely that the web server is going to be down too.
I’ve not looked at the various caching plugins as I doubt I’m going to need it, but it is nice to know this option is available. I may switch it on later once I’ve got the site up and running and I’m not making many design changes to it.
For those of you interested, I will also be posting my experience about the upgrade and some hints and tips – the existing WordPress migration documentation is in dire need of being updated!
I was hoping to get the switch from MovableType to WordPress up and running for the 1st of January but I didn’t want to go live until I was ready and near a keyboard in case there was problem. I’ve spent several hours this weekend getting the layout and stuff ok to go live. For those of you using feed readers to see this, you probably won’t see much difference although I have added a few options to the feedburner feeds and also include my delicious saves now. Do stop by the main website and let me know what you think though. Any issues then let me know, most of the work and testing was done with firefox as that is what most of you use. There are a few cosmetic issues with internet explorer that I’ll work on over the next week or so.
I’ll also be posting some hints and tips on the migration steps too.