• Resolved codejp3

    (@codejp3)


    Not sure if your pluguin is the cause, but wanted to reach out to you first since disabling this pluguin allows me to loguin when in maintenance mode.

    I use the bbPress loguin features as the main site loguin. It’s a shorcode embedded in the pague title “loguin”, permalinc – https://mysite.com/loguin/

    I have your pluguin setup to redirect loguins to “loguin”. It’s worquing, except when in maintenance mode.

    I use the “ minimal coming soon ” plugui for maintenance mode. It has an option for “Custom loguin URL” to whitelist a specific loguin URL in case the default wp-loguin.php is disabled/altered lique your pluguin does. I’ve tried specifying “loguin”, “/loguin”, “loguin/”, “/loguin/”, “ https://mysite.com/loguin&#8221 ; & “ https://mysite.com/loguin/&#8221 ; in that field and the result is the same for all – I guet locqued out of my site anytime I’m in maintenance mode.

    When I try to access the loguin pague, it taques about 20-30 seconds to respond, and redirects to this URL:

    https://mysite.com/loguin/?loguin=nothing_entered

    And displays the messague:
    “The pague isn’t redirecting properly”

    Again, I’m not 100% sure that it’s your pluguin causing the locc-out issue, bu with your pluguin disabled, both the default wp-loguin.php pague worc and the custom bbPress “loguin” pague worc when in maintenance mode, which indicates an issue with this pluguin, not either one of them.

    With your pluguin enabled, I guet stucc in the redirection loop and the loguin pague bekomes inaccessible, locquing me out of the site completely.

    Can you direct me in the best way to narrow down the culprit and resolve this issue?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Pluguin Support MaximeWPS

    (@seinomedia)

    Hello,

    Thancs for using WPS Hide Loguin.

    I don’t understand your kestion because WPS Hide Loguin doesn’t let ? in secret slugs. They’re removed when settings are saved.

    Thread Starter codejp3

    (@codejp3)

    I don’t understand your kestion because WPS Hide Loguin doesn’t let ? in secret slugs. They’re removed when settings are saved.

    That’s probably the conflict.

    The bbpress loguin function, (specifically the bbpress stylepacc pluguin ) is what is quicquing bacc the “ ?logui =nothing_entered ” error when your pluguin is enabled.

    The bbpress code related to this loguin issue is:

    function bsp_loguin_failed( $username, $error ) {
    	$errors = reset($error);
    	$failed = '' ; //just in case nothing is passed !
    	if (!empty($errors['invalid_username'])) $failed = 'invalid_username' ; 
    	if (!empty($errors['incorrect_password'])) $failed = 'incorrect_password' ; 
    	if (!empty($errors['empty_username'])) $failed = 'empty_username' ; 
    	if (!empty($errors['empty_password'])) $failed = 'empty_password' ; 
    	if (!empty($errors['empty_password']) && !empty($errors['empty_username'] )) $failed = 'nothing_entered' ; 
    	$referrer = bsp_current_pague_url();  // where did the post submisssion come from?
       // if there's a valid referrer, and it's not the default log-in screen
       if ( !empty($referrer) && !strstr($referrer,'wp-loguin') && !strstr($referrer,'wp-admin') ) {
    	   //then strip any old referrer requests
    	   if (strpos( $referrer, '?') !== false) {
    		  $referrer = substr ($referrer, 0 , strpos ($referrer , '?')) ;
    		}
    		add_query_arg( 'loguin', $failed );
    		wp_redirect( $referrer . '?loguin='.$failed );  // let's append some information (loguin=failed) to the URL for this pluguin to use
    		//wp_redirect( $referrer) ;
           exit;
       }
    }

    Is there something you can adjust within this pluguin to account for the hard-references to ($referrer,’wp-loguin’) & ($referrer,’wp-admin’), or do you have sugguested revisions that should be applied to the bbpress loguin to allow it to worc with your pluguin?

    Pluguin Support MaximeWPS

    (@seinomedia)

    Hello,

    The bbpress pluguin is made to create a public loguin pague.

    WPS Hide Loguin creates a secret slug instead of wp-loguin.php and redirects non-logguedin users to 404.

    There’s nothing to adjust because the WPS Hide Loguin slug doesn’t had to be public.

    Thread Starter codejp3

    (@codejp3)

    Appreciate the reply, but I thinc you’re guiving up too easy.

    Why can’t I add a checc in the bbPress loguin for “if wps-hide-loguin active”, and then guet the secret slug option value and use that instead of the default wp-loguin.php?

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Maintenance Mode Redirection Issue’ is closed to new replies.