Archives for posts with tag: wordpress

First of all, why are you using GoDaddy? I mean, seriously. Cancel that plan. Quit. Go somewhere else. Anywhere. Second of all, if your client is using GoDaddy, educate him, talk him into canceling that plan. Only if your client is stubborn, like mine, then read the rest of the article.

Basically, you do all the standard tasks you need to do to bring a fresh WP installation online, and after configuring wp-config.php file, you find yourself staring at blank page. If you plan contacting GoDaddy support – good luck with that.

Rather go through this list:

  • delete all the empty spaces and lines after the last meaningful line in your wp-config.php file
  • disable FastCGIread about how to do it here
  • if you’re getting the “Strict Standards: Assigning the return value of new by reference is deprecated in /…/…/public_html/wp-settings.php” error, you’re probably trying to install an older WP version; if you don’t really depend on it, get the latest version

And remember, leaving localhost in your wp-config.php file won’t cut it with GoDaddy, you need to change it to a value that’s specific to your account.

If you’re not able to make it work even after all these steps, quit GoDaddy.

This problem can be a bit annoying if you’re used to using the scheduled posts feature. But, like with any problem, there is solution, this time a quick and painless one.

Twitter Tools offers the possibility of setting up a default hashtag for your Tweets. Since this feature won’t work with the scheduled post, I took the liberty of seeing how this actually works – and to our luck – it uses custom fields. To be more precise, aktt_hash_meta custom field.
Therefore, when writing a scheduled post, simply add this custom field, and set it’s value to the hashtag you want to use, for example #ivanlistes. Save the post with this custom field added, schedule it, and that’s all there is to it.

It does require a bit more of work, but this way we don’t touch plugin’s original files, and we’re absolutely sure we won’t break something, cause future compatibility issues and so on.

What do these things have in common? They use JavaScript libraries to work, and if those get messed up, they will stop to function. This happened to me after switching hosts. Since I didn’t have the time to debug this, and search for a proper solution, I simply used this plugin. So, what does it do? Here comes the answer:

Allows your site to use common javascript libraries from Google’s AJAX Libraries CDN, rather than from WordPress’s own copies.

This will prove to be a fast solution for your problems. The plugin is useful even if you don’t have these problems, since it:

  • increases the chance that a user already has these files cached
  • takes load off your server
  • uses compressed versions of the libraries (where available)
  • Google’s servers are set up to negotiate HTTP compression with the requesting browser

WordPress is my blogging platform (and more) of choice, there’s no doubt about that.

But up until recently, I haven’t really dealt with bbPress, even though I did know it goes with WordPress nicely. To be more precise, easy integration and single sign on between these two should make them an obvious choice if you want to add forum to your WordPress blog/site.

On to the troubles!

After installing bbPress, which has a similar style of installation to WordPress, I tried to complete the integration. I followed all the steps described in the documentation, but ended up with ‘User doesn’t exist error’. I tried to repeat the process a couple of times, but I couldn’t get rid of it.

I checked out the forums, and found out a number of unresolved issues, identical to mine. Here are a couple:

If you read through these issues, you will see that a number of times, users are instructed to visit this blog, since it has step by step instructions. And while this is true (thank you author for being so kind), it has one error right at the end, where it says to fill the custom user tables part with ‘wp_user’ and ‘wp_usermeta’. The problem is, ‘wp_user’ table does not exist (at least not in the last WordPress release), it’s actually called ‘wp_users’.

So I’m not really sure whether this is a typo, or this table changed it’s name, but this little thing did it for me; integration works flawlessly.


Ashfame fixed the error we talked about, kudos to him! I’d say his blog is a great resource for WordPress in general, so do check it out!