cache

  • Add caching to your modules

    In several previous tips(like Turn caching on!, Caching reloaded, Give a boost to your Joomla site and couple of others) I urged you to turn caching on wherever is appropriate. Recently one of my readers had criticized me, because he tried to follow the tip, but on several modules he used simply he didn't found the option to turn cache on (or off) in module settings.

    Indeed, this might be a problem, since some modules does not have this option! this little detail don't need to stop you to do so!

  • Caching reloaded

    This tip is only for Joomla 1.0! For newer versions the handling of bandwidth is more cleverly solved, so read on only if you still use Joomla 1.0.

  • Customize your Browser Caching for Faster Performance

    In the race to the top of Search Engine result pages - ultimately higher SERP (Search Engine Ranking Points) the site speed is an important factor. There are lots of tricks to increase a Joomla site's speed, here is one wich does not need additional code to be installed and executed, but yet is powerful an let you fine-tune your site's performance.

  • Give a boost to your Joomla site

    One of the problems any webmaster is facing that the site may be not fast enough to meet his expectations. How you can squeeze up that last drop of extra speed from your site? We published lots of tips on this theme, but let's reorganize and update them with possibilities of the latest Joomla implementation (1.5.10 as the original article was written, 1.7.3 on last update I wrote this). I try to present them in decreasing order of importance/effectiveness, but the actual order reflects mostly my personal experience - which may be different from yours - and not some rigorously measured facts. But, believe me, I have a good nose for this. Some of the tips are easy to implement - and some may need advanced knowledge. But I mixed them up there to let you know what you may need to check - or what you may need ask from your programmer/web developer.

  • Installer tabs missing after upgrade to Joomla 3.6

    After upgrading to Joomla 3.6 I had a nasty surprise - in the Joomla Installer the tabs - Install from file,  Install from folder etc.., all but the Install from Web - where all gone. Of course, nothing found on the web: this happens when you are an early adopter. But I discovered the "fix" accidentally, on my own.

  • JLIB_APPLICATION_ERROR_COMPONENT_NOT_LOADING

    Did you ever get this error on a Joomla 1.7 or 2.5 site? If yes, you probably searched the net and was dazzled by the amount of hits. Today I got this:

    About 33,900 results (0.28 seconds)
  • JLIB_APPLICATION_ERROR_COMPONENT_NOT_LOADING reloaded

    Suddenly you get the JLIB_APPLICATION_ERROR_COMPONENT_NOT_LOADING all over the place - frontend and backend alike? And you searched the web and get all sorts of confusing tips?

    Look no further - at least until you did not tried this simple trick! (Especially if you just relocated your site recently - or your hosting company did it for you). If you have plenty of space, check the following tip too.

  • The directory /components/libraries/cmslib/cache/ is filling up and is eating my server space!

    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?

  • Turbocharge your Joomla site

    Over the years spent in web page building and maintaining (since 1995, when published my very first webpage on a self-hosted SCO Linux box) a lot of information has been collected, settled down and at the end the best and most important tricks helping to make a website became fast and stable in the same time where surfaced. Despite the fact, that I wrote about this subject several times, it's a subject wich never looses his actuality.

  • Turn caching on!

    To improve your Joomla website's performance, just turn on "caching" on the "Cache" tab from Joomla's Global Configuration. When caching is turned on, Joomla creates a static file or "cache" of your website data on the disk. When the static file is found, the system retrieves the data from the disk rather than from the database. This improves performance because it saves system resources by not making redundant SQL calls to the database. And it will also speed up the display time of the pages.

    You can set cache refresh rate in seconds. If you don't constantly update your contents, you might want to set it longer. And to further improve it, go to all your modules configurationand select "yes" to cache option (not available in all modules).

  • Virtual spring cleaning for your Joomla sites

    Websites take maintenance, and making a habit of performing a little spring cleaning each year can keep a business website running smoothly. The tips below does not apply for Joomla sites alone, any site can benefit from most of these tricks and tips.

  • Why my Joomla site is this slow?

    Joomla generally is running at an acceptable speed -  users aren't seeing differences between an average Joomla site and another CMS'es. But what if they do? What can cause the (sometime unbearable) slowness of some Joomla sites?

  • You are not authorised to view this resource

    Sometimes when you publish a new menu item, and everything seems to be OK, when you try to access the new menu item you just created you hit the wall: instead of the intended content you'll see the following error:

    You are not authorized to view this resource.
    You need to login.

    Even more confusing can be the situation when a link which used to work behaves this way. The target content item is published, access rights are set to Public, and you still got this message! What can be wrong here?