Apparently I'm the only person in the universe with this problem but reporting it anyway.
Got a Fatal error: Call to undefined function themekey_node_nid2type() as well as various obscure permissions problems with themekey BUT only a few days *after* it was installed. Put it on, it works absolutely perfectly then a few days later the entire site dissolves into a puddle of 500 errors and is completely inaccessible.
Site is on d6 (but was upgraded from d5), running boost, and on a windows server, which is probably an obscure enough combination it explains why its just me.
Turning themekey off and back on again fixes it for a few days, then back to 500 errors again.
Unfortunately because of the several day lag its hard to replicate or debug and the things it is getting errors on are things it should have from the instant it is installed, not happen several days later so it has me completely stumped. Its clearly some kind of fatal interaction boost or its just some kind of weird fairy magic delay fatal bug.
Either way I point blank can't run themekey on this site, and just reporting it in case anyone else has the same error.
Comments
Comment #1
mkalkbrennerPlease post the stack trace from the php/web server error log file when the fatal error occurs?
Comment #2
mkalkbrennerno feedback
Comment #3
firfin commented@ giraffian, you are not alone.
I am experiencing the same problem. Also windows server btw (why oh why)
Had an old drupal site that started having problems after host updated to PHP5.3. So I downloaded to local machine. Made updates to core and modules (including themekey), everything running smoothly.
Uploaded site -> WSODs
Only working page is /user but logging in as admin just yields 'site offline'.
Admin pages give me 'access denied'
Regular pages just show a WSOD.
^^ do these qualify as obscure permissions errors?
Only thing visible in the providers' backend / logs is :
Not exactly the same issue as giraffian, but very close?
My guess is it has something to do with windows server environment and updating from older versions?
I went from 1.x (I believe 1.3, not sure) to 4.0 version of themekey.
Comment #4
firfin commentedI re-read giraffions description and tried his suggestion.
Disabling the themekey module manually removed the problem.
Not ideal (as I really want to use ThemeKey) but at least the site is up and running again.
Please let me know what other info I can provide.
Comment #5
firfin commentedJust updating. I have requested the following from the hosting provider:
Is there any other information which would help?
Comment #6
mkalkbrennerDid you clear the caches on the server?
A stack trace of the fatal error would be helpful!
Comment #7
mkalkbrennerI reviewed the code and probably found something. Can you post the current value of the variable "themekey_modules"?
Comment #8
mkalkbrennerI guess module 'node' is missing in variable "themekey_modules".
If you update ThemeKey and run the database update, the last step of the update is to update all the variables:
So if you updated the module on a different server, how did you deploy it to the live server?
Copied the code and the complete database including the tables system, variable and cache?
I assume, one of these tables is not up to date.
Comment #9
firfin commentedThanks mkalbrenner, my apologies for not responding sooner.
Unfortunately my request for more info from the hosting provider went largely ignored. They are unable to supply me with a stack trace.
To answer your other qeuestions:
- yes, I did clear caches (cleared appropiate tables using mysql)
- I did the update by clearing the www-root directory, uploading the updated files and clearing and importing the entire database. I also used the same files (and DB) on other servers, worked fine on those.
- themekey_modules in variables table is (currently )set to :
Unfortunately I do not know what is was at the time of malfunction.
There were a lot of other problems on the website. These disappeared without any intervention on my part. After these were all gone I re-enabled the themekey module and after visiting the themekey settings page all problems were gone.
I am sorry I can not provide more info, but it seems to me the caching software used by the hoster was ill-configured somehow. I don't know how else to explain this behaviour.
Comment #10
firfin commentedComment #11
TimeBandit commentedFYI I just had this issue on a site as well. D6, upgraded to 6.26 from I think 6.19. I noticed pages giving the error "undefined function themekey_node_nid2type() in /var/www/www.[domain].com/sites/all/modules/themekey/themekey_base.inc on line 447"
Clearing cache didn't work itself. Also disabling/re-enabling module didn't work by itself. After these efforts I visited admin/settings/themekey and saved those settings (no changes). Then I went to admin/settings/themekey/settings and saved those settings (no changes). This seems to have resolved my issue. No errors now.
I also noticed the server had been updated to PHP 5.3.3 (from 5.2) which I had not been informed would happen.