• webmasteral

    (@webmasteral)


    When updating this plugin from 1.1.7 to 1.1.9 the plugin fails and breaks.

    Had to roll back to 1.1.7

    Notice this plugin is now locked due to “need of full review”

    Hope this matter is resolved and that 1.1.9 can be fixed to correct whatever issue caused the login redirects to stop working and revert back to wp-login

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Alexander Kovalev

    (@alexkovalevv)

    Could you describe the problem in more detail? If there are PHP errors, please attach them to this topic so that we can fix it.

    The plugin is being reviewed by moderators due to a small problem in the plugin, we have made these corrections and are waiting for verification. Unfortunately, this may take time.

    Thread Starter webmasteral

    (@webmasteral)

    My thought was maybe because the plugin is not downloadable during this locked review process the update process isnt happening correctly.

    There was no php errors sadly. No errors at all other then the custom url no longer working.

    What happened is on the 27th the update was applied, after that links that normally pointed to (custom login url example: hello) pointed to wp-login.php like the login button went from /hello back to /wp-login.php

    I tried to turn the plugin off and back on, change the url, hide the default url on/off the link for the login button did not change.

    Rolling the plugin back to 1.1.7 caused the url to point again to the correct url.

    I was not able to investigate the issue further as my clients customers were messaging about noting being able to login but if I had time I wish I could have checked the DB to see if the url value was being updated.

    I should also mention this “bug” did not replicate itself on my other clients websites that also use this plugin but those updates were applied before the plugin was locked for review.

    During the clients next maintenance window I was planning on DL the plugin from client A and uploading it to client B (the one that had the issue) and see if that solve the issue or if the issue re-appears.

    Thread Starter webmasteral

    (@webmasteral)

    When digging through the error logs I finally found the following

    PHP Fatal error: Uncaught Error: Class ‘Wbcr_Factory465_Requirements’ not found in /home/public_html/websites/wp-content/plugins/hide-login-page/hide-login-page.php:74
    Stack trace: 0 /home/public_html/websites/wp-settings.php(473): include_once() 1 /home/public_html/websites/wp-config.php(81): require_once(‘/home/p11iqgg22…’) 2 /home/public_html/websites/wp-load.php(50): require_once(‘/home/…’) 3 /home/public_html/websites/wp-blog-header.php(13): require_once(‘/home/…’) 4 //home/public_html/websites/index.php(17): require(‘/home/…’) 5 {main}

    thrown in /home/public_html/websites/wp-content/plugins/hide-login-page/hide-login-page.php on line 74

    hope that helps

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘update 1.1.9 fails/breaks [Stay at 1.1.7 as it still works]’ is closed to new replies.