2. Home
  3. Tags
  4. Tag troubleshoot

troubleshoot

  • GoDaddy's Joomla blues

    A while ago I wrote a tip about problems geting SEF URL's work on 1&1-s servers. Back then I didn't realized, that the problem is the same - or at least fairly similar - on GoDaddy's servers too. Not everywhere, I have a site running on GoDaddy with sh404SEF without any need of tweaking the .htaccess file, but recently I had issues with another site.

    So, the trick above solves the problem, but what is the cause?
  • Help! I'm Locked Out Of My Site!

    Beginning with Joomla 1.6 it's possible to lock anyone out of the back end of the website — including Super Users with Admin permissions — by setting the Site Admin permission to Deny. And this is something you can do accidentally against yourself by playing with the permissions without knowing how exactly these settings are working. That can have unpleasant side effects especially at the Super User group or at the Manager or Administrator group level. If Manager or Administrator is set to Deny, the Super User would inherit Deny from these groups, even if the Super User group is set to Allow.
  • How to turn your error reporting level to maximum?

    Anyone who maintained/developed something with or for Joomla, or needed to troubleshoot something on a misbehaving Joomla site knows the feeling: something does not working, and the available error messages aren't showing enough information to help you track down the root of the issue.

    Any extra bit of info can help, so here is a tip for Joomla 1.7 which might help you got that.
  • Increase the available memory for your page

    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.
  • Infinite loop detected in JError

    Today I have faced a strange, never seen before error. I have worked on recovering a server with couple of old Joomla sites after a major crash, when one of sites ceased to "fly" again, and showed up nothing else but a white screen with this text:

    Infinite loop detected in JError
  • 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.
  • Invalid Token, in store config - when try to upgrade VirtueMart

    Time-to-time I am hitting the wall with this, even with 100+ VM sites in my portfolio, and parts of VM core having my signature. Here are few tricks wich usually solves the problem.
  • JFolder::create: Could not create directory

    The full error looks like this:

    JFolder::create: Could not create directory
    Warning! Failed to move file.

    You might see this nagging error every once you install something to your Joomla site. Apparently everything working, but - as any errors you see - should alert you: something isn't right with your site, and even if apparently everything works, you might have unexpected problems later!
  • 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.
  • Joomla 1.0 and PHP 5.3

    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.
  • Joomla display a blank page containing "Error" string

    ... and does this randomly, both in frontend and backend, sometimes showing the correct pages, and rarely an error message saying, that "table '#__session' is marked as crashed and last (automatic?) repair failed".
  • jtablesession::Store Failed - DB function failed with error number 1062

    It is an error which drive me crazy couple of times. It's easy to fix - but hard to detect why happening. I didn't see any good explanation which fits to each single situation I needed to handle it. There are couple of popular theories on what causes the "jtablesession::Store Failed - DB function failed with error" type of errors, but sincerely  I can not confirm any of them:

    • Flooding (Check your http access logs for access IP’s, and your PHP error logs). Solution: Try dropping the time out down temporally to a lower value, to see if the sessions clear or not.
    • SEF If your site has a lot of visitors table jos_session can accumulate substantial overhead. And if you use default SEF, some 404 pages can make some bots to enter into loop, and those bots gives you a huge session overhead.
    • Site statistics from within Joomla. Enabling statistics through your site configuration just adds extra MySQL queries and increases server loads.
  • Just turned SEF on and inner page images where gone

    Did you had this experience? Couple of days ago I just turned on SEF and the inner pages began to act weird - images disappeared, modules misbehaved, scripts weren't loaded...

    My first reaction was that I have set something wrong... or the SEF component I used have a flaw. After few days of digging I found that the issue has a much simpler cause.
  • K2 - Error decoding JSON data

    After updating K2 to version 3.6.3, in the backend, when tried to edit one of items, I got this error:

    Error decoding JSON data: Syntax error.
  • Lost admin password - reloaded

    Did you manage to lost your password? Worst, maybe you lost the Super Administrator password? And for some reason you can't use the retrieve lost password functionality of Joomla...  If you use Joomla, if you forget your password you could just simply click on the "Forgot password" menu, and the new password will be sent to your email address. But what if you can't remember the exact e-mail address, or you have a local, development version and did not have the mailer handy... or your Internet connection is down? Or, worse - happened to me couple of times - you need to overtake a site originally developed by someone else?
  • MAX_JOIN_SIZE problems

    Recently in more (usually cheap) hosts more of my clients reported a strange error, wich showed up recently, withouth notice.

    The error message is like this:

    1104 The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET SQL_MAX_JOIN_SIZE=# if the SELECT is okay

    followed by the failing query.
  • Menu items keep reordering after migration

    Recently - once again - I faced a very annoying problem: after migrating a Joomla site from Joomla 1.5 to Joomla 1.7 - and later to Joomla 2.5 - time-to-time the menu ordering switched back to the essentially wrong ordering resulted from migration process. First time I thought I am doing something wrong, and when my client cried about, I reordered a menu again and again. I have to fight with this problem too many times until I found the source of error and an easy fix.
  • Misterious "Bad Certificate" error when you click on certain inner links

    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?
  • MooTools problems after FireFox update to version 18

    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.

Page 2 of 4