• I am trying to protect a WordPress page on my site. I have done this before quite easily, but I cannot do it now. Something has changed. I have done a lot of Google searching to get information, but everything I find seems to be out-of date. There are plugins that can do this, but they require signing up for a regular payment. I am not going to pay for something that should be free and easy. Can anybody help? Thanks

    The page I need help with: [log in to see the link]

Viewing 11 replies - 1 through 11 (of 11 total)
  • Using the new editor, that option has moved (no idea why…). It’s now under the ‘Status’ for the page. When you click on ‘Published’, or ‘Draft’, or whatever the status of the page is, it will bring up a pop-up window with the status, and the option to password-protect that page is right at the bottom of that window.

    Thread Starter omahajoe74

    (@omahajoe74)

    Thanks for the quick reply. However, when I click on the “Published” status, there is no pop-up window and no option to password-protect that page at the bottom right. Is there some setting I need to change to get that pop-up? As far as I know, all the site settings are at the default level.

    That’s how it is out-of-the-box, so there’s nothing that should be stopping it. This s what I see.

    View post on imgur.com

    If you’re not seeing the same, then it means that either a plugin or your theme is blocking that somehow so you’ll need to go through the standard debugging processes to find out what is doing that. Normally that means reverting to a default WP theme, and disabling plugins one-by-one until you find out which one is the cause of the problem.

    Thread Starter omahajoe74

    (@omahajoe74)

    I have always used a default WP theme. I only have 4 plugins, and I disabled all of them, but I still do not see the popup window that you see. Any other suggestions?

    At this point, no. It might be that you’ve got some JavaScript problem that can’t be seen from here, or there’s something else going on. Hopefully someone else might be able to help more.

    Thread Starter omahajoe74

    (@omahajoe74)

    I appreciate your efforts to help me. My site is a simple travel blog. There is no personal, confidential or financial information there. I would have no problem giving someone the Username and password to my site to see if they can log on and figure out why I cannot password protect a specific page. I have a personal reason, unrelated to the travel blog, to post page that is password-protected and would appreciate any help I can get. This is so important that if can’t find a solution, I will give up on WordPress and find another program to publish my site.

    Anyway, I am grateful for the help you have given me.

    Hi @omahajoe74 ,

    You can easily password-protect your WordPress page without any plugins. Here’s how:

    1. After publishing the page, go back to your WordPress dashboard and click on Pages.
    2. Locate the page you want to protect.
    3. Click on Quick Edit under the page title.
    4. You’ll see an option for Password. Enter your desired password.
    5. Click Update to save the changes.

    That’s it! Your page should now be password-protected.

    Thanks

    @omahajoe74

    Also, if you unable to do it yourself, I am happy to check your back-end and give it a try.

    Thanks

    Hi @omahajoe74 ,

    Your WP login page not accessible, would you please share me the correct URL.

    This URL not working : https://www.shanahanfamily.com/wp-admin/

    Thanks

    Hi @omahajoe74 ,

    You website also not accessible, please make sure and share me the correct live URL and I can give it a try.

    Thanks

    Moderator Support Moderator

    (@moderator)

    While I know you have the best of intentions, it's forum policy that you not ask users for admin or server access. Users on the forums aren't your customers, they're your open source collaborators, and requesting that kind of access can put you and them at high risk. 
    
    If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.
    
    Thankfully are other ways to get information you need:
    
    
    Ask the user to install the Health Check plugin and get the data that way.
    Ask for a link to the https://pastebin.com/ or https://gist.github.com log of the user's web server error log.
    Ask the user to create and post a link to their phpinfo(); output.
    Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
    Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site vistors).
    Ask the user for the step-by-step directions on how they can reproduce the problem.
    
    
    You get the idea.
    
    We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It's actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it's difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.
    
    When you help users here and in public, you also help the next person with the same problem. They'll be able to read the debugging and solution and educate themselves. That's how we get the next generation of developers.

    @omahajoe74 @ahnuhmannathly Please note that sharing and accepting logins to the user\s site backend is against forums guidelines.
    While debugging password protected pages issues you can only share page access passwords, not the admin logins

Viewing 11 replies - 1 through 11 (of 11 total)
  • You must be logged in to reply to this topic.