Naming conventions

The way that we are externalizing login requires that you follow certain naming conventions.  If you’ll recall in our example, there was a public site that was not password protected and a set of private sites that require that an end user login to get access.  Upon logging in, the end user is not sent into the Control Panel.  Instead, each end user is redirected to the right page for them based on their membership in a particular group.  Suppose you have clients each with their own secured area.  Your clients are called “Aclient”, “Bclient, and “Cclient.” 

Here are the naming conventions you must follow in order to get our hacks to work correctly:

The weblog_shortname must be a single word e.g. aclient

The weblog_longname must be that same word but you can capitalize it e.g. Aclient

The membership group corresponding to that weblog must be the same word e.g. aclient

The template group corresponding to the membership group and weblog must be the same word e.g. aclient

If you are creating a submembership group – for example for the R&D department within the client organization, you’d name that group like so:


The system will ignore everything after the underscore when determining where to send an end user after they log.  In this way, you can create multiple subgroups that can login and get to a set of secured pages.  You can then change preferences for the various templates within that group by hand and/or use if/else statements to customize the content displayed to “aclient” versus “aclient_randd”. 


Naming conventions
Scroll to top