I have just installed WordPress 2.9.1 RC (release candidate) as I want to continue scheduling posts, and it was also an opportunity to try out the WordPress Beta Tester plugin.
The database was backed up first (though the automatic e-mailing of this every three days isn’t yet working, I’ve noticed), and I’ll schedule the next post for a few minutes in advance to check if the issues I was previously encountering have been vanquished. I also need to find the information on resetting file ownerships in Windows 7, as I can now access Anna’s pictures on the portable hard drive when not at home. I’ll check our home PC via LogMeIn later. The evening draws on here, and Anna will need her bath soon. As she is still only 10 months old, we’re not planning to keep her up for the arrival of the New Year. The last day has seen the temperatures drop again – yesterday we saw it rise to -2C, almost enough to ruin snowmen, with some snow melting, however today fresh snow has fallen, and the temperatures was back towards -20C again. I’m glad it isn’t dropping really low once more, as the fireworks that many people let off past midnight each year are well worth standing in the snow for.
Dec 31 2009
Betas Installed, Temperatures Dropping And Fireworks
Dec 20 2009
WordPress 2.9 Scheduled Post Problems
Upgraded all my blogs to WordPress 2.9 last night, and took the opportunity to also update a handful of plugins on each site. Only one problem so far – scheduled posts are missed. That is to say that any posts I’ve written, and published with a date in the future are not made live once the correct time has passed.
Trimming my ping list down to just pingomatic did not help, neither did temporarily disabling all plugins active on this blog. Turns out I’m not alone in finding errors with posts that are scheduled – see this WordPress support thread. There are two options until a fix, and hopefully 2.9.1 is released – either goto the Edit page that lists all posts, and click the Quick Edit option for the missed post (then change the post status to Published), OR use the MIA plugin mentioned in that support thread. I’ve not tried the plugin myself, though others have reported success. For now, as I only have 3 posts scheduled to publish in the near future, I’ve used the Quick Edit route instead (editing the post directly does not allow you to change the status to Published, you’ll need to do it from the Quick Edit option within the Edit page for all posts.)
I’m a little bit surprised that this problem wasn’t detected with beta and RC1 testers, unless some last minute code changes were implemented?
[edit]
OK, looks like you might need to register at that site to download the plugin, and I was unable to leave a comment there as Comment Guardian apparently thought it was spammy. It also reported that Javascript or cookies weren’t enabled, which surprised me.
Anyway, I was trying to leave the following…
Until WordPress 2.9.1 is hopefully released, I imagine you’ll be getting a fair amount of new traffic to this post 🙂
Scheduled posts seem to be a problem for many 2.9 users.Weird, my comment was detected as spam by Comment Guardian the first time, wonder if this one will get through? In case it makes any difference, I used RoboForm 2 Go to fill in the Name/Mail/Site boxes the first time – entered them manually this time around.
Nov 04 2009
Ouch
Just lost all the tags on around 120 posts. I was trying to mass edit 100 at the same time, my server complained about memory issues, and upon checking the posts, it not only had failed to add the new one, it had stripped ALL the old ones!
Uggh.
Jul 28 2009
Calais Auto Tagger Problems?
If you use the WP Calais Auto Tagger plug-in, your site is on a server with PHP5, and cURL enabled, but no tags are returned, there may be hope. Although on other sites, both this and the auto archive tagger were working fine, here at ChrisMerriman.com, the post tagger was returning NO tags, even on long posts with a lot of viable keyword nominations.
For some reason, it turns out I need to change into Visual (as opposed to HTML) editing mode first. I can immediately swap back into HTML mode, without clicking the ‘Get Tags’ button first, and still have success, but for each post, I need to load Visual editing mode at least once.
At first I assumed the plug-in used some hook that is only loaded/parsed within (the admittedly standard and default) Visual edit mode, but on other sites this step was not necessary. So… no idea why it works, but I hope my comment on his plugin’s page, and this post, will help out someone someday and ensure they can use this plugin, and through it, Calais’s services to automatically suggest tags for the posts they are writing.
Comments Off on Calais Auto Tagger Problems?
Jul 28 2009
SearchTerms Tagging 2
Just wanted to write a quick post about a (WordPress) plugin I’ve started using recently. It is called SearchTerms Tagging 2 (I’m guessing I missed version 1?), and the idea behind it is quite simple.
As you may know from my posts about the WP GotLucky plugin, I find it interesting to see what people were searching for when they found my blog. Obviously a lot tends to be based around Astana or Kazakhstan in general, but sometimes people are looking for quite specific information about a software configuration issue they have, or for other people’s thought on a holiday destination. With the GotLucky plugin, I have an RSS feed and e-mails sent each time this site is found via a google search, but without running the search myself, I can’t tell specifically which post they ended up at. With SearchTerms Tagging 2, each post has a list of the search terms used to find the post (if this has occurred since the plugin was installed), and on the config page, I also have a list of which terms (and associated post) were found most regularly.
So, head on over to the page linked above if this sort of plugin sounds of interest you. If you have any queries/feature suggestions, check out the comments, where you’ll see the author is pretty quick and helpful in his responses/upgrades 🙂
Comments Off on SearchTerms Tagging 2
Jun 14 2009
Facebook User Names
Thanks to MattG for the heads up on Facebook’s new policy… I’ve just grabbed http://www.facebook.com/chris.merriman before any of the other Chris Merrimans on Facebook noticed 🙂
If you want to secure yours, pop along to http://www.facebook.com/username and select your preferred format. Props to Richard McLaughlin for reporting that facebook are using a similar policy to GMail’s approach to user names – you can drop the full stop between your first and last name if you like, or even play around with extra ones – ie http://www.facebook.com/c.h.r.i.s.m.e.r.r.i.m.a.n is the same as http://www.facebook.com/chrismerriman which is the same as http://www.facebook.com/chris.merriman
Anyway, I’m going to run a quick test on a new version of WP Security Scan now, and probably head to bed, hope everyone is well.
Comments Off on Facebook User Names
Jun 12 2009
Plugin Problem Traced – WP Security Scan
See my earlier (possibly related?) post on an inability to upgrade to WordPress 2.8.
It looked as though my laziness in tracing the upgrade initialization problems had caught up with me earlier, as I found I was unable to edit existing posts or pages, with a blank white page being presented, and no changes committed since using 2.8. Deciding this wasn’t something with I’d just ignore for now, I went through the plugins, individually disabling them, trying to edit an existing page§. If the page updated correctly, with no blank response, I re-enabled the plugin, and disabled the next in the list. Of course, I didn’t find the misbehaving plugin until the second to last one – WP Security Scan. I’ve left a thread informing the author on his forum, and just left the plugin disabled for now.
§ – In case you’re interested, I noticed that either the newer version of the DandyID plugin, or a change in WP2.8 had caused the list of places you can find me online to be presented on seperate lines, with accompanying text, rather than the space saving row of icons I had previously. This information has now been moved to the About / Contact Me page.
Comments Off on Plugin Problem Traced – WP Security Scan
Jun 12 2009
This Blog Will Change
… its appearance for a few minutes whilst I try to track down the root cause for the site’s inability to automatically upgrade to WordPress 2.8. I’ll be temporarily disabling all the plugins, so don’t worry if the site looks a little odd for a short while. Back soon…
Comments Off on This Blog Will Change
« Previous Page — Next Page »
Jun 12 2009
WordPress 2.8 Upgrade Problems
OK, problem sorted. I don’t know which of this site’s plugins caused this blog to be unable to automatically upgrade to WordPress 2.8, but after deactivating all of them, the process completed at the first attempt. Just in case this helps other blogs, if you currently have any of the following activated, you may want to disable them all, upgrade, and then obviously re-enable them. Akismet, All in One Adsense and YPN, All in One SEO Pack, Auto Thickbox, Broken Link Checker, Comment Referrers, DandyID Services, Different Posts Per Page, Easy IP2Country, Executable PHP widget, FeedBurner FeedSmith, Fuzzy Recent Comments, Google XML Sitemaps, MiniMeta Widget, MyBlogLog: Just for you, MyBlogLog Recent Readers Widget, No Frames, Revision Control, runPHP, ShareThis, Subscribe To Comments, Twitter Tools, WordPress Automatic Upgrade, WordPress Related Posts, WP-Blackcheck, wp-GotLucky, wp-headlineanimator, WP-o-Matic, WP Calais Archive Tagger, WP Calais Auto Tagger, WP Security Scan and finally Zap_NewWindow 🙂
You can now see why I didn’t follow the correct protocol (disable one by one) to discover which plugin was the naughty one 🙂 If I had to lay money on it, I’m guessing the No Frames plugin caused problems (I had already tried disabling the external WordPress Automatic Upgrade plugin), but I have no proof whatsoever.
Tags: Comment Referrers, correct protocol, DandyID Services, Different Posts Per Page, FeedBurner, Google, Link Checker, ShareThis, twitter, WordPress, XML
Comments Off on WordPress 2.8 Upgrade Problems