GET parameters break theme switching based on url aliases
Lenn-art - October 10, 2008 - 14:13
| Project: | ThemeKey |
| Version: | 6.x-1.2-beta4 |
| Component: | Code / API |
| Category: | bug report |
| Priority: | normal |
| Assigned: | mkalkbrenner |
| Status: | closed |
Jump to:
Description
I can select a different theme with http://foo.bar/news and http://foo.bar/news/newsarticle, just by adding at the path-tab news and news/%
But this puzzles me: how can i set up this kind of pages: http://foo.bar/news?page=1 ??? news% and news?% or news?page=# aren't working. Just using the right type under properties does also not work.
However, news?page=1 is just working ... hmm strange ... how do i use the wildcards?
Can someone help me with this?
#1
Im in the same boat here.
I have a node like so:
http://smapp02/cms/content/ember-map
This uses content/ember-map to switch the theme. Great, but If I use the node, the node changes itself somewhat like so:
http://smapp02/cms/content/ember-map?zoom=5&lat=64.49378&lon=-121.5&laye...
Now ThemeKey doesnt change the theme.
In a wildcard situation, I should have been able to add:
content/ember-map%
to get themekey to switch over regardless of the rest of the URL. or are wildcards in ThemeKey not like a wildcard in drupal?
content/ember-map% <> content/ember-map*
Franco
#2
You shouldnt need any additional wildcards in the path for this kind of url parameters at all.
Example: To switch the theme for a simple node (nid=20) you would enter 'node/20' for the path. Theme switches to the selected one. If you now add a parameter to the url, say 'node/20?abc=def' it works the same as before (without any change to the path).
#3
On drupal paths like 'node/20' it works like described at #2. The additional parameters are ignored for theme switching decision.
On aliased path the issue occurs like described in the issue and at #1.
#4
will be fixed in 6.x-1.2beta5
#5