Hi.,

I recently I did an upgrade from PHP 4.2 TO PHP 5.2.8 I was running Drupal 6.6 after my upgrade drupal works fine with no error everything seems to work fine I check most of my pages I add few book contents browse fine.
After I upgrade Drupal 6.6 to 6.9 is when it started my book content is not opening at all any page in the book content is working at all please help this is the error:

Fatal error: __clone method called on non-object common.inc on line 1685

thanks

David

Comments

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Title: Fatal error: __clone method called on non-object common.inc on line 1685 » __clone method called on non-object

Do you see any error messages in Drupal log, or other logs that point to a line in the book_access.module file?

pirulo’s picture

pirulo commented

I did not see any log regarding to this issue but the line pointing to the common.inc is this.

/**
* Provide a substitute clone() function for PHP4.
*/
function drupal_clone($object) {
return version_compare(phpversion(), '5.0') < 0 ? $object : clone($object); ## common.inc on line 1685
}

/**

thanks for you help

David

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

That function is not called directly from the project code; maybe the module calls a Drupal function, which calls drupal_clone().
To know if this is a Book Access bug, it's needed to trace back where the module is causing such error; otherwise it could be an issue caused by something else, and we are looking in the wrong direction.

I would try by disabling all the third party modules but Book Access.

harry slaughter’s picture

harry slaughter
Location Omaha NE USA
commented
Status: Active » Closed (won't fix)

this does not sound like a book_access bug.

you can install the devel module and in its settings, set error handling to 'backtrace' and then when this error occurs, you should see the order in which functions were called that led up to this error.

with that info, you can pretty well determine the actual source of the problem. find out what function is calling drupal_clone() and you will likely have the module responsible for the error.