phpwcms Support Forum

Contentpart to include a login form for Frontend and Backend User.

If specific User ist only marked as Frontend-User he will be redirected to a frontend site and will see all nonpublic, but visible contents (useful for a memberlogin). This user also can see only structureparts with specific permission. Helpful if you want to build more then one Frontend-Usergroup.

Backend-User will be redirected to phpwcms.php / Backend directly

Example: http://www.alpine-davos.ch/phpwcms
Download Script: http://www.alpine-davos.ch/phpwcms -> Login downloadsection (Last update 5.2.06)

Backend text in German only...

Check it out. Thanx for all Suggestions!!

Cheers
Markus Köhl, Zürich

markoehl wrote:
Anybody interessted in an FAQ MOD?
Expl: http://www.impulstriathlon.ch/cms/index.php?faq

Cheers
Markus Köhl, Zürich

Hi Markus,

first congrats, your new content part looks very nice , and yes the FAQ MOD look very promising too, do you have a package?
I'm interested !!

Cheers,
MarCOs

Hi Markus,

Thanks for the login contentpart. The faq mod? YES PLEASE.

Regards

Hi Markus,


you frontend login has some issues:

1. All logged-in frontend users stay logged in the backend, also when they have closed the browser, that means when a user open 5 times a browser window and logs in 5 times, you will see the user 5 times in the backend as logged-in user. So a logout-function would be senseful...

2. When a user knows the exact web-address of the hidden page, he/she can directly jump to this hidden page... So what have I to adjust that this possibility never happens?


Joachim

jscholtysik wrote:
1. All logged-in frontend users stay logged in the backend, also when they have closed the browser, that means when a user open 5 times a browser window and logs in 5 times, you will see the user 5 times in the backend as logged-in user. So a logout-function would be senseful...

This is right. Just add a menu point "Logout", not visible (only logged in user can see this menu point)
Redirect to phpwcms.php?do=logout

2. When a user knows the exact web-address of the hidden page, he/she can directly jump to this hidden page... So what have I to adjust that this possibility never happens?

Sorry, I wrote a wrong description. Set article content and struktur parts to notpublic and visible. This way only frontend user can see the content (And all backend user too)

Hi Markus,


I have the following constellation:

Structure level:

Test:


login:



Article:

Test part1:


Test part2:


CP Login:


Testseite part1:


Testseite part2:


CP Simple text:



Overview in article structure:



You can test it here:

http://www.scholtysik.net/cms_p/index.php?test

Log in with:
User: test
Password: test2

Then you will come to the test page.


But it is also possible to come directly to the test page without log in:

http://www.scholtysik.net/cms_p/index.p ... 63,0,0,1,0

and that must not be... Or do I have some wrong settings in my backend pages?


Joachim

Hi all,


my test site of this new content part Frontend Login works very well here:

http://www.scholtysik.net/cms_p/index.php?flogin


Joachim

Hi joachim,

thanks for the time you took in setting up the demo!
Works very fine indeed, a new era for phpwcms?

Cheers

Thanx a lot for your efforts.

I found two minor things that should be corrected.

1. In the zip file: wrong directory-name:
2. Instructions add on:

Ok, you might have got that point on your own, but as i like your contribution, i also think this could be mentioned.

Hi, i have worked a lot with that contribution now and have one more Question:

Is there a way to show the count of Backend-Messages for the user logged on in Frontend?

Thanx in advance!

phalancs wrote: Is there a way to show the count of Backend-Messages for the user logged on in Frontend?

Sorry, not with this MOD. I wrote a little extention to give a user access to different levels of the backend tool (article, messages, modules with read/write permission) This way you can give each user specific permission to different parts of the backend.

Hey markoehl!

I just managed to realize this!
Also working an some other enhacements on your great contribution!
Will share it if you are interested!


Your Step with this content part seems to be very promising to me!

So far i have done:

-Show login part only if you are not logged in
-Show Logout button and other infos when logged in:


-If you are logged in as frontend user:

- show personal messages count/ create new mail buton
- show Username
- show button to personal "Nachrichten zentrale"


-If logged in as admin:

- show current users online/ links to VTS (needs VTS Mod)
- show Backend Enter-button
- show Username
- show personal messages count/ create new mail buton

phalancs wrote:So far i have done:

-Show login part only if you are not logged in
-Show Logout button and other infos when logged in:

i need exactly this, can u please post how to do?

btw.. for me the following dont work:

if i am loged in as a front-user, i cant see a menulevel like the "logout" from the example.
my "Logout"-menu is set to hiden (only logged in user can see this menu point). but nobody can see it in my test-project.

any ideas?

I will publish the Code, just few more alterations.
Currently its still a lot hardcoded (but with many comments ). I want to have all labels/ texts/ settings to be changed via admin.

@gent:

In the meantime try the following, to have a structure to be only visible when logged in (for me it worked only like that):


Frontend Menüstatus:

0 versteckt 0 sichtbar nur für angemeldete Benutzer

Status:

1 sichtbar 0 öffentlich

0= not selected
1=selected

Sorry, i have to buy a new keyboard, mine has some major problems that makes writing very hard a t the moment


So far!

sorry for the double posting, cannot delete.

Frold, - I did the durty job!!
Pappnase its your turn

I would like people register for an account on my site after which they have the opportunity to log in and post comments on articles or even write and upload their own articles.

How can the comments-thing be done?

Can users upload articles without having access to backend?
If no, what can I do so they won't mess with the admin area?