0

I have a Joomla! 3.8 site that is running fine on the front-end. However, when I try to access /administrator/ I get the following error:

ERROR 504 - GATEWAY TIMEOUT

There is nothing new in /administrator/error_log. However, in the error_log of the root directory, there is this log hundreds of times:

[20-Jun-2018 11:00:40 America/Chicago] PHP Warning:  require_once(/home7/userfolder/public_html/libraries/joomla/document/html/renderer/head.php): failed to open stream: No such file or directory in /home7/userfolder/public_html/templates/consultpress/error.php on line 42
[20-Jun-2018 11:00:40 America/Chicago] PHP Fatal error:  require_once(): Failed opening required '/home7/userfolder/public_html/libraries/joomla/document/html/renderer/head.php' (include_path='.:/opt/php70/lib/php') in /home7/userfolder/public_html/templates/consultpress/error.php on line 42

Line 42:

require_once(JPATH_LIBRARIES.'/joomla/document/html/renderer/head.php');

Is this related to the ERROR 504? If not, what could be the issue?

I've contacted the host (BlueHost) and they assure me it is a Joomla! issue. Any help?

Improve this question
1

This issue also exists in Gantry4 templates. Below is the fix for that:

if (!class_exists('JDocumentRendererHead')) {
   require_once(JPATH_LIBRARIES.'/joomla/document/html/renderer/head.php');
}
Improve this answer
  • Well, that solved the error in the error log, but had nothing to do with the 504 error. :/ – Michael Yaeger Jun 21 '18 at 17:20
  • Who is your host? Have you reached out to them? 504's can be caused from their side as well. – YellowWebMonkey Jun 22 '18 at 11:25
  • Yes, I mentioned that in the question. Bluehost says it is a Joomla! issue. – Michael Yaeger Jun 22 '18 at 14:12
  • Sorry, I missed that. Check out this advice from Akeeba guys: akeebabackup.com/support/admin-tools/Ticket/… – YellowWebMonkey Jun 22 '18 at 18:45
  • I've disabled error reporting via configuration.php, disabled Admin Tools via database, uploaded default .htaccess, and upgraded to PHP 7.0...nothing has changed. :( – Michael Yaeger Jun 23 '18 at 15:35
0

We ended up moving the site to another host and the problem was resolved.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.