Active
Project:
Path Rules
Version:
7.x-1.0
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
24 Mar 2014 at 07:50 UTC
Updated:
25 Oct 2017 at 23:36 UTC
Jump to comment: Most recent
If you create only 1 condition: Check path and fill it with URL, module works as intended, but when you add 1 more condition, e.g. "check user role" and select all needed roles, this module won't work.
Here's steps to reproduce:
1. Events: Drupal initialization
2. Conditions: Check path (set your url)
3. Conditions: Check user role (set your roles)
4. Actions: system redirect (set to front page url)
Comments
Comment #1
alexanderpas commentedAre you correctly nesting your conditions with and/or conditions?
Comment #2
mttjn commentedsame problem. yes, i am correctly nesting and/or conditions. the OP's steps to reproduce are accurate.
Comment #3
luxpir commentedWorks as designed here - I have:
1. Events: Drupal initialization
2. Conditions: Check user role (set multiple roles)
2.5. Add AND condition
3. Conditions: Check path (set register url)
4. Actions: system redirect (set to node create url)
So if the user already has the role, the register (profile2) field redirects to the node create page. It works fine. I have the AND condition between them and have reversed the conditions to check roles first.
Now I'm just wondering about site performance with this check running on every init...
Comment #4
plato1123 commentedI'm having same issue, unable to combine path rules with other rules. I've tried a variety of orders and ways of nesting (and I think I have it right but can't be 100%).