Plugin not restricting content

I went with a different plugin. This was not working at all with Avada.

I have it set to be the login page in the settings and on the page itself, I have marked it as Restricted. Why is it not being blocked?

Because you set that page to actually be the login page. A page can’t be both the login page AND a restricted content page.

Certainly, you can set things up that way – manually applying the login form along with restricted content. But when you set the plugin’s option to identify a login page as the login page, that page cannot be set as restricted because as the login page, it has certain functionality that it needs to be able to do. (There’s more to it than that, but there’s not really a need to go into the technical aspects in this answer.)

When you restrict a page, you don’t have to implement the login form manually – it’s done automatically. And for this particular plugin, the login page cannot be a page that is restricted.

Note that while this is noted in the plugin’s documentation, it was not noted specifically on the page regarding the login page. I have updated that accordingly so that this is more clear to users in the future.

• This reply was modified 1 year, 3 months ago by Chad Butler.