A Tale of Two Members’ Areas

No memberNo cookie found
No memberName cookie found
No memberStatus cookie found
No loginDate cookie found

2. You are not logged in.

4. Your membership is not current.

6. Your membership is not lapsed.


To allow BAHS members to login to the original members’ area using their individual login (email address) they need to use this link:

Link to (original) members’ area

The original members’ area is technically part of the membership system which is part of the BAHS website but separate to the WordPress part of the website which is what visitors to the website use.

Original Members’ Area

The original members’ area provides the ability for members to login and check their subscription status and history as well as update their contact details (address, email, password,…) which can reduce the workload of the membership secretary. When new members join they are directed to this to update their temporary password. The membership system also provides options to allow committee members to update the email addresses, passwords etc of members or to block them if need be from the members’ area.

Second Members’ Area

Sarah introduced a second members’ area which replaced the link to the original members’ area as the original members’ area was not something she could make changes to. However this is really a shared resources area as it is accessed uses a password that all members must use. However this has some problems:

  1. It no longer provides access to the original members’ area and has confused new members who receive emails about changes of passwords;
  2. the password entry needs to be on every page that provides access to these shared resources (i.e all pages that are part of this shared resource area needs to be a protected page within WordPress). To illustrate why click here to view the latest Glaven Historian with entering a password.

Going Forward

Really what is needed is a bit of both members’ areas with some communication from the original members’s area to the shared resources members’s area to indicate the user is logged in or not logged in.

  1. the original members’s area is brought in from the cold abd is responsible for managing individual logins and access to functions such as updating personal details and subscription status and history – that is functions performed by tge membership system;
  2. a shared members’ resources area where members gain access (if logged in above) to newsletters, AGM papers, the latest Glaven Historian and other resources which can be provided by the WordPress part of the website and may offer this to any member who is logged in – and to do this is straightforward for those maintaining the website.

Using Shortcodes

So members will login to the original (but simplified) members’ area to access these functions mentioned above. There will a be link provided to a shared resources area which is really an update of the current members’ area with the removal of the protected password page. However each WordPress page in the shared resources area (newsletter, AGM paper, latest GH plus any future additions) will use the shortcode pairs listed below to control the information displayed on these pages when a member is logged in or what is displayed when not logged in. These shortcode pairs are added to WordPress by me as a new plugin.

  • Anything between the shortcodes pair [ is_logged_in ] and [ /is_logged_in ] will only appear on the web page if the user is logged in.
  • Anything between the shortcodes pair [ is_not_logged_in ] and [ /is_not_logged_in ] will only appear on the web page if the user is not logged in.
  • Anything outside these shortcode pairs will always appear on the web page.
  • Note: WordPress shortcodes do not have a space after the opening square bracket or before the closing square bracket – this is a peculiarity of getting WordPress to display a shortcode and not use it.

You are not logged in as a member. Members may login ‘link’ (to be created).

No more details displayed as file doesn’t exist.

Anything after [/is_logged_in] will always appear on the web page