Posted by protoplasm on September 10, 2010 at 12:39am
3 followers
Jump to:
| Project: | ThemeKey Properties |
| Version: | 6.x-2.3 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | mkalkbrenner |
| Status: | closed (cannot reproduce) |
Issue Summary
I've used themekey rather successfully in the recent past and am very grateful for this module and themekey properties. I am stuck on making a cascading rule set work with wildcards. Here is the type of path I'd like to theme only the organic group ID will change and the search terms will change:
og/search/6968?keys=clubs
I can theme this exact page using drupal_get_q for og/search/6968 and system query param keys=clubs. But using wildcards like og/search/# and keys=% just doesn't work. I'm sure it's something obvious I'm missing. Any clues would be greatly appreciated.
Thanx
Comments
#1
Ok, development server is php 5.3 and apparently was causing the issue. The solution was a simple og/search/% once the problem with php 5.3 became apparent. Even so, I'd love to see more documentation on the use of the autoloader wildcard with themekey in conjunction with subsequent additional child calls.
#2
Sounds strange that php 5.3 should have caused the issue. Did you debug your rules using ThemeKey Debug?
Wildcards only exist for paths, p.e.
drupal:path = og/search/#og_idFor query params you could use an regular expression:
system:query_param ~ /keys=.*/Did you read the included ThemeKey tutorials and properties explained?
#3
Yes, I used themekey debug and that is how I figured out how to make it work for the exact URL. Yes, I read the tutorials that I found and explained properties, but I don't recall finding the key piece of information--that query_param uses regular expressions with a tilde operator. Thanks, that's exactly what I was missing!
The error message I received about parameter 1 being a value instead of a reference that I found in watchdog on some of my wildcard attempts seems to be a known problem related to the use of php 5.3 with autoloader wildcards if I am recalling correctly.
#4
Thanks for your feedback. I'll try to reproduce that warnings with PHP 5.3
#5
#6
Desired using selected theme for each "new forum topic" page
1. drupal:path node/add/forum/#tid works
2. drupal:path node/add/forum/#tid
2.1 drupal:path:wildcard tid > 0 => template1 works
What if doesn't work?
Use administration theme for content editing?
goto admin/settings/admin
uncheck Use administration theme for content editing
click Save settings
Still doesn't work?
Turn on debugging
goto admin/build/modules
check ThemeKey Debug
click Save settings
goto admin/settings/themekey/settings/debug
check Show values of ThemeKey properties
check Trace ThemeKey rule switching
click Save settings
#7
nice explaination
#8