wordpress tips

When your TweetMeme goes 404 on a WordPress site, here are some tips

Posted by | Social Media, Websites | No Comments
I had the interesting dilemma of TweetMeme failing on one of the sites I manage over the weekend. If you're using the TweetMeme plugin on WordPress to send your posts to Twitter you may encounter this problem. You'll see a question mark instead of the number of tweets, and when you try and tweet a post using the TweetMeme button you'll be directed to a 404 page on TweetMeme's site. I did what anyone would do; reinstalled the plugin, updated it to the latest version. The problem still persisted so after hunting around to see if others had the problem and how they fixed it, I can offer this solution which will probably work for you. Firstly, check your .htaccess file via FTP and make sure that any links there are relative, not fixed. If you don't know much about .htaccess or FTP, ask your webmaster or hosting service for help.  If you're not using a huge range of plugins, this probably won't be the issue anyway. The real issue is more likely the permalinks on your posts. Permalinks, for those who don't understand the term, are the addresses of your post which show up in the address bar of your web browser. If you include punctuation marks such as apostrophes, or more than one dash in row, for example, you will force an error. Those extra dashes and in particular that apostrophe made TweetMeme throw a wobbly. The UTF-8 code behind those characters was something it didn't recognise. If that sounds like gobbledegook to you, don't worry about it, knowing the finer points of the theory aren't important. Knowing how to fix it is. If you're getting TweetMeme errors look at the permalinks on pages the errors are occurring, and get rid of commas, apostrophes, extra dashes, question marks, exclamation marks and other punctuation. Make sure the permalink doesn't end on a period or full stop.   Your permalink may now look a little odd grammatically but the improved code behind it will make it easier to tweet about and may assist some of your other plugins to work better too.

When good sites turn bad. Canonical loops, white screens of death and more

Posted by | Services, Websites | No Comments
Until now I've managed to avoid the dreaded 'WordPress loop' which, like a naughty imp, attacks WordPress sites for a variety of reasons including website builders like me trying to get too clever. There are several loops you can get caught in - the Canonical redirect infinity loop is a popular (and very UNpopular with us lot) example. Add one plugin too many, or indeed change from standard permalinks to pretty permalinks, and you might get a message like this: “Firefox has detected that the server is redirecting the request for this address in a way that will never complete.” Or this one in Safari: “Too many redirects occurred trying to open this document.” There are some excellent plugins around that help fix this dire loop. Mark Jaquith's Disable Canonical Redirects plugin is probably the best and easiest to use. So when a client's site starting looping last weekend after I upgraded to the latest version of WordPress, I confidently installed the plugin and thought all would be well. After all, I'd backed up the database. Or so I thought. Things went from bad to worse. The initial site Canonical loops were all fixed up, with internal links working perfectly, but neither the client or I could log into the site. We were caught in a login loop. No matter how many times we cleared caches and history, at each attempt at logging in we were simply redirected back to the login screen. Nothing I could find online seemed to solve the problem no matter which browser I used. I got into the back end via FTP and removed all plugins, including the Canonical Redirect one. So then the site crashed. Big time. White screen of death. Nothing. Except my extremely red face. I contacted the host, a US-based company which shall remain nameless, but they were little help and didn't respond to my help desk emails. In the meantime my client had bought hosting at Crazy Domains as we'd intended to shift the site there anyway. It's local, the help desk is local, the backend system is CPanel X which is fantastic for maintaining your site, and the hosting rates are very affordable for small business. I recommend Crazy Domains to all my clients; if you need help those guys are really on the ball. So we pointed the domain name to the IP address at CD, and I installed WordPress. I jumped onto PHPMyAdmin and uploaded the backed up database. Or tried to. The system wouldn't accept it.  By now I was getting nervous. We'd wasted nearly a day already trying to fix the site up. Moving the WordPress site database should have been an easy process. Rather stressed and furious, a male version of meThe guys at CD help tried everything for another day to get the old database to talk to the new, and I had visions of burning the midnight oil rebuilding the entire site from scratch. Finally their head techy told me the old database wasn't a proper backup. Simply exporting from PHPMyAdmin doesn't create a backup of a WordPress site that PHPMyAdmin can read when it tries to reinstall it. Poor Crazy Domains, they must hate me; up to six calls a day for three days trying to get this wretched thing to work. So... back to the US host I went, this time using an online chat facility where all they could recommend was exporting from PHPMyAdmin. I explained why that didn't work and they suggested trying Navicat in the end. I downloaded a free trial of Navicat for My SQL and it's seriously good. $500 worth but I have it free to try for 30 days. There's plenty of documentation, and it's a simple to use, quality product. Realistically I didn't have to do much in the way of RTFM, it's quite intuitive. It took another chat line conversation to find out what the US host's port for the SQL server was, and finally, oh finally, I had a proper, working backup that the Crazy Domains server accepted with open arms. (By the way, Crazy Domains and any host using CPanel X provides you with a proper backup facility via CPanel X. For free. Great if you are doing single site backups.) But I still couldn't log in and the site's home page and all other pages were still glowing white with nothing on them. The air around my Mac was turning blue in response. Finally I reinstalled WordPress, crossed my fingers that the backup would upload again safely (it did), and all was well. The site was back online. My widgets hadn't kept their place in my sidebars, but that was the only difficulty I had. I could feel my blood pressure falling gracefully.

New to blogging? Here’s the gen to get you rating from day one

Posted by | Marketing, Websites, Writing and Editing | No Comments

I love WordPress. So does Google. They're a pair made for each other.

But simply starting up a blog on WordPress itself or one your own domain name isn't enough.

If you're a newbie to blogging, there are things you need to know. Obviously you have to have your blog topic all thought out (and I'm not talking about the posts themselves, I'm talking about what your whole blog is going to be about.). And I'd advise, if you're using WP to build a corporate site, to sit down with a pen and paper or better yet an Excel spreadsheet and work out the framework of your blog before you press the 'install' button on WordPress.

Once you've done all that, and preferably chosen a good professional theme (as professional themes are better built for SEO), there's something you should read: 43 Blogger Tips for WordPress Installations.

Andrew Rondeau is from the UK and a very experienced and successful blogger (by the way, I am not affiliated by him, but rather impressed by his entrepreneurship). While I implement a lot of his tips on my site and sites I build for others, Andrew puts this advice so succinctly and clearly it's worth directing you to his post.

One thing I can add to Andrew's advice is to tweet your blog. Get on Twitter. Install Twitter Widget Pro on your site and tweet every post. More than once, if you can find something different to say about your post on a separate tweet or two.

Social media works best when it works in partnership: blogs with Twitter, or YouTube, or Facebook. Try and combine your social media memberships with your blog.