Re: Members-only pages implementation tips
Posted: Thu Feb 26, 2009 8:13 pm
CustomContent is indeed the way to provide the menu, based on the people being logged in...
The message you stated is still needed, as the pages are active and so they are calleable directly. Wo within the template, you could do a lttle {if } {else} to show the content when logged in, and the message without being logged in.
For the structure it is hard to say how deep you should go... You could either work with prefixes in the page_aliases and based on that, include it in the menu, when logged in, and exlude it when not (includeprefix and excludeprefix) are parameters in the menu-call.
Another option would be to put the groupname in the extra-field of a content-page, and modify the menu-template, to check for that field, to show/not show the page based on if the user belongs to the group that is filled in the field.
So depending on how many different groups you will define, there are options. If only one group, then I would go with the include/exclude prefix...
Ronny
The message you stated is still needed, as the pages are active and so they are calleable directly. Wo within the template, you could do a lttle {if } {else} to show the content when logged in, and the message without being logged in.
For the structure it is hard to say how deep you should go... You could either work with prefixes in the page_aliases and based on that, include it in the menu, when logged in, and exlude it when not (includeprefix and excludeprefix) are parameters in the menu-call.
Another option would be to put the groupname in the extra-field of a content-page, and modify the menu-template, to check for that field, to show/not show the page based on if the user belongs to the group that is filled in the field.
So depending on how many different groups you will define, there are options. If only one group, then I would go with the include/exclude prefix...
Ronny