Support » Plugin: Custom Login » Error 500 after update to 2.3.1

  • Resolved Jos Klever

    (@josklever)


    Parse error: syntax error, unexpected ')' in /.../wp-content/plugins/bm-custom-login/bm-custom-login.php on line 101

    It looks like the comma on line 100 needs to be removed. Then the plugin works.

Viewing 6 replies - 1 through 6 (of 6 total)
  • There Has Been a Critical Error on Your Website
    Yeah, same problem here. Also, thanks for the tip @josklever

    Plugin Author binarymoon

    (@binarymoon)

    Oh no – really sorry about that. It didn’t happen for me. I wonder if it’s because I’m running a different version of PHP

    I shall fix this now.

    Sorry again!

    Ben

    Thread Starter Jos Klever

    (@josklever)

    That’s what I was thinking as well. This site is still using PHP 7.2 (long story, bad hosting) and it was for a long time not possible to upgrade to 7.4, but I’ve just checked again and it was possible now so I’ve updated directly.

    Of course I’ve tested the issue, by putting the comma back and it works with PHP 7.4, so it should only be removed for backward compatibility. I’m just not sure what the correct/best coding would be (I’m not a programmer).

    Plugin Author binarymoon

    (@binarymoon)

    Ah ha – thanks for confirming and glad that’s it. Hopefully it means not too many people were affected.

    In terms of the change, removing the comma is fine, it got left in by accident – but since it didn’t affect me I didn’t pick up on it.

    Thanks again – Ben

    Tony

    (@tmalonemktg)

    I have a few websites on an old server that are experiencing the issues as stated above. Removing the comma did not stop the issues on my websites. Please assist.

    Plugin Author binarymoon

    (@binarymoon)

    Are you using the latest version? If the plugin is on version 2.3.2 then it should work. If it doesn’t then I need actual error messages from the error logs to be able to work out why it’s not working. Hopefully your web host can help with that.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Error 500 after update to 2.3.1’ is closed to new replies.