Thread Starter
yu
(@yudesign)
Yes, I did. It’s the same info as in the video mentioned above. And I could not find a hint regarding the conflict between htaccess protected wp-login and the protected option via Visibility. Or am I missing something?
If you do not make the Post or Page private and simply password protect it, no on will have to login to view it. They’ll just need to enter the Post/Page specific password via the front end of the site.
Thread Starter
yu
(@yudesign)
Nope. Have a try. Password for the page is: 123
http://www.publishing-bootcamp.de/test/
Can you not whitelist the ips you want to have access to this page?
Thread Starter
yu
(@yudesign)
No, that is not possible.
The protected page is for the participants of our event. We want to provide them downloads for the sessions, pics and so on. We can’t control which IP they use and in most cases their IPs will be dynamic.
use master WP-admin Panel,
Then I can’t think of a solution using core WordPress. sorry.
You might want to have a look around to see if there are any membership-type plugins that could help you restrict this content without undermining your wp-login.php protection.
Thread Starter
yu
(@yudesign)
Uhhh, that’s a pity. But thanks for your help so far!
At this point my suggestion to the wp developer team would be to find a way to use protected options for single pages and posts without using wp-login.php. Maybe by creating an extra transfer page for protected content naming differently as wp-login?
I really do need this on at least every second project. Maybe other users would take advantage as well from this adjustment…
Did anyone find a solution for the problem?
Thread Starter
yu
(@yudesign)
Plugins seem to be the only viable solution. I’m personally not very keen on plugins that always are potential security risks. The core won’t be modified, see my ticket: https://core.trac.wordpress.org/ticket/28798#comment:2.
Having exactly the same problem. Sadly, there doesn’t seem like any way to work around this.