Conditional Redirect contains a highly configurable condition engine capable of evaluating single conditions or multiple conditions within a single Conditional Redirect attribute and even evaluating multiple Conditional Redirect attributes.
Conditional Redirect is pre-configured for up to 5 conditions within a single Conditional Redirect attribute.
This number of conditions can be configured in application/config/ at jl_conditional_redirect.condition_engine.max_conditions
Multiple conditions are either all OR or all AND.
Conditional Redirect is pre-configured for a single attribute. The processing of multiple attributes can be configured at jl_conditional_redirect.conditional_redirect_mode which can have the values single_attribute (default) or multi_attribute.
When multi_attribute is configured, all Conditional Redirect attributes for a page are executed in alphabetical sequence. The first redirect ends that sequence. This should not be configured unless you actually need it as it presents an overhead for all pages, not just those with the attribute.
Page caching could have unexpected consequences for evaluation of Conditional Redirect. If in doubt about whether a condition evaluation could be skewed by the page cache, the page cache is best disabled for any pages using one or more Conditional Redirect attributes.
You can leave the page cache enabled for other pages.
Conditional Redirect in not a substitute for page permission. If you need genuine security, require users to register and login and use page permission to determine what pages they can see.