Tips & Tricks Joomla Troubleshooter
Joomla Troubleshooter
Yesterday your Joomla site worked just fine. Today is misbehaving. And you're clueless... Right? Hey, you're not the first one having this experience. You're on the good site where you might find the cure for your problem!
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
After year of using myself the tip You Do Not Have Access to the Administrator Section of This Site successfully today I hit the wall.
I did one more stunt as the ones described above - but didn't helped.
But let's see first the failed hack - because that\s interesting too:
I was sure that ths is an error wich newer come back to me - was a relatively common one in early 2010-s, since dissappeared from my radar. Today one of my former students approached me with his problem. He took over a site running the latest Joomla, and when tried to change the blog list views to category blog views, as the siteowner requested, the respective pages ended up with a white PHP fatal error death screen.
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.
Today I had to upgrade an old, Joomla 2.5.7 site to latest Joomla, everything went out fine until I had to do the first critical step - the upgrade from Joomla 2.5.28 to Joomla 3.51. Did I mentioned that server has PHP 5.6.25 withouth possibility to upgrade - at least not on short term?
OK, so, wasn't the best setup condition available, but usually this is not a dealbreaker.
And BUMM, I have seen an old "friend", a popup saying:
ERROR: Invalid login
... 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".
More Articles ...
- K2 - Error decoding JSON data
- Installer tabs missing after upgrade to Joomla 3.6
- Can't login after moving to new server
- You cannot access the private section of this site
- Crashed article editor
- Save failing when adding new tag in Joomla 3.0
- 500 Internal Error when saving an article - reloaded
- Server Forbidden 500 error when saving in Joomla Admin backend
- Invalid Token, in store config - when try to upgrade VirtueMart
- You Do Not Have Access to the Administrator Section of This Site
Subcategories
What to do when you got hacked? Here you can find some advices, tricks and tips on what you can do!
- Article Count:
- 5
Site Statistics
Users 319
Articles 303
Articles View Hits 5879497
Today 2124
Yesterday 3101
Week 13791
Month 85680
All 4507141
Currently are 570 guests and no members online