Infinite loop detected in JError in Joomla 1.7
From Joomla! Documentation
 |
This is a article which: needs review. You can help the Joomla! Documentation Wiki by contributing to it. More pages that need help similar to this one are here. If you feel the need is satistified, please remove this notice. While actively editing, consider adding {{inuse}} to reduce edit conflicts. |
| |
This article or section is in the process of an expansion or major restructuring. You are welcome to assist in its construction by editing it as well. If this article or section has not been edited in several days, please remove this template. This article was last edited by Tdijk (talk| contribs) 19 months ago. (Purge) |
When moving a locally developed Joomla 1.7 site to a server results in the error Infinite loop detected in JError in Joomla 1.7 there's something wrong with the configuration in configuration.php
First double check the following variables:
public $dbtype = 'mysqli'; // if your server doesn't support mysqli, try 'mysql' public $host = '[some host]'; public $user = '[some database user]'; public $password = '[some password]'; // wrong password could be the cause public $db = '[some database]'; public $dbprefix = '[someprefix_]'; public $log_path = '/logs'; public $tmp_path = '/tmp';
To get detailed information about the error, edit on the server /libraries/joomla/error/error.php
public static function throwError(&$exception) { static $thrown = false; // If thrown is hit again, we've come back to JError in the middle of throwing another JError, so die! if ($thrown) { // echo debug_print_backtrace(); jexit(JText::_('JLIB_ERROR_INFINITE_LOOP')); }
remove the //commenting tag and add the < pre > tags to get a readable output
// echo debug_print_backtrace();change to:
print"<pre>"; echo debug_print_backtrace(); print"</pre>";
Now Joomla will show a more detailed error that might give you some clues of how to correct the settings in your configuration.php. Don't forget to switch off the detailed error reporting afterwards by commenting the echo debug_print_backtrace();.
