Limit access to a membership page by current membership type?

[mclyde]

We currently have 2 membership pages;  we have a required membership in the organization and then optional memberships in "sections".
The organizational membership has several options: one year, 3 year and Lifetime.  We set up the second membership page for current members in the 3 year or Lifetime group to add an optional sectional membership. (so they did not accidently renew their 3 year or lifetime; yes despite warnings it did happen :-)

I would like to have the section only page accessible only to members who have 3 year or Lifetime memberships - is that possible through civi without serious coding?   would it be any easier to extract info using php to display the different urls to the different signup pages from a membership overview page? 

we're using price sets on both, so if access to a price set could be limited by membership types that would also do the trick and actually allow us to go back to one page

Thanks in advance!
Merlise
 

[Hershel]

I would like to have the section only page accessible only to members who have 3 year or Lifetime memberships - is that possible through civi without serious coding?

I don't think so.

would it be any easier to extract info using php to display the different urls to the different signup pages from a membership overview page? 

Might be a bit easier but it doesn't actually protect the other pages. But for a non-secure, low-tech solution, that would work.

[NASACT]

I guess a work around would be that those are membership types and then you can use ACL to control access based on current rather then trying to complicate things.  Just my thoughts on this.

[mclyde]

NASCT - would you elaborate?   I was not aware that you could use ACL  to limit access to specific  contribution pages in civi. 

So I would create an ACL role based on  everyone with a Lifetime membership (but that is a dynamic smart group, not a static group) so civi ACL doesn't seem to be able to access the group. 

and then I could create a rule that allows only them to access  a contribution page with a specific id    I don;t see where that is an option ?

thanks,
Merlise

[NASACT]

Sorry for the confusion, I don't think you can limit access to membership pages but I know Pete said there was a way to limit membership renewal to those already with a specific membership type. But I digress.  I thought you were referring to content within the site and using ACL for current members or those with a particular tag, say 3 years is a new tag and then smart group then assign ACL based on smart group.  Sorry again for the confusion.

[Hershel]

I would like to have the section only page accessible only to members who have 3 year or Lifetime memberships - is that possible through civi without serious coding? 

It depends on what "serious coding" means.

It's actually not hard at all to code this as a Drupal module.

[mclyde]

Hmm I still cannot see where to allow a smart group to have a ACL role.  (I'm running 4.1.2 and D6)

On the Manage Groups: Group Settings page the only Group types available for smart groups are Mailing List.  (this is true for creating a new smart group)

For static groups the Group type access control is an option,

Under the  Administer -> User and Permissions -> Access Control page  I can only grant ACL Roles to the static groups. ( which is what the documentation for 4.1 indicates under limitations)   

 Is the smart group ACL a feature in 4.2?   Any chance a given contribution page could have access based on a civi  ACL? 

[mclyde]

Hi Hershel,

writing a Drupal module is getting into serious programming for me as my php is pretty limited and I while I can understand basic code with the Drupal/Civi API starting from scratch is still daunting!

I am using member pricesets, so is it feasible to have a hook that limits a specific price field  in a specific price set to a given membertype?       That way I do not neeed to limit access to the page but just the membership options.     

best,
Merlise

[NASACT]

You have to turn on OG Sync in CiviCRM module on Drupal side, it's off by default.  Then you map an organic group (call it the same if you wish) to the CiviCRM Smart Group.  Not sure if there is any Cron you have to setup for the sync or not.