I noticed a problem today which is illogical for me.
The following situation:
The website has its own login page (not the standard WP login page)
When my website is open, this page is also displayed for the login request - I have defined this page as the login page in the general Bricks settings.
But now the problem is that when I put the website in maintenance mode (a special template is specified for this) it is completely ignored.
If I remove the own login page under the general settings, the maintenance page (not logged in) is displayed again. I suspect there is an error in the logic here - as the maintenance page should have the top priority - or am I seeing this wrong?
I am slightly confused by your report and unsure if I understand it correctly.
I understand you are complaining about the custom login page being displayed when maintenance mode is enabled, and you are logged out, right?
If this is the case, I don’t see any logical issue. Otherwise, you wouldn’t be able to log in, as both /wp-admin and /wp-login.php would redirect to your custom login page, which would then be “taken over” by maintenance mode.
I may have expressed it a bit unfavorably - I had thought about the problem again in the evening - and yes, of course that’s right - if the maintanance page was above the login page I wouldn’t be able to log in. I saw this from the point of view of my maintenance page - which itself also has a login option - so the whole thing is completely correct from the Bricks side. My only problem was - that if I switch the page to maintenance mode - the users can still log in and the maintenance mode would make no sense - because I want to prevent a visit to the page (except administrators).
Best regards, Ivo
