I have been testing the new custom login page in the Bricks settings issued today (v.1.9.2).
I set a custom page for login on a temporary project, so no stress. But I continued playing with this page and removed the login form at some point, saved, and later logged out.
Now when i try to connect to this project, I can’t get to the login form obviously because I removed it. And trying a direct url www.mysiste.com/wp-login does not work…
So basically I am locked out of this project
Is there a fallback to get passed this custom page and back to a regular login page/form ?
Thanks @timmse@thomas , I think this will be helpful for many if you can create a fallback of some sort ?
Hm yeah this is a little bit tricky. On one hand it’s easy to “shoot yourself in the foot”. On the other hand, having to check whether the page you’ve chosen as the login page actually has a valid login form might introduce more latency when redirecting to that page.
Just brainstorming here: maybe we could introduce a URL query parameter, where if that exists, then we should redirect to the actual WP login page I’ll record this in our internal board and discuss this more with the team first to see what makes most sense. If you have some other ideas feel free to share as well
I don’t have (for the moment) any particular suggestion, I am mostly looking into other ways of getting around this issue, and getting access back to my project.
I am thinking on changing the active theme (from Bricks child to any other WP theme I have on the install), this way it should cancel the login redirection, right ? If you have any other way you can think of to disable this redirection, I’d like to hear about it.
I’ll look farther into this when I can, and will offer some insight then, if I can gather any.
My hosting provider offers a service called Softaculous that allows to rapidly install various services (WordPress, Joomla, Drupal, prestashop, … whatever amongst hundreds of them).
It also allows a “one-click” link to automatically log-in using a special link in the form of : https://..:///**/softaculous/index.live.php?act=sign_on&insid=26_******&autoid=vhicn*****************cq2j2c3kh
Using this link I could access the admin panel and disable the login redirect. So problem solved.
Maybe there is a clue in this kind of “one-click-login” function ? Obviously any shortcut you would allow would become a weak point for security, so not sure how to. use this.
If you end up introducing an url parameter for that, make it customizable so we can hide the default login and only show it if we know the “code” parameter
Hey @timmse
Is the new release supposed to redirect from wp-login.php to the page indicated in the settings?
It’s not clear from the docs, and it’s not doing it for me on the latest version. If I access wp-login.php, it stays there and shows the default WP login form.
The new release allows you to add a parameter to the login URL brx_use_wp_login=1, bypassing the custom login page you’ve set and taking you to the default WordPress login page. If you added the parameter earlier you can try clearing your browser’s cache.
But maybe I’m misunderstanding your question, some screenshots of your settings would be helpful.
The WP-CLI solution worked well for me when I accidentally used settings to get rid of the standard log-in page.
So again, not a bug, but the solution is still useful, even for later versions of bricks.