Infinite loop detected in JError in Joomla 1.7

From Joomla! Documentation

Revision as of 21:10, 1 September 2011 by Pe7er (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Replacement filing cabinet.png
This page has been archived - Please Do Not Edit or Create Pages placed in this namespace. The pages in the Archived namespace exist only as a historical reference, it will not be improved and its content may be incomplete.
This Page Needs Your Help

This page is tagged because it NEEDS REVIEW. You can help the Joomla! Documentation Wiki by contributing to it.
More pages that need help similar to this one are here. NOTE-If you feel the need is satistified, please remove this notice.

Documentation all together tranparent small.png
Under Construction

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 Pe7er (talk| contribs) 4 years 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]';
 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();

remove the //commenting tag and add the < pre > tags to get a readable output

 // echo debug_print_backtrace();

change to:

 echo debug_print_backtrace();