Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.After testing for quite a while, it seems path wildcards are broken - or at least I have no chance at getting it to work.
I have added a path play/# (also tried play/%) with operator > and value 0 - it never switches the theme.
I also encountered an issue after deleting the play/% -- which made it impossible to add a new entry using the interface (interface said my new rule was stored, but nothing happened); so I had to manually add an extra line in the database to get something to work with again.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | themekey.jpg | 71.28 KB | 2xe |
Comments
Comment #1
mkalkbrennerThis sound strange to me because the value should be 'play/#' and not '0'. Could you please provide a screen shot of your rule chain?
Comment #2
2xe commentedI've been testing a bit more, but still can't make the path wildcard rule work; I managed to add an entry by using the second textfield to write the "listen/%" rule. I've tried multiple options for the comparison operators; none of them seem to make any difference - or at least, none of them make my callback switch the theme. My other rule (node:type) works like a charm.
Comment #3
mkalkbrennerYour property needs to be "drupal:path" and not "drupal:path:wildcard":
if you "name" the wildcard in the rule above you can access it later in the rule chain:
see #676322: wildcard handling for path aliases is broken
Comment #4
2xe commentedThanks. Sorry for not checking the issue history good enough. This solved my issue - thanx.