simplenews_roles currently enforces membership for a certain role.
We have optional newsletter lists that need a certain permission level.
What we need is assigning a role to a newsletter tid to allow subscription -- while unpermitted users won't be able to (and get auto unsubscribed on role loss.)

This is some kind of access controle..
Would you consider this as a feature to welcome? -- And how would you prefer adding the admin

Miro

Comments

joachim’s picture

joachim commented
Status: Active » Closed (won't fix)

I would have two roles in this case, and some users have both and some users only have one. That would be simpler than adding extra options and UI to this module.

miro_dietiker’s picture

miro_dietiker
Location Switzerland
commented
Status: Closed (won't fix) » Active

joachim i don't really understand how you would prefer the solution. can you please specify in some more detail?

We have currently no module and no option to make newsletters with restricted rolebased access.
we only have open newsletters, hidden newsletters, and autosubscribed newsletters.

I'm looking for a way to add permissions per role to limit subscribe capability for certain roles. this will need some additional ui clutter.

One way would be to have per-role settings for a newsletter. but instead of 1 checkbox it should be a table:
One line per role, first column is visibility per role (which makes only sense for non-hidden newsletters), second is autosync per role (which might be also in conjunction with newsletter options).

It's still an option to have two different modules for different per-role settings. But i'd much more appreciate to add them into one module it it makes any sense.

Or is there something like a general taxonomy access permission module that will perfectly work for simplenews taxonomy access limitation on a per-role basis?

Thanks for your answer.

joachim’s picture

joachim commented
Status: Active » Closed (won't fix)

This sounds like a more general feature -- the ability to say which roles may subscribe to a particular newsletter.

That is independent of this module's purpose; furthermore, it could be a feature that's needed without any automated subscription. That's why I'm marking this as wontfix.

You'd have a hypothetical simplenews_access module which lets you say 'Users in any role may sign up to Newsletter A, but only users in the Premium role may sign up to the Newsletter B'.
Alternatively, it could be implemented in simplenews core.

miro_dietiker’s picture

miro_dietiker
Location Switzerland
commented

Thanks for your opinion. We didn't want to add more and more related modules as long as some maintainers have similar focusses.

joachim’s picture

joachim commented

That's a laudable aim. :)

I think in this case, the concepts of 'Who may manually subscribe themselves?' and 'Who is automatically subscribed' fall nicely into different modules.

edmonkey’s picture

edmonkey commented

Having a play round with TAC-lite and node_privacy_byrole you can achieve limiting users of certain roles to only be able to subscribe (and view) certain newsletters.

example:
Newsletter A - authenticated users(role1) can see/subscribe with vocab 'newsletter' and taxonomy 'Everyone'
Newsletter B - only 'member' (role2) can see/subscribe with vocab 'newsletter' and taxonomy 'Private'

I did this by:
1)node_privacy_byrole - setting access control in newsletter node type to allow no roles to see this node type (the hides all newsletters)

2)Tac-lite then uses a scheme based on vocab 'newsletter' and allows role1 to view only content with taxonomy 'Everyone'. And same scheme allows role2 to view 'Private' based taxonomy.

This also seems to hide newsletters that a user can't join in the user profile.
Also hides content properly for unauthorised users (due to TAC)
drup 6.17, tac_lite-6.x-1.3 , node privacy byrole 6.x-1.5, simplenews 6.x-2.x-dev and simplenews-roles 6.x-2.x-dev

hope that helps!