CODEWITHSUNDEEP
phpjoomla
Muhahaha
Muhahaha

Reputation: 67

Admin Backend of Joomla (ADMIN PANEL) is extremely slow

Hello i have problem with Joomla 1.5.26

The front end of the website is opening fast. But admin panel loading extremely slow and from one link to other it takes ~1 minute to load!

Hosting providers tells me that there is no problems in our hosting and server where are hosted our websites.

Here is php.ini file that my hosting providers put into main folder of website https://www.dropbox.com/s/djuinnmdjftsi1r/php.ini

This is because yesterday i cannot login in the system and shows me message: Internal Server Error 500. Now works fine but load time is killing me..

What to do?

Upvotes: 4

Views: 5410

Answers (2)

sovainfo
sovainfo

Reputation: 101

Would advice to set error reporting to 'maximum' instead of 'development'. Consider 'development' to verbose due to 'strict' messages.

Upvotes: 0

Peter Wiseman
Peter Wiseman

Reputation: 354

As provided in the comments against the original question, answering the "What to do?" question.

  • Turn error reporting to Development and review the errors/warning/notices, then revert error reporting back to the previous setting
  • Turn on debugging and inspect the load time of the various phases
  • Disable all additional extensions, then re-enable one by one, or variations on this approach
  • Update extensions to latest versions (though you really want to do this on a test site first)
  • Clone the site and try and reproduce the problem, then you have somewhere to do more aggressive debugging without effecting your end users

Aside: I had a similar problem recently with a NoNumber extension and it turned out a regex was performing poorly. I had upgraded the extension which upgraded the framework, which effected another extension from the same provider. The solution was upgrading all extensions from that provider. Or... perhaps I have this wrong and that was an unrelated problem. I had another where I had applied an update which contained the problem. By the time I got around to debugging, the developer had already provided a fix - I just had to go looking.

Upvotes: 6

Related Questions