Error 500 or(error with my site
Fatal error: Uncaught Exception: Представление не найдено [name, type, prefix]: profile, awg, usersView in /home/www/site/ba/libraries/legacy/controller/legacy.php:885 Stack trace: #0 /home/www/site/ba/components/com_users/controller.php(39): JControllerLegacy->getView('profile', 'awg') #1 /home/www/site/ba/libraries/legacy/controller/legacy.php(728): UsersController->display() #2 /home/www/site/ba/components/com_users/users.php(15): JControllerLegacy->execute('display') #3 /home/www/site/ba/libraries/cms/component/helper.php(405): require_once('/home/www/site/...') #4 /home/www/site/ba/libraries/cms/component/helper.php(380): JComponentHelper::executeComponent('/home/www/site/...') #5 /home/www/site/ba/libraries/cms/application/site.php(191): JComponentHelper::renderComponent('com_users') #6 /home/www/site/ba/libraries/cms/application/site.php(230): JApplicationSite->dispatch() #7 /home/www/site/ba/libraries/cm in /home/www/site/ba/libraries/legacy/controller/legacy.php on line 885
If you're getting an uncaught exception then something is unregistering the core global exception handler or you've been hacked. The error message is 100% correct (even if it's not "user friendly").
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-05-11 14:26:14 |
Closed_By | ⇒ | mbabker |
joomla.org has a 500 error https://www.joomla.org/core-features.htwfa
But that's another matter. of course
Because mod_search
is rendered on the error page and it tries calling $doc->addHeadLink()
which doesn't exist on anything but an HTML object. So the error page throws an error there.
oh ... the error page "thing" again :)
Reason 5214890 why I hate Joomla's error handling layer
How fixed this bug? See link: https://www.joomla.org/core-features.htwfa
This it's fixed, but how?
There isn't a core fix. In the case of joomla.org
we changed to using Smart Search (mod_finder) instead of "legacy" search (mod_search) and the former module doesn't have a JDocument
call like the latter does (in part because that feature was never fully implemented for some reason).
You shouldn't be getting an uncaught exception message. The fact you are means that the core bootstrap process has been altered or something has overloaded the core exception handler. Make sure your includes/framework.php and libraries/cms.php files are the correct versions then check for any uses of set_exception_handler()
or restore_exception_handler()
in your installation.
For further support, please use the Joomla! Forum.
Cannot reproduce this in latest staging.
/test-page.html (article page that exists) = OK
/test-page.htsdl = 404 error