Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Uncanny Owl

    (@uncannyowl)

    Yes, our plugin forces a login form in the body of the login page so you don’t accidentally lock yourself out by setting a login page that doesn’t have a login form. Modifying it to look at the sidebar may be something we consider, but for passwords resets and other functions it’s a good idea to have a dedicated login page with a single login form (not in the sidebar). You don’t have to link to it, but it is helpful for that process and would alleviate the issue you have now on the homepage. You could also hide the on-page form with CSS, but I suspect that will cause problems with password resets.

    I’m using a membership plugin with its own user database and custom login form. So would it be possible to remove the default action of forcing a login form on the page?

    Plugin Author Uncanny Owl

    (@uncannyowl)

    Hi czerney,

    If you’re using a plugin with its own login form then you should disable our Front End Login module. Otherwise there will likely be a conflict like this.

    Yep that was my first instinct,

    However I want to use the Login/Logout link in the menu that alternates depending on whether I’m logged in or not.

    This option directs automatically to the /wp-login page as it has #uo_log_in_out_link in the URL configuration of the menu link. If I change this #uo_log_in_out_link in the URL configuration to the page I want, then it breaks the login/logout link.

    So I need to leave the #uo_log_in_out_link and instead enable the “Front in Login” option to force the login page to be the custom one I’ve got with the membership form on it.

    Now this works perfectly except that the front end login is now force appending an additional form to be put onto the page. I know it’s being forced onto the page to remove the risk of someone directing login to a page that doesn’t have a form, but in this case I need to remove it as access to my site has to be via the membership plugin login form.

    If the front end login simply did not force a login form to appear on the custom page I select to be the login page then it would be perfect. Surely a checkbox that could be selected in this option to enable/disable the login form being inserted could be easy enough to implement?

    Plugin Author Uncanny Owl

    (@uncannyowl)

    Sorry czerney, when a login form wasn’t forced we had way too many users miss instructions and lock themselves out of their site by not setting up a login form. That’s the real issue. This approach may not work for all cases but it limits the risk of people locking themselves out and being rather annoyed with us. Even with a toggle it’s less safe than just forcing the form if none is detected. I would still suggest disabling our module and using an alternative plugin, or ask what your membership plugin suggests for the behaviour you want (since they’re enabling the login form maybe they have ideas).

    How about adding an option to the login/logout link to direct to a custom login page of my choice directly rather than hardcoding it to direct to the /wp-login page?

    No need then to make any changes to the “front end login” and alleviates the risk of locking a person out of their site since they could just browse to /wp-login to login in.

    Thoughts?

    Plugin Author Uncanny Owl

    (@uncannyowl)

    Login page is set in Front End Login (see https://www.uncannyowl.com/knowledge-base/front-end-login/), so setting it in the second module would create a conflict (and it definitely needs to be in that module). Custom development is an option, but we’re not expecting a Toolkit change here, sorry.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Double sign-in area’ is closed to new replies.