Closed (fixed)
Project:
Curlypage
Version:
6.x-2.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
12 Jan 2010 at 10:51 UTC
Updated:
31 Jan 2010 at 01:20 UTC
Please consider a way to allow us to exclude a role from a curl. For example, if I want to automatically peel the ear to all of my registered and anonymous users, but not my editors or admins, I can't do that, because an editor role is also a registered user role. Once I configure an ear to show to registered users, everyone gets it.
Feature request aside, I love the new scheduler. Awesome work!
If you ever find a way to track impressions or click thrus, you will be my hero! Haha.
Comments
Comment #1
manfer commentedAdded exclusion for roles visibility settings and commited to CVS.
As I think the next packaging for dev releases wont take place till about 2010-Jan-13 00:00 UTC , it would be available on homepage after packaging is finished as 6.x-2.x-dev (2010-Jan-13).
It is easy to understand how it works, anyway...:
On module update don't forget to run update.php.
Comment #2
djudd commentedWow manfer, that was fast! Thank you so much for this feature, it will really help a lot in my environment!
Comment #3
djudd commentedmanfer, I love that we can exclude roles now, but is there a way to show a second curl to a different block of users?
If I have a curl that auto-opens, and I exclude the roles administrator, editor, premium, and reporter, can I then add a second curl that displays to just those roles but doesn't auto-open?
That's what I tried this morning, but the second version wouldn't load.
Comment #4
manfer commentedI have made a simple test on my test environment and seems to work.
Both works as expected for its respected users.
One setting is just the inverse of the other: show except some users, show only to those users (being careful with registered role). Are you configuring this logic?
In your case it is:
Take in mind that "registered" role was the problematic one. That's why you suggested the exclusion feature at first time. So, if I have roles: anonymous, registered, editor, administrator, these rules are not inverse though they could seem to be:
and these ones are not inverse either:
If you have configured the correct logic for roles, is there any other visibility configured on second curl that could do the curl not appear (languages or pages visibility settings)?
If it is no one of these reasons, please tell me and I would try to think what is wrong.
Comment #5
djudd commentedActually, it does work. I am running Boost and Authcache, and forgot to wait the 15 minutes for cache to clear. Sorry for that manfer, and thanks again for the new code. I love it.
Comment #6
manfer commented