Problem/Motivation

I'd like to "chain" redirects once a user has registered - sort of required actions post registration.

For example:

User A registers as an Author. Rules dictates that immediately after this, User A goes to "node/story/add". Once this is done, User A is sent to "select-favourite-authors" etc.

Is this at all possible with rules or am I completely out of it?

Thanks for the help :)

Comments

AntiThesis’s picture

AntiThesis CreditAttribution: AntiThesis commented

Alright, I've established that having two redirects in the actions certainly doesn't work. I suppose what would be needed is some way of seeing whether the user has submitted or moved on from the original redirect.

TR’s picture

TR CreditAttribution: TR commented
Issue summary: View changes
Status: Active » Closed (works as designed)

User A registers as an Author. Rules dictates that immediately after this, User A goes to "node/story/add". Once this is done, User A is sent to "select-favourite-authors" etc.

Rules can definitely do this, but a large part of it has to be your data model design. Where do you keep track of which steps the user has completed, and which step is next? One way to do this is with the workflow module, but you can also do it yourself by adding a "step" field to the user entity which keeps track of what step is next for the user. Then write a rule for each step transition, triggered by the expected action (e.g. "New story is created") and include a condition "if user is on step n", then redirect to the next step.