password-based page restriction

> As a freelancer I am creating a wedding website for friends

imo, you need to use a Membership plugin, and a Role Manager.

You are overcomplicating things with too much customization.

Just use this :
https://en-ca.www.ads-software.com/plugins/ultimate-member/
plus this :
https://en-ca.www.ads-software.com/plugins/user-role-editor/

and you’ll be good to go.

Create Roles for the Bride/Groom –> Guests –> Visitors
Assign Permissions to Categories or Pages within the site to those Roles based on the hierarchy.

– I want a welcome page with a “Password” field
– There are 2 passwords possible: password1 and password2
– password1 allows to access the content for guest-group1, and password2 allows site-visitors to access content for guest-group2 (who e.g. will take part to the reception dinner, whereas guest-group1 won’t see any reception dinner detail)

(Emphasis mine)

Corrinarusso’s suggestion is the ideal way to go if each “group” area has MULTIPLE PAGES of content.

But if all that each “group” sees is a single page of information (you mentioned “who will take part in reception dinner” and “any reception dinner details”) then I’ll dumb this waaaaaaaaaaay down and simply use WordPress’ native password-protection page feature.

Create a PAGE for each “group” and password-protect it. Note that this is a built-in feature of WordPress — you don’t need any external tool to password-protect a page. Then create your “Welcome” PAGE and have buttons/links on it with messaging directing members of each group to click the appropriate button.

Once members land on their respective pages, they can then enter the group’s page password to view their group’s information.

As I mentioned earlier, this only makes sense if each “group” has just a single page of information. If this is not the case, use a membership plugin as already advised by Corrinarusso.

@corrinarusso
Thank you for your idea, I probably need to study better your solution again. I already looked into a “member” option, but I really want to avoid for visitor to have to register themselves, create a log in etc.
Maybe I don’t understand enough about it in order to avoid this with such a solution?

@gappiah

As there are a few pages that would be “in common” for both groups, your solution would imply creating those pages in double. A little complicated later in the update and maintenance.

I am currently using a plugin called “smart passworded pages” which helps already with my logic but doesn’t solve the problem entirely: the visitor lands on a welcome page, with “password1” gets on “page-for-password1” and from there he can get to a common page (e.g. Gallery) via button or navigation. But when he wants to hit back, he lands again on the welcome page and needs to enter password1 again – not such a nice user experience! And I haven’t been able to find a way to cache this password ??

• This reply was modified 3 years, 9 months ago by Francesca.

@gappiah
That’s a solution to the ‘problem’ – yes.
But as we all know – when the client see what they asked for, they then continue to ask for 14 more things. And it will get super complicated and start to break very quickly. This approach is far too single focused.

@sunniersky
> I am currently using a plugin which helps but doesn’t solve the problem
That’s bc you are only focused on one thing.

> I want to avoid for visitor to have to register themselves
Why?
If you think it’s too tedious for people, then use a Social Login plugin to make it easier for people:
https://en-ca.www.ads-software.com/plugins/miniorange-login-openid/
https://en-ca.www.ads-software.com/plugins/nextend-facebook-connect/

The path you are going down now has no scale / room for growth.
The maintenance will be a mess, and the Bride is gonna start asking for loads of other stuff that she hadn’t thought of until she see it in action.

Just do it properly.
Would you build a house with a poor foundation?

My 2 cents!