I need to set up a site where there are five tiers of membership. Each successive tier of membership would have access to content for that membership tier, in addition to content on all tiers below that level.
From what I gather from the docs, "there is only one security level for members, so it does not matter which membership level they are, as long as they are a member they will have access to members only pages." This seems to imply that someone at the bottom tier of membership would have the same access to material at the top tier of membership.
Do I have that right?
If so, thinking of workarounds, could a subdomain be created for each membership tier that would only allow those members in?
You're correct that — in NationBuilder — being a member is a binary state: you either are or you are not a member. While NationBuilder allows you to sell various membership levels, the database doesn't recognize those various levels as distinct and different from a permissions level. That means that if you make a page viewable to "Members" it will be viewable to all members, equally.
There's really no good workaround for this that's based on membership level of which I am aware. You can, however, use conditional liquid tags to display different content on a given page to logged-in users depending on what tags their NationBuilder profile has. Since each membership level can be configured to automatically tag people, this method could be employed to display different content to individuals who have different membership levels (or none at all).
Showing 8 reactions
Sign in with
Hines Digital
Certified Architect
Certified Expert
{% if request.current_signup.tag_list contains "M-OTL" %} <p><a title="TITLE" href="LINK_URL" target="_self">LINK LABEL</a></p> {% endif %}I’m not happy hard-coding variable stuff in the template, but that seems to be the only option to achieve this goal.
The following code takes care of issue 1:
{% if request.current_signup.tag_list contains "M-" %} {% for child in site.supporter_pages %} <li> <a href="%7B%7B%20child.url%20%7D%7D">{{ child.icon | icon }} {{ child.name }}</a> </li> {% endfor %} {% else %} {% for child in site.supporter_pages %} {% if child.url != "/otool_download" %} <li> <a href="%7B%7B%20child.url%20%7D%7D">{{ child.icon | icon }} {{ child.name }}</a> </li> {% endif %} {% endfor %} {% endif %}The first “if” checks to see if the current user has a tag starting with “M-”. This means that all Membership tags have to start with these characters. If they do (they are a member) then they see the usual Supporter Nav. If the do not (they are NOT a member) then the page with URL of “/otool_download” is knocked out of the <li> series.
It’s kludgey and not robust, but it works. Tomorrow I will tackle requirement 2.</li>
Tim Wayne
Certified Architect
Certified Expert
Tim Wayne
Certified Architect
Certified Expert