Did you check you server log files for error messages?
What is the version of your drupal core? If you use a core older than 7.22 in combination with ThemeKey 3.x it will lead to a fatal error. (This is stated in the release notes and the .info file.)
I actually just started experiencing this as well - Themekey UI and dblog both produce WSOD for me, and I can't quite pin down what would have changed recently. The configuration I had in themekey still seems to be working properly, I just can't access the UI to change it. Running Drupal 7.26.
I am running drupal 7.26. I have checked php and apache logs and have not gotten any reports. I don't even get a WSOD. I just get that the page is unavailable. I can reload the page or check the connection based on what browser I am in. Once I delete the folder everything is fine and runs like normal. I have even tried the 7.x-3.0-dev version with no luck
I just dug into my logs and determined my issue was related to some custom code, so at least for my specific issue it doesn't appear to be themekey, but it's also sounding like your symptoms are different from mine.
I've also experienced this problem. I fixed it by comment out 'description' part in themekey_compat.info. I guessed that a single quote inside cause the problem. The environment is drupal 7.28 themekey 7.x-3.2 on Wampserver php5.4.3 apache 2.4.2. mysql 5.5.24.
@lekpanti:
I verified the description again. I contains less than 255 characters. Can you reduce the description step by step to see which character causes the issue in your setup?
(admin interface unreachable after copying the "themekey" folder in the "modules" folder).
I changed the themekey_compat.info description from :
description = "Optionally disable the theme switching capability of core and additional modules. Their theme switching capabilities will become part of ThemeKey's theme switching rule chain instead and therefor configurable."
to
description = "Optionally disable the theme switching capability of core and additional modules. Their theme switching capabilities will become part of ThemeKey's t"
The problems seem to be caused by (the combination of) two things:
1. the description
2. php version
It would be helpful if you try the latest dev version of ThemeKey and report the result including details about your environment regarding php version and operating system.
Hi,
Actually no, the issue is not solved yet with the 7.x-3.3 release. Still the same problem of broken admin as previously described.
Using WampServer Version 2.5.
Hi,
I have the same issue as soon as I put the ThemeKey folder into sites\all\modules. As soon as I delete that folder the admin UI is available again. I tried ThemeKey 3.3 and the 3.x-dev releases. My environment is:
Windows 8.1
Wamp: Apache 2.2.22; PHP 5.4.3; MYSQL 5.5.24
Drupal 7.37
Jquery 1.10
This is the first time I have attempted to use ThemeKey.
Rory
OK, if I read through the comments it seems like the issue is somehow related to Windows or WAMP or PHP for Windows. Unfortunately that's something I can't reproduce because I don't use Windows.
So I suggest to schedule a chat on irc to some real-time debugging on one of your setups. Please contact me to schedule such a meeting. You'll find me on #drupal-contribute most of the time or use my contact form on drupal.org.
Thanks to a lot of work with you we have identified that a long description in the themekey-compat.info file caused the issue. We designed a shorter text:
Optionally move the theme switching capability of core and additional modules to the ThemeKey rule chain.
Looking forward to the dev release to test.
Rory
Comments
Comment #1
mkalkbrennerDid you check you server log files for error messages?
What is the version of your drupal core? If you use a core older than 7.22 in combination with ThemeKey 3.x it will lead to a fatal error. (This is stated in the release notes and the .info file.)
Comment #2
tannerjfco CreditAttribution: tannerjfco commentedI actually just started experiencing this as well - Themekey UI and dblog both produce WSOD for me, and I can't quite pin down what would have changed recently. The configuration I had in themekey still seems to be working properly, I just can't access the UI to change it. Running Drupal 7.26.
Comment #3
Explosivo22 CreditAttribution: Explosivo22 commentedI am running drupal 7.26. I have checked php and apache logs and have not gotten any reports. I don't even get a WSOD. I just get that the page is unavailable. I can reload the page or check the connection based on what browser I am in. Once I delete the folder everything is fine and runs like normal. I have even tried the 7.x-3.0-dev version with no luck
Comment #4
tannerjfco CreditAttribution: tannerjfco commentedI just dug into my logs and determined my issue was related to some custom code, so at least for my specific issue it doesn't appear to be themekey, but it's also sounding like your symptoms are different from mine.
Comment #5
mkalkbrennerThis sounds like an apache or poxy error message. I assume that the request does not reach drupal at all.
Can you post a screenshot?
Comment #6
mkalkbrennerNo feedback for weeks.
Comment #7
lekpanti CreditAttribution: lekpanti commentedI've also experienced this problem. I fixed it by comment out 'description' part in themekey_compat.info. I guessed that a single quote inside cause the problem. The environment is drupal 7.28 themekey 7.x-3.2 on Wampserver php5.4.3 apache 2.4.2. mysql 5.5.24.
Comment #8
mkalkbrennerSeems like we missed one. If the issue occurs or not depends on the database's behavior
Comment #9
mkalkbrenner@lekpanti:
I verified the description again. I contains less than 255 characters. Can you reduce the description step by step to see which character causes the issue in your setup?
Comment #11
mkalkbrennerI'm still unable to reproduce the issue. But I decided to remove all single quotes from module descriptions as proposed by lekpanti in #7.
Can anyone test the latest dev version?
Comment #12
Chris Gillis CreditAttribution: Chris Gillis commentedI'm also experiencing this error. Steps:
drush dl themekey --dev
I repeated several times, with both stable and dev versions. Symptoms are consistent.
Note, I did not install at all. Error happens just by having the folder in your modules directory.
Comment #13
Chris Gillis CreditAttribution: Chris Gillis commentedComment #14
mkalkbrenner@Chris Gillis:
Can you share some more information about your environment? (OS, PHP version, ...)
Any errors in PHP error log?
Comment #15
Chris Gillis CreditAttribution: Chris Gillis commentedRunning WAMP on Windows 8.1.
Apache 2.4.9.
PHP 5.5.12.
Error Log:
Comment #18
geraud.demareschal CreditAttribution: geraud.demareschal commentedI experienced today the same issue.
(admin interface unreachable after copying the "themekey" folder in the "modules" folder).
I changed the themekey_compat.info description from :
description = "Optionally disable the theme switching capability of core and additional modules. Their theme switching capabilities will become part of ThemeKey's theme switching rule chain instead and therefor configurable."
to
description = "Optionally disable the theme switching capability of core and additional modules. Their theme switching capabilities will become part of ThemeKey's t"
And then I can load admin UI.
My configuration
Wampserver 2.2
Drupal core 7.33
Themekey 3.2
Comment #19
mkalkbrennerThe problems seem to be caused by (the combination of) two things:
1. the description
2. php version
It would be helpful if you try the latest dev version of ThemeKey and report the result including details about your environment regarding php version and operating system.
Comment #20
mkalkbrennerDid anyone test the latest dev? Is the problem solved?
Comment #21
Leeteq CreditAttribution: Leeteq commentedThat apostrophe is no longer present in that .info file in today's brand new 7.x-3.3 release.
Comment #22
mkalkbrennerYes, but does that fix your issues? I got no feedback so far.
Comment #23
cavilio CreditAttribution: cavilio commentedHi,
Actually no, the issue is not solved yet with the 7.x-3.3 release. Still the same problem of broken admin as previously described.
Using WampServer Version 2.5.
Comment #24
Rory Downes CreditAttribution: Rory Downes commentedHi,
I have the same issue as soon as I put the ThemeKey folder into sites\all\modules. As soon as I delete that folder the admin UI is available again. I tried ThemeKey 3.3 and the 3.x-dev releases. My environment is:
Windows 8.1
Wamp: Apache 2.2.22; PHP 5.4.3; MYSQL 5.5.24
Drupal 7.37
Jquery 1.10
This is the first time I have attempted to use ThemeKey.
Rory
Comment #25
mkalkbrennerOK, if I read through the comments it seems like the issue is somehow related to Windows or WAMP or PHP for Windows. Unfortunately that's something I can't reproduce because I don't use Windows.
So I suggest to schedule a chat on irc to some real-time debugging on one of your setups. Please contact me to schedule such a meeting. You'll find me on #drupal-contribute most of the time or use my contact form on drupal.org.
Comment #26
Rory Downes CreditAttribution: Rory Downes commentedThanks to a lot of work with you we have identified that a long description in the themekey-compat.info file caused the issue. We designed a shorter text:
Optionally move the theme switching capability of core and additional modules to the ThemeKey rule chain.
Looking forward to the dev release to test.
Rory
Comment #28
mkalkbrennerThanks for your time Rory to figure that out!