Not planned login as login_form.

Hello,

I want people to see my forum only if they log in first. If they are not registered, they should not see anything. The login page style I have now is not good for me. Just changing permissions for unregistered users is not enough. I want the forum login page to look and work like the Admin Control Panel (ACP) login page, like in the picture below.:

login_form.webp

I am quite surprised that no one has suggested implementing such a feature until now. Why do the forum login form and the ACP login form use different templates?
I want public "login" Template look like admin "login_form" Template.
Looking forward to your thoughts and possible solutions!

Clarification:
I didn't say to unite them. I said that I want the public login page's behavior and appearance to be like the admin login page.
I didn't suggest creating a single place to enter both admin and pub instances.
I wrote only about an opportunity to have the pub login page behavior and appearance like admin's.
 
Last edited:
Upvote 1
This suggestion has been closed. Votes are no longer accepted.
Nah, I don't agree with this. I think keeping it separate is best. I was testing with 2.3 just yesterday with older templates as I'm preparing for upgrading it all the way to 2.3, and it broke everything on the main page. I wouldn't have been able to log back in if it used the same template set. Because when I just typed the URL to /admin.php, everything there was perfectly fine.

Our admin.php is protected, so no guests can ever see or access it anyway.
 
Nah, I don't agree with this. I think keeping it separate is best.
I didn't say to unite them. I said that I want the public login page's behavior and appearance to be like the admin login page.
I didn't suggest creating a single place to enter both admin and pub instances.
I wrote only about an opportunity to have the pub login page behavior and appearance like admin's.
Our admin.php is protected, so no guests can ever see or access it anyway.
Also the pub has to be protected too.
 
Hello,

I want my forum to be accessible only through a login form, so that unregistered users cannot see any part of it. The current login template style doesn’t suit me, and simply adjusting permissions for unregistered users doesn’t fully address this. Ideally, the forum login form should look and work like the Admin Control Panel (ACP) login form, as shown in the image below:

View attachment 324442

I am quite surprised that no one has suggested implementing such a feature until now. Why do the forum login form and the ACP login form use different templates?
I want public "login" Template look like admin "login_form" Template.
Looking forward to your thoughts and possible solutions!
The only way I see to do this is create a page node with all the appropriate html code with a conditional that bypasses the page for logged in users.
Use Index page route to direct the main forum URL:.

li1.webp
 
The only way I see to do this is create a page node with all the appropriate html code with a conditional that bypasses the page for logged in users.
Use Index page route to direct the main forum URL:.

View attachment 324460
You are offering a workaround. I am suggesting a solid feature.
I think the best way is to copy the login page behavior from admin/App.php to pub/App.php. Appearence and behavior are already implemented. Nothing to add.
 
Any XF update will most likely over write. You will also receive an Admin error message due to an altered file.
Its best to not alter core code but use the given tools.
 
Our admin.php is protected,
Seems to be not so protected:
 
The bug I've described in another thread may lead to security issues. Obviously, the two environments are not separated.
No, they are not separated and they don't need to be. As mentioned, most of us have other protections in place over admin.php, so you need to authenticate through a separate layer outside of XF to access it. Just as he said above, nobody can even see admin.php with the additional layer of security configured. (it can be a network layer control, it can be a server level control, there are several options outside of XF you can do to protect admin.php functions on top of standard permission based controls in XF by user classification)
 
 
Back
Top Bottom