February 13, 2018 at 10:12 am #132209
I have been using the Svtle template for some time now to create landing pages within my WordPress site using the plugin Landing Pages. Entry to the WordPress site itself requires registration or a Facebook login. However, using a password shared among a group of conference delegates, I also want to separately password protect a single landing page within my site, once delegates are logged onto the site. I had thought that this should have been an extremely straightforward arrangement. In particular, the top menu item ‘Edit landing page’ for my page of interest provides me with access to the following options:
“Visibility: Password protected”,
which I have chosen, including the desired password.
However, anyone who logs onto my site can access the password protected page without any prompt for a password. I am puzzled about this. I would be grateful for advice on how to correct the problem so that I can make good use of password protection for a single page.
Many thanks in advance!February 13, 2018 at 4:23 pm #132215
I looked into it and found a partial solution. It will display the password prompt if needed, but it’s bare minimum in styling. It would take custom development to craft a better template for handling password requests, which I can refer you to a good agency if needed.
I can have the change in the next release, but here are the documented changes if you’d like to add them in manually:
Hope this helps!February 14, 2018 at 10:06 am #132228
Thanks for replying so promptly. Could you help me further, please, by explaining exactly what the user will experience after I implement this code. Also, unfortunately, I do not really understand the annotating comments and in one case, they are running off the screen. Would it be possible, please, for you to specify the exact code that I need for the purpose I explained by including the password in the code where it is needed? More precisely, I am not able to distinguish those cases where I am supposed to use the text “password” from those cases where I should use the actual password. Let’s assume that the password is Fido. Perhaps you can include this password in the code where it should appear as such.
I’m sorry that I need more advice but one little error can cause one big problem!February 14, 2018 at 3:55 pm #132234
No worries I have an easier way.
Are you using Inbound Pro plugin or Landing Pages stand alone?
If stand alone, find this file:
(1st create a backup)
And then completely replace the original’s contents with the contents of this file:
And then the password feature will work and you’ll see it’s limitations. It’s not pretty, very simplistic, but it does serve as a gate.
Alternatively there might be a good 3rd party plugin you could use. I haven’t done much research on it though.February 15, 2018 at 1:04 am #132237
Thanks for the first simpler solution you suggest. I appear to be using the stand-alone version of Landing Pages rather than the pro version. However, I also have the Landing Pages extension Use Landing Page as Homepage activated. Therefore, I would like to confirm in the first instance that copy-pasting the new code in the way you have suggested will not cause a problem with the functionality of the above extension. Can you please advise on this matter.February 15, 2018 at 7:43 pm #132241
The instructions I gave above were for landing pages alone so you should be okay. Just remember to back up before making any changes for extra safety.
Hudson AtwellFebruary 16, 2018 at 4:14 am #132247
Many thanks for this reassuring reply. I am very happy with the result of implementing the new code – simple and does the job!February 16, 2018 at 3:16 pm #132252
Fantastic news. Welcome, np.
You must be logged in to reply to this topic.