Hi atherrien,

I'm a bit puzzled about what you are actually trying to achieve. Can you spell out the scenario a bit clearer?

Don't forget that at the end of any rule you can trigger the succeed (or fail) action but still continue to the next rule. Perhaps that might help?

The standard way to use a landing variable and to make it stick for the rest of the session is this:

1st rule: detect session variable A. In succeed action: set template and stop processing

2nd rule: detect "landing=x" in the URL. In succeed action: set template, and set session variable A.

In this way, if the person goes to a "landing=x" page then it sets the session variable. On the next page the session variable will be detected in rule 1, and the template will be set (and this will continue for the rest of the session).

If you want to give people the ability to cancel the new template using a URL with "landing=y", then you could do the following:

1st rule: detect "landing=y". In succeed action: reset session variable A and stop processing. Then the person just gets the normal default template. IN fail action, continue to next rule.

2nd rule: detect session variable A. In succeed action: set template and stop processing. In fail action, continue to next rule.

3rd rule: detect "landing=x" in the URL. In succeed action: set template, and set session variable A.


I don't know if that helps... but I hope so.

Cheers,
Stephen

Please reply my post asap as I need this to complete the production.

Thanks,
Alex

Ok, I logged in to your site and got it working. It took a little experimentation to get it right, and the new "debug" mode made it a lot easier too. Did you know about that? You can turn it on from the "Parameters" button on the MetaTemplate rules page. Then, each page that you view has a panel on it that lists each of the steps that MetaTemplate goes through. This helped to remind me that when you set a new session variable you have to cancel any old ones as well, or else they trigger some of the other rules...

Anyway, here's final order of the steps, and their actions. It's a bit different to what I said before (sorry).

Step 1: "Detect Landing=1 set Metal Template + set variable A"
In the SUCCEED action, you have to do 2 things with the session variables. In the first dropdown, "delete session variables A-D" and in the second "set session variable A".
In the SUCCEED action, set the appropriate template, and "stop processing".
In the FAIL action, "continue to next rule".

Step 2: "Detect Landing=2 set Femme Template + set variable B"
Do the same as in the 1st rule, including deleting the session variables A-D. Then set variable A and stop processing.
In the FAIL action, "continue to next rule".

Step 3: "Detect Variable A and set Metal Template"
In the SUCCEED action, set the appropriate template, and "stop processing".
In the FAIL action, "continue to next rule".

Step 4: "Detect Variable B and set Femme Template"
In the SUCCEED action, set the appropriate template, and "stop processing".
In the FAIL action, "continue to next rule".


I hope that all makes sense now. Please let me know if you need any clarification.

One of the important things was to detect the "landing=x" in the URL before relying on the session variables, otherwise you couldn't change to a different "landing=..." value. So all the "landing=..." rules go first.


Best regards,
Stephen

One last thing... sorry about that:

I have 5 templates thus in need of 5 variables. Could you provide me the mod info so I could edit one of your code file and add "Variable E" in the rule menu?

Or maybe there's a simpler alternative?

Thanks

Great! I hope you will go for the second option... LOL

I really appreciate your fast reply.

Cheers, Alex