It sounds like you’re just blocking one page, in which case you don’t really need the login form shortcode – that’s only if you need a dedicated login page. Blocked content will be replaced with a login form by default, so all you need to do is make sure the page is blocked.
If you do not want a register link in the login form, that is created by setting the location of a registration page in the plugin’s main options, so unset that setting if you don’t want the link.
I would recommend taking a look at the initial setup video here:
https://rocketgeek.com/plugins/wp-members/docs/videos/
Thanks, Chad, but I’m not sure I understand. I have seven individuals for whom I created wp-member identities and assigned passwords. These are the seven currently in the band. Wen they choose the Bandmates Only option from the top menu they will get access to a list of well over a hundred downloadable pieces of sheet music– but only if they can supply a password. What I thought I was aiming for was: the guitarist clicks Bandmates only. A password challenge appears. S/he puts in the username and password. The sheet music page appears.
In this way only the seven band members I’ve allowed will be able to access it.
As I watch the video you recommend, it is mainly based on blogs, not static web pages, though I’m sure that both could be handled by this. One problem is that the video examples are all dated Sept. 17, 2008. I have the most recent version of the plugin, which I downloaded only a couple of weeks ago.
I am beginning to think that this may not be the plugin for me, for the simple and straightforward task I need it for, and that I should be scouting out other membership plugins.
I will continue trying to implement the one I have, and will pay close attention to rocket geek documentation. But meanwhile, if you or any other readers have a recommendation for another plugin that might be better for my need, I’d certainly be interested and grateful to hear about it.
Don’t overthink it. The plugin is extremely simple to set up and what you’re doing it a very basic implementation of it.
All you need is to set the restriction for the one page you’re trying to block. That setting is in the upper right of the post/page editor. Set it to “block”. At that point, a user will need to log in to view the page’s content.
One problem is that the video examples are all dated Sept. 17, 2008.
That’s only the date on the posts in the demo site (which is imported data). It doesn’t have anything to do with when the video was created or what version is being used.
