This will tell you if a plugin is the culprit and specifically which one. One by one, disable plugins and re-test your password protected pages. If password protected pages work after the switch, then you know it’s likely that your theme is the culprit. Switching to a default theme such as Twentytwenty one is a good first step. All the below recommendations should be carried out on a staging site – a clone of your live site that can be used for testing changes. We’ll call these the ‘nuclear’ options as they require significant but temporary changes. Password protection does not cover custom fields by default, but it’s not hard to make this happen – see our article on this. This is the most important part to check – your page must have the_content() within your loop for password protection to work.
If you are running Cloudflare, also clear the cache over there. This is unlikely to be the cause, but we’ve seen some strange errors caused by caching plugins over the years, and it can’t do any harm. If you have a caching plugin, make sure you do a full cache clear.
Try opening the page in an incognito window to avoid any browser caching or chances of being logged in. This is aimed primarily at developers as it’s most likely to affect custom themes.
But what do you do if you’ve set up a password for a page, but it’s still allowing access without a password? here’s some basic troubleshooting tips.
0 kommentar(er)
