I received a WSOD after installing a module (I can't remember if it occurred before or while I was running update.php.
I've installed dtools, and when I ran it, I got the followinging message:
Fatal error: Call to undefined function ctools_include() in /home/account/public_html/sandbox/sites/all/modules/ctools/page_manager/page_manager.module on line 665
array(4) { ["type"]=> int(1) ["message"]=> string(44) "Call to undefined function ctools_include()" ["file"]=> string(92) "/home/account/public_html/sandbox/sites/all/modules/ctools/page_manager/page_manager.module" ["line"]=> int(665) } Rebuild system table.
\nForce to load all enabled module files.
\nEnabled potential dependency module: $module_name.
\nPlease refresh the page if problem has been fixed.
\nERROR: Script execution halted with error: Call to undefined function ctools_include()
Backtrace: wsod_sess_close(:);session_write_close(:);
array(4) { ["type"]=> int(1) ["message"]=> string(44) "Call to undefined function ctools_include()" ["file"]=> string(92) "/home/account/public_html/sandbox/sites/all/modules/ctools/page_manager/page_manager.module" ["line"]=> int(665) } n/a
--
So what's next? I'm not sure how to interpret this.
Is this a bug in ctools?
Thanks,
JV
Comments
Comment #1
alexanderpas CreditAttribution: alexanderpas commentedmoved to ctools issue queue.
Comment #2
jvinci CreditAttribution: jvinci commentedOK, here's what I've done...
1. deleted (compressed and then deleted) the ctools folder in /sites/all/modules
2. refreshed page and got an error with having do do with forums (didn't record it)
3. deleted (compressed and then deleted) the forums foder in /modules
4. refreshed webpage and site came up. There were errors, but only because I had deactivated a bunch of modules using Contrib Toggle just before the WSOD.
5. Extracted Forums back into /modules--did not activate it.
6. no errors
7. Extracted ctools back into in /sites/all/modules--did not activate it.
8. Attempted to run update.php--> got what appeared to be a 404 error or something similar (the exact number of the error didn't appear).
9. uninstalled ctools
That's where I'm at now. I'll try to reinstall it afresh to see what happens.
-JV
Comment #3
Skirr CreditAttribution: Skirr commentedI've updated (copied files) Drupal from 6.13 to 6.14 and got a WSOD just before update.php
dtool showed the same error
Deleted ctools and site came up again.
Comment #4
merlinofchaos CreditAttribution: merlinofchaos commentedThis is very confusing. ctools_include() is right at the top of ctools.module, line 81, the second function. The only way this wouldn't be there is if ctools.module is not enabled. page_manager.module depends on ctools.module, though. So if it's enabled and ctools isn't, this is not a state Drupal could normally put you in. I simply do not understand how you can be getting this error.
It's possible update.php is automatically enabling page manager because it's trying to update panels? Perhaps disable panels or enable ctools prior to hitting update.php.
Comment #5
Skirr CreditAttribution: Skirr commentedSo i just deleted the Ctools folder. Site came up, i updated drupal 6.14. Than downloaded Ctools again, and everything back to normal. But wow i panic :))
Perhaps you right about the update.php
Comment #6
cgjohnson CreditAttribution: cgjohnson commentedFor what it's worth in troubleshooting, I got the same error after uninstalling page manager (after I had disabled and uninstalled ctools).
I too was able to fix my site by deleting the ctools folder in my sites/all/modules -- so maybe this is a bug with the uninstall? It doesn't remove the folder so even after uninstalling ctools, you still see pagemanager.
Comment #7
BrightBoldI just got this error after attempting to disable contributed modules in 6.14. I had not run update.php - just clicked "save configuration" and then possibly refreshed the page. Based on this thread I deleted the folder and the site came back up (yay, thanks).
It looks like maybe Panels hadn't been disabled (I had attempted to use the Contrib Toggle module to automatically disable all the contributed modules - it worked fine last time but this time didn't get them all so I did the rest by hand - maybe I missed Panels or was unable to select it?) No idea whether that could have caused the error but there's the info in case it's helpful.
Panels is 6.x.3.2 and CTools was 6.x.1.2 (I just noticed that's a different version than listed in this issue - I assume the correct etiquette is to add to this issue but let me know if not and I'll do it right next time).
Comment #8
adraskoy CreditAttribution: adraskoy commentedI can confirm the problem. I was also disabling all contributed modules in preparation for a 6.13-6.14 upgrade. On saving the configuration I got this error. It's repeated whenever I attempt to go into the module administration page. As for the others, removing the ctools directory from modules provided a workaround, however I was unable to disable the panels module.
Comment #9
seanrIs it possible that the weight for the two modules is wrong? I just ran into this with an installation profile as well - ctools appears in the module list before purl yet I still got this error. This only just started happening - the install profile has not been modified and used to work just fine as recently as a week ago.
Comment #10
merlinofchaos CreditAttribution: merlinofchaos commentedI've put in a guard against this condition, though I don't know if it's enough. Let's see if this turns up again in CTools 1.3
Comment #11
cmcintosh CreditAttribution: cmcintosh commentedThis error was still showing up in the latest stable release of both ctools/purl, this seems to have not been rolled into the prod versions as of yet.
My solution was to add the following as the first line for _purl_options function, but not sure this is how it should be corrected:
module_load_include('module', 'ctools', 'ctools');
Prevents any errors on page loads from what I can tell so far.
Comment #12
merlinofchaos CreditAttribution: merlinofchaos commentedI am unfortunately not familiar with purl or what it does.
Comment #14
scott859 CreditAttribution: scott859 commentedSolution described in #11 worked for me - thank you.
Comment #15
SocialNicheGuru CreditAttribution: SocialNicheGuru commentedSolution #11 worked for me also... random though because this error never came up before
Comment #16
SamRose CreditAttribution: SamRose commented#11 http://drupal.org/node/573646#comment-2589772 above also worked for me, for whatever it may be worth
Comment #17
jun CreditAttribution: jun commentedThe same error also appeared just after enabling the RDF 6.x-1.0-alpha7 module. Fix in #11 also worked.
Hope this helps.
Jun.
Comment #18
jun CreditAttribution: jun commentedActually #11 only gets rid of the WSOD, however PURL seems to not be functionning anymore. A bit of research showed that this was already reported here #682346: WSOD when install RDF and have purl installed, but changing the weight of the RDF module as suggested didn't help.
FYI, this is an obstacle on my way to try to install fileframework on openatrium.
Jun.
Comment #19
SocialNicheGuru CreditAttribution: SocialNicheGuru commentedwill this be added to the dev version?
Comment #20
rsvelko CreditAttribution: rsvelko commented#11 worked here too.
Comment #21
rsvelko CreditAttribution: rsvelko commented#11 does this :
function _purl_options($active = TRUE) {
+ module_load_include('module', 'ctools', 'ctools');
it works
Comment #22
chriscalip CreditAttribution: chriscalip commentederror sighted, in my case i saw on system table that ctools status is 0
updated and fixed.