- This topic has 12 replies, 3 voices, and was last updated 12 years, 6 months ago by
.
-
Posts
-
Hello there
I’m trying to block the entire site but leave the homepage (http://www.domain.com) public for everyone to see.
If I enable site wide protection and specify http://www.domain.com to exclude, then it does not work. (all the site is available for public).
Same happens if I insert http://www.domain.com/, then all the site is available for public.
Any way to solve this?
We didn’t count on someone using the site-wide lockdown feature and then exclude the homepage. We assumed, someone using the site-wide lockdown would want everything except a few particular pages to be locked. Anyway, I have updated the condition so you should be able to exclude your homepage URL when using the site-wide lockdown feature.
We have now added a feature in the plugin to handle this scenario.
Hello,
I have a similar request. I just purchased so I should be up to date. I want to lock down an entire site to anybody not having an account with it. The thing is that I need to exclude the homepage and a subdirectory (categrory) named http://mysite.tld/public1/(*) and one called http://mysite.tld/public2/(*) from the lockdown. Also I would like the user to be able to see the homepage itself so http://mysite.tld/ but not http://mysite.tld/(*) as this would be a contradiction to the lock-down .
Currently this doesn’t work? Any suggestions?
I wanted the lock-down feature so if any resources that should be protected within the website are by accidentally compromised (wrong settings etc.) will only breach inside registered members boundaries and not to the public (google etc.). Avoiding some customer pointing out that he found his personal data via google…
Regards
The *Page Exclusion* option we have for the domain level lockdown option is targeted to exclude *exact* URL (not a pattern). So you should be able to exclude your home page URL by specifying the URL “http://mysite.tld/” in the exclusion field but if you want to exclude “http://mysite.tld/public1/(*)” then that won’t work as you are trying to exclude a pattern there.
We can look into adding another exclusion list area that you can use to exclude URL patterns maybe.
Hello,
that would be a great idea! You can see the usefulness of this option and one could also make work as a checkbox that converts the interpretation of the comma-sepaerated textfield-rows into regular expressions. Either way: nerdy or an additional inputfield… extending the behavior is a feature not only I would benefit from. I guess lot’s of users will find the argumentation for looking down sites with broad brush strokes and then gradually opening them appealing. Maybe a tutorial on this will even further deepen the insight for potential new users. Correct me if you think I am wrong.
By the way… played around with the settings and I love the product!
This work is now complete. You will find a new field under the site wide lockdown feature that can be used to exclude URL patterns.
Very happy client here! Great feature fulfillment! Will try it right away… and come back with a pint if it works!
Okay I couldn’t get it working I added a screen shot: [http://bit.ly/JD0HtS]
None of the features worked? The lockdown exception my homepage as seen in the screenshot was not accessible. And all sites below /oeffentlich/ also? What am I doing wrong?
I always get the promt to login.
Sorry to dwell on this feature. But its an important one! Thank you!
Remove the trailing slash “/” from that URL (The full URL has to match exactly as what you see in your browser’s address bar). If you see the following in your browser’s address bar:
http://www.example.comThen using the following in the settings will not result a match:
http://www.example.com/The *exclude specific page* looks for an exact match.
- You must be logged in to reply to this topic.