Throughout our website here at UsingJoomla.com we give many tips, hints and suggestions.
![]()
Many articles include boxes like this one that include a tip.
There are articles on web-hosting, and Joomla Tools.
However - this article goes in a slightly different way.
Sometimes when we are building our website things "go wrong" - it happens in all walks of life.
There are however some things we can do to "fault find" - from simple things to much more complicated.
Here we aim to list some of the more simple things we can try.
![]()
The first thing we should do is:
Keep calm !
Ask yourself some questions
- what is not working ?
- when did it go wrong ?
- do you get any error or warning messages ?
- is it possibly a browser issue rather than a website issue ?
Things you can consider are
- clear your Joomla caches
- clear your server caches - for example: opcache
- clear your browser cache, close your browser, re-open your browser and visit your site again - browsers can cache your website meaning changes might not always work properly
As well as . . .
- have you just installed a new extension/component/plugin/module ?
- if you have:
- have you enabled all necessary features ?
- have you recently changed a setting or parameter ?
- if you have changed a setting or parameter try changing it back to what is was
- have you recently updated one or more component, plugin, module (extension) ?
If you are having an issue with the "front-end" - something not working or "looks terrible"
- try a different browser - does it work / look as expected ?
- try the same browser on a different PC / Laptop / device
- if trying a different browser, or different PC / Laptop /device is not such an easy option - have you added one (or more) browser extension(s) - try disabling browser extensions - these too can interfere with website functionality
If you have recently enabled, or disabled, plugins or modules?
- try disabling plugins / modules one at a time that you have recently enabled - does the issue go away ?
- try enabling plugins / modules one at a time that you have recently disabled - does the issue go away ?
![]()
Above we say: try disabling plugins/modules one at a time.
Two important points to remember
1) Disable - do not (yet) uninstall - there is a major difference between disabling and uninstalling
2) Take a note of what you disable - you may need to enable them again after your tests
If you have updated one or more component, plugin, or module - developer mistakes happen.

A couple of very true and apt quotes
'One who makes no mistakes makes nothing' Giacomo Casanova
'It's only those who do nothing that make no mistakes, I suppose.' Joseph Conrad
When you are aware that an update is available, consider
- visiting the developer's change-log for that (those) extension(s)
- what does the change-log indicate has changed ?
- this will give you a good idea of what has changed and maybe what to expect, or to look at if there is an issue for you ("Forewarned is forearmed")
- waiting a few days, for example 3 - 5 days, before updating; Why ? Reported issues may well get resolved quickly
- what does the change-log indicate has changed ?
- visiting the developer's support forums:
- has there been an increase in support requests since the updated version was released ? ('Forewarned is forearmed')
- visit the developer's latest releases page
- has a new release been made available relatively quickly addressing any support requests ?






