Comments

mkalkbrenner’s picture

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.)

tannerjfco’s picture

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.

Explosivo22’s picture

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

tannerjfco’s picture

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.

mkalkbrenner’s picture

I just get that the page is unavailable.

This sounds like an apache or poxy error message. I assume that the request does not reach drupal at all.
Can you post a screenshot?

mkalkbrenner’s picture

Status: Active » Closed (cannot reproduce)

No feedback for weeks.

lekpanti’s picture

Version: 7.x-3.0 » 7.x-3.2
Issue summary: View changes

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.

mkalkbrenner’s picture

Seems like we missed one. If the issue occurs or not depends on the database's behavior

mkalkbrenner’s picture

Status: Closed (cannot reproduce) » Active

@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?

  • mkalkbrenner committed 48fe42a on 7.x-3.x
    Issue #2224913 by mkalkbrenner: removed single quotes from module...
mkalkbrenner’s picture

Title: Admin Interface broken » Admin Interface broken / Avoid single quotes in module descriptions
Category: Support request » Bug report
Status: Active » Needs review

I'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?

Chris Gillis’s picture

I'm also experiencing this error. Steps:

  1. drush dl themekey --dev
  2. /admin/modules returns ERR_CONNECTION_RESET
  3. Delete folder sites/all/modules/themekey
  4. /admin/modules displays normally

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.

Chris Gillis’s picture

Status: Needs review » Active
mkalkbrenner’s picture

@Chris Gillis:
Can you share some more information about your environment? (OS, PHP version, ...)
Any errors in PHP error log?

Chris Gillis’s picture

Running WAMP on Windows 8.1.
Apache 2.4.9.
PHP 5.5.12.

Error Log:

[17-Sep-2014 09:35:47 Australia/Brisbane] PHP Warning:  Invalid argument supplied for foreach() in C:\wamp\www\drupal\includes\module.inc on line 1079
[17-Sep-2014 09:35:47 Australia/Brisbane] PHP Stack trace:
[17-Sep-2014 09:35:47 Australia/Brisbane] PHP   1. {main}() C:\wamp\www\drupal\index.php:0
[17-Sep-2014 09:35:47 Australia/Brisbane] PHP   2. drupal_bootstrap() C:\wamp\www\drupal\index.php:20
[17-Sep-2014 09:35:47 Australia/Brisbane] PHP   3. _drupal_bootstrap_full() C:\wamp\www\drupal\includes\bootstrap.inc:2267
[17-Sep-2014 09:35:47 Australia/Brisbane] PHP   4. drupal_theme_initialize() C:\wamp\www\drupal\includes\common.inc:5156
[17-Sep-2014 09:35:47 Australia/Brisbane] PHP   5. _drupal_error_handler() C:\wamp\www\drupal\includes\common.inc:100
[17-Sep-2014 09:35:47 Australia/Brisbane] PHP   6. _drupal_error_handler_real() C:\wamp\www\drupal\includes\bootstrap.inc:2320
[17-Sep-2014 09:35:47 Australia/Brisbane] PHP   7. _drupal_log_error() C:\wamp\www\drupal\includes\errors.inc:75
[17-Sep-2014 09:35:47 Australia/Brisbane] PHP   8. watchdog() C:\wamp\www\drupal\includes\errors.inc:202
[17-Sep-2014 09:35:47 Australia/Brisbane] PHP   9. module_implements() C:\wamp\www\drupal\includes\bootstrap.inc:1741
[17-Sep-2014 09:35:47 Australia/Brisbane] PHP  10. drupal_alter() C:\wamp\www\drupal\includes\module.inc:750

  • mkalkbrenner committed 48fe42a on 8.x-1.x-playground
    Issue #2224913 by mkalkbrenner: removed single quotes from module...

  • mkalkbrenner committed 48fe42a on 8.x-1.x
    Issue #2224913 by mkalkbrenner: removed single quotes from module...
geraud.demareschal’s picture

I 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

mkalkbrenner’s picture

Priority: Normal » Major
Related issues: +#2385483: Unable to install - The connection is reset

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.

mkalkbrenner’s picture

Status: Active » Needs review

Did anyone test the latest dev? Is the problem solved?

Leeteq’s picture

That apostrophe is no longer present in that .info file in today's brand new 7.x-3.3 release.

mkalkbrenner’s picture

That apostrophe is no longer present in that .info file in today's brand new 7.x-3.3 release.

Yes, but does that fix your issues? I got no feedback so far.

cavilio’s picture

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.

Rory Downes’s picture

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

mkalkbrenner’s picture

Title: Admin Interface broken / Avoid single quotes in module descriptions » Admin Interface broken / Potential incompatibility with WAMP on Windows
Version: 7.x-3.2 » 7.x-3.x-dev
Assigned: Unassigned » mkalkbrenner
Priority: Major » Critical
Status: Needs review » Needs work

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.

Rory Downes’s picture

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

  • mkalkbrenner committed 8450fde on 7.x-3.x
    Issue #2224913 by Rory Downes, mkalkbrenner: Admin Interface broken /...
mkalkbrenner’s picture

Status: Needs work » Fixed

Thanks for your time Rory to figure that out!

  • mkalkbrenner committed cf47d83 on 7.x-3.x
    [#2224913] Rory Downes, mkalkbrenner: Admin Interface broken / Potential...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.