Did you added something to a perfectly working Joomla site, and you suddenly have a blank age instead your site? Chances are that you hit the memory limit allowed to you on your server. Memory limits help to keep scripts from running out of control or using up all of your free memory. This value is generally carefully set by your host's SYSADMIN to let the hosted sites to run smoothly without bottlenecking each other by overusing this precious system resource.

Lately many of Joomla 1.5 site owners have been experiencing weird Java script  errors when tried to use their site with FireFox browser. Receiving lots of request almost simultaneously the first reaction was that some software update caused the problem.

One of my clients, who have serious Joomla background complained recently, that on his brand new Joomla site when he clicked on one of menu items his browser raised the well known "Bad Certificate" error. The site obviously worked well, but for some reason the link to that inner page was created using the https:// prefix.

Obviously, he had no valid security certificate in place - as many sides does not have these days, but the menu entry being an inner, Joomla generated link he (and myself, for some... 5 minutes approx) was dazzled, what might happened?

GoDaddy is notoriously buggy when comes to Joomla hosting. But when you turn on SEF, you might have another nasty surprise, instead of your site's pages you might see this:

I was totally forgot about this problem - until this morning, when I found in my mailbox a request to save someone's old Joomla 1.0 based site from disaster. I was thinking, that until now all servers where upgraded to PHP 5.3 and all Joomla 1.0 sites upgraded - or at least patched to work with the new PHP.

Today one of my clients asked me to find out why he is running out of available disk space, despite the fact that has an average Joomla 1.5 site with nothing extraordinary installed, and a generous 2 Gigs server space. In couple of minutes I found the first clue, the /components/libraries/cmslib/cache/ directory has a whopping 700 Megs plus worth of content consisting by outdated cache files. From there finding the culprit was easy - it's the Jom Comment component which is filling up the server space with unneeded cache files. The fix was promised sometime back in 2009, but seemingly was never implemented - at least not in the Joomla 1.5 versions.

What you can do?