The idea is Section 1 contains a form to register to see content. Section 2 contains the content. The form redirects back to the page with a parameter and a cookie set that hides Section 1 and shows the content they registered for in Section 2. (Using both parameter and cookie rules so they will definitely get the content even if they have all cookies blocked.) I’ve done parameter-based show/hide rules before without issue, but this is giving me trouble. And I’m not super familiar with the new cookie dc elements but I’m excited to try!
Section 1:
Should show if the user a) does not have a cookie b) does not have a parameter.
For cookies, I have tried -
- {{dc:cookie:get name=“archive_access”}} is not yes
- {{dc:cookie:get name=“archive_access”}} is blank
For parameters I have tried -
- {{dc:url:param key=“wkpass”}} is blank
- y not in {{dc:url:param key=“wkpass”}}
- y is not {{dc:url:param key=“wkpass”}}
- {{dc:url:param key=“wkpass”}} is not y
Section 2 should show if a) the user has a cookie b) user has a parameter that equals y.
This rule works:
- {{dc:url:param key=“wkpass”}} is y
These rules do not work:
- {{dc:cookie:get name=“archive_access”}} is yes
- {{dc:cookie:get name=“archive_access”}} is not blank
So to summarize: Section 1 rules don’t work at all, Section 2 rule works for parameter but not for cookie.
I tested by visiting the page with and without the parameter set. And I manually set the cookie and refreshed, confirming it was still there each time. (testing by form submission was going to be phase 2 of testing.)
I can live without the cookie rule if they don’t work that way, but the parameter rule not hiding Section 1 is challenging. Is this just a syntax thing I goofed up? Cache issue? (I can disable cache for this page if that helps!) I’ll reply with access info in case this sounds buggy and not like standard user error. 
