I am trying to password-protect some of my pages but when I try the function on an example page: http://www.netzarroyo.org/lab-members-contact-information/
Pass: hola
clicking submit just won’t do anything.
I have tried deactivating all of my plugins but the problem did not get fixed. So I am guessing this could be related to the theme?
Hope you are having a good day and thank you for your question
Please activate one of default wordpress theme and check again, let me know results
Thanks!
Colorlib Support Team
Thank you for your fast reply. I have activated twenty seventeen and the password protected page does work as expected. So, something to do with Activello?
I tried in my local installation all works just fine, you sure you’re on the latest version of the theme and the plugins? If still you didn’t figure out, can you pass us the WP Login details in a “Private reply” we will check what is going wrong.
Please deactivate all third party plugins and try again your problem, most probably this I conflict with third-party plugins.
Once you deactivate all plugins please check your problem again, if the problem is gone then this means it was a plugin conflict. Now, start activating plugins one by one and same time repeat your problem until your problem appears again, now you know which plugin was in conflict Thanks!
Colorlib Support Team
I just deactivated all of my plugins, tried the password protected page again, and it didn’t work. It only works if I switch to a different theme (even with plugins on), which suggests to me that there is an issue with my theme.
This is very strange, when i try this on the fresh theme an fresh WordPress i cant replicate the problem,
do you have any modifications done in the theme?
Thank you for all your help, I am giving up. The password protection is not absolutely necessary for me, it clearly isn’t a simple problem, and I don’t want to waste more time on this issue. I will simply not use the functionality.
the thing is that we cant replicate same problem on our sides, my other colleagues tried this as well and the problem was not replicated this is indeed indicated but if this thing is not so important for you lets give up it here, if same problem will appear for other customers then we can debug it till the end