SeeIT Consult

There are various reasons why wp-cron does not work, one of the most common ones being a misconfigured network or firewall.

However, due to the way wp-cron works, anything that prevents WordPress opening a http connection to itself will cause wp-cron to fail. In my case I had a .htaccess password set on the development site to prevent crawlers from indexing it.

A quick test to see if WordPress will be able to access wp-cron.php is to use wget from the command line of your server:

If this fails you will at least have a clue as to why it failed. It would be great if WordPress could log the failure rather than remaining silent (even with WP_DEBUG enabled). This was discussed in http://core.trac.wordpress.org/ticket/11831.

You would think that many of your worries are reduced when you move from shared web hosting to a virtual private server (VPS) but as my experiences testify, there is are some pretty frightening stories out there.

I have dealt with 3 VPS providers in the past year and this post goes through some of my experiences and offers some advice on what to consider when you are weighing up your options.

Not all VPS providers are created equal!

Continue reading ‘Choosing a VPS Web Hosting Provider’ »

Updated with more tests on 2010-05-16.
Click here to jump to the 2010-05-16 update…

The conventional wisdom always said that PHP’s include()/require() was quicker than include_once()/require_once(), but recently I came across an interesting post by Arin Sarkissian which suggests otherwise. Also I found more commentary on the performance benefit of using relative versus absolute paths in include()/require() and include_once()/require_once() statements (although the main article’s conclusions contradict Arin’s experiments). The Drupal developers discussed and benchmarked the relative/absolute include() issue too.

So in keeping with the spirit of quick and dirty experimentation I hacked up some code and ran some tests on include()/require() against include_once()/require_once() and on the relative/absolute path issue. The results are pretty surprising and I love to hear some views.

Continue reading ‘PHP: The include() include_once() performance debate’ »

The symptom

You cease your contract with your hosting company, cancel your contract and move your web site. People start to complain that they cannot reach your web site. Nothing seems out of order.

The problem:

You were hosting with a major ISP (like Eircom, Magnet or BT Ireland). They put DNS entries into their servers for your web site. When you cancel your contract they should remove these entries. Magnet and BT Ireland are two companies that are negligent in this regard. If they don’t remove these DNS entries, then their customers can have problems reaching your new web site.
Continue reading ‘Beware: ISP’s as Hosting Companies – watch your DNS’ »

Symptom:

• An XML file saved as something.php.html
• Apache was trying to parse it as PHP and throwing an error because Short_open_tag was ‘on’

Fix:

Add the following to an .htaccess file in the folder (or a parent folder):

I don’t know if this is a ‘bug’ or a ‘feature’. I don’t see why Apache should be interpreting *.php.html files as PHP (BAD Apache) but now that the issue is fixed for me I am not too concerned.

Update: 2010-05-07:

Kae Varens already came across this and blogged about it in October 2008. It turns out that

1. it’s Apache – not me!
2. there is a lot more to this than meets the eye

If you manage your own Apache web server then Kae’s blog post is required reading.

A client was approached the other day with an offer that sounds too good to be true. Well guess what, it is!

For more information, Webphoria (a UK web development company) has the story of the AdWords scam, and James from Online Media Direct checked it out the story with Google.

If you are approached with such an offer, make sure you check out the facts. We’ll be quite happy to do so for you if you wish.

UPDATE:

And the muppet is… http://www.polepositionmedia.co.uk/ just in case you were curious!