Page 1 of 1
passwortgeschütze seiten? / password protected pages?
Posted: Tue 4. May 2004, 10:22
by cyrano
Hallo wertes Forum,
ist es möglich, Seiten innerhalb der Website als passwortgeschützt anzubieten? Nur ausgewählte User dürfen nach Eingabe eines Passwortes und Username sich einloggen; alle anderen erhalten einen Hinweis, das es nicht geht.
Ich würde dies zur Zeit nutzen können in Verbindung mit den Newsletter-Abonnenten, wird so etwas angedacht (Frage an Oliver G.?).
Ich kann zwar mit Hilfe von Passwörtern Verzeichnise schützen, da komme ich aber an einzelnen Seiten innerhalb einer wcms-Installation nicht dran... oder doch?
Danke für Tipps.
Dear Forumuser,
I want to offer password-protected pages within a wcms-installation - is this possible? Or a feature for the future (Question to Oliver G.?)
at the moment I would like to offer special pages only for successfull registered newsletter recipients - may be this is possible?
I can protect directories via my webspace, but I didn't get this within a wcms installation.. right or any ideas?
Thank you.
Re: passwortgeschütze seiten? / password protected pages?
Posted: Tue 4. May 2004, 11:08
by frold
cyrano wrote:
Dear Forumuser,
I want to offer password-protected pages within a wcms-installation - is this possible? Or a feature for the future (Question to Oliver G.?)
at the moment I would like to offer special pages only for successfull registered newsletter recipients - may be this is possible?
I can protect directories via my webspace, but I didn't get this within a wcms installation.. right or any ideas?
Thank you.
At the moment the easiest way to do it is via htacces (for the whole site)...
Posted: Tue 4. May 2004, 11:24
by cyrano
hello frold,
hmm, yes for the whole site, that's the same like htaccess via webspace configuration....
Ok, i can wait, it is not a urgent need

Posted: Tue 4. May 2004, 12:00
by Jérôme
I think this would be a quite complex feature, because every page in phpwcms is created through the index.php.
So it would be necessary to mark a page as "private" in the backend of phpwcms, to include a front user management to the backend and so on, and so on...
I think this would be a too huge task for a "simple" MOD, but I think this will be included in one later release of phpwcms. At least I have put it on the ToDo list for the case that Oliver hasn't done so

.
Posted: Tue 4. May 2004, 12:15
by cyrano
hi Jérôme,
thanx for your endless knowledge...
thank you for enlighten my problem zones (hey i mean the brain)

Posted: Tue 4. May 2004, 12:28
by Pappnase
hmm
i have one idea!
install phpwcms in an subdir of your domain! and call these sites you wanna secure via the {PHP:} Tag. understand what i mean!?
Posted: Tue 4. May 2004, 12:31
by cyrano
Posted: Tue 4. May 2004, 13:15
by Pappnase
oh cyrano!
you create an new dir in your root eg. secure, where you also place the htaccess! upload there a new installation!
setup it to the same database with an different prefix!
you create an template without an navigation.
build youre sitestructure there. with aliases
in your main domain you place now links in the articles
like
http://www.cyrano.de/secure/index.php?newsletter
now visitors can only via htaccess this pages!
Posted: Tue 4. May 2004, 13:36
by cyrano
hehe pappnase,
thanx for writíng.
i know how to make a subdir

really
but i want the acces only to a couples of sites and only for users i know, especially for those who has submitted the newsletter.
so... let it be...
Posted: Tue 4. May 2004, 13:43
by frold
cyrano wrote:hehe pappnase,
thanx for writíng.
i know how to make a subdir

really
but i want the acces only to a couples of sites and only for users i know, especially for those who has submitted the newsletter.
so... let it be...
I guess the RC5 will solved your problem (will be released at the end of may) It should support frontend login and then you can set some menu levels only to be visible for logged in users... I see this as the best solution...but you have to wait
http://www.phpwcms.de/forum/viewtopic.php?t=1781
Todo until next release:
- Content Part "News"
- Content Part "Blog"
- Replacement Tag for <ul><li> Menu based on sitemap creation
- Template Defaults editor for template based default values
- Possibility to choose in which frontend block content parts should be rendered
- Frontend user