Forum Replies Created
-
Posts
-
Ah! I see! Works like a charm! I shouldn’t give up that easy and try more variations before taking up your time. But this one just bought you a hot chocolate! … and I think it’s not the last drink we will have together
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!
Well as I started the translation I did it with my project in mind. So I got a lot of funny and ungeneric phrases.
Very happy client here! Great feature fulfillment! Will try it right away… and come back with a pint if it works!
Thanks. I went into the /lang-Directory and was surprised to find most language files named after foreign languages but in fact not translated. In my case it was called ger.php (German) but every term was in english. Well I am translating it now.
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!
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
