Hi,

Is this a working version of a module? I can only get ThemeKey to change the theme on an empty url, i.e. a url that I haven't even created content for yet in Drupal.

After I've made a page and want to change its theme, I go to Site Configuration > ThemeKey Paths or Properties. Setting a Node or URL alias to have a different theme, e.g. Garland, then pushing Save Configuration does nothing. It does not work at all for a pre-made Drupal page. I've tried viewing the page logged in as Admin and outside Drupal as an anonymous user (also deleted Cache in Firefox).

Also, going to Content Management >Content >Edit for the page, then finding the Theme field and changing it to the different Theme, then Saving it, does not work either. I still have the same default theme no matter what. Hoping someone out there can fix this for next time. I'm using Drupal 6.1.

Comments

wpanssi’s picture

I can confirm this behaviour. I can make it work for just predefined paths like node/add. Using clean urls and path redirect. Would be awesome module, but doesn't seem to work!

greg.harvey’s picture

Works fine for us, which is weird. Haven't tried it with a pathauto generated alias, but logically there should be no difference...? We have one page created by us, as a registered menu item using hook_menu (which is what you mean by "predefined paths), aliased three times with three different themes and it works great!?

profix898’s picture

Status: Active » Postponed (maintainer needs more info)

Can you please try the latest development version of themekey. The module has been updated with some heavy modifications and I'm unable to reproduce the problem you reported above for (at least) the newest version.

noymen’s picture

Possibly cause of bug in other module using js for example Lightbox. I have turn off all modules with JS and themes began to be switched.

noymen’s picture

p.s. It was the conflict with Meta_tags.

greg.harvey’s picture

Title: Doesn't work for node or pathauto aliases » Some other contributed modules seem to break themekey for node or pathauto aliases
Assigned: cloudrider9@gmail.com » Unassigned
Status: Postponed (maintainer needs more info) » Active

Ok - I think that constitutes "more info"... changing title and setting back to Active. Someone should investigate *why* meta_tags and themekey don't play nicely... ;-)

If the initial two posters are still having problems, they need to try the latest stable version on a clean Drupal installation. If it works fine, time to start figuring out which other contrib you are using is breaking it! Come back if you find more modules. =)

Ps - this might not mean a fix for ThemeKey - it might be that ThemeKey is fine, for example, and meta_tags does something bad. For now this is an investigative task for someone who has the time.

profix898’s picture

Status: Active » Postponed (maintainer needs more info)

I just installed MetaTags 6.x-1.0 but it doesnt seem to break ThemeKey ... A story node with a theme assigned via the 'node:nid' property still works as expected.

mkalkbrenner’s picture

Status: Postponed (maintainer needs more info) » Active

I fixed a lot of bugs in ThemeKey that might caused conflicts with other modules. Is there anybody who could confirm that this issue still exists? Otherwise I will close this issue because I'm not able to reproduce it and use the combination of nodewords (Meta_Tags) and ThemeKey on different sites.

dagdag’s picture

Hi i was trying to use this module but no way to make it work, I do not if I doing some wrong

drupal 6.14
URL alter 6.x-1.2
Pathauto 6.x-1.2
Sub-path URL Aliases 6.x-1.1
Sections 6.x-1.2 but section is disabled
ThemeKey 6.x-1.2-beta5

I try to set to a node:type but was impossible to work, the theme doesn't change, I also test the themekey properties but nothing. even with a example from the README but nothing!

mkalkbrenner’s picture

I tested the combination of these latest modules:
drupal 6.14
url_alter 6.x-1.2
pathauto 6.x-1.2
subpath_alias 6.x-1.1
nodewords 6.x-1.2
themekey 6.x-1.2-beta6

I checked different theme switching rules. Especially those switching on paths created by pathauto or subpath_alias. Everything works well.

What happens if you install ThemeKey Properties and turn on debugging?

mkalkbrenner’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

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