Support » Plugin: Proxy & VPN Blocker » Blocked Page Blank for Registrations

  • I am only using this to block the login and registration forms.

    If I use the default message, it works fine.

    If I set a page for the blocked message, it works for logins, but not registrations.

    I simply get a white screen, which looking at the page source is the registration page.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Had to disable the country block array line with list of countries, as it was causing a PHP error.

    Now the only error is:

    PHP Warning: Cannot modify header information - headers already sent by (output started at /home/xxxx/public_html/wp-login.php:74) in /home/xxxx/public_html/wp-includes/pluggable.php on line 1219

    Plugin Author rickstermuk

    (@rickstermuk)

    Hi @sandgroper,

    What was the PHP error before you disabled the country array?

    Also what version of PHP are you using? This isn’t something I’ve come across before.

    Rick

    With the array line enabled, I get these errors:

    PHP Warning: Invalid argument supplied for foreach() in /home/xxxx/public_html/wp-content/plugins/proxy-vpn-blocker/includes/plugin-options.php on line 286

    PHP Warning: Invalid argument supplied for foreach() in /home/xxxx/public_html/wp-content/plugins/proxy-vpn-blocker/includes/lib/class-proxy-vpn-blocker-admin-api.php on line 144

    The error at line 286 is related to the country array, which is making all the code after that line show as “black”, meaning something is not coded correctly.

    I’m using PHP 7.2 but if I roll it back to 7.0, I still get the header error message and white screen for registrations if using a blocked page.

    All very confusing and a lot of mucking around to test. Plus I don’t know coding, just how to hack it enough to tweak or disable things.

    I have made the default message more informative to visitors, so quite happy to use it that way for now.

    Plugin Author rickstermuk

    (@rickstermuk)

    I have done some testing and I am unable reproduce this issue on the latest version of the plugin. All I can think is there is some kind of comflict with something else.

    Apoligies for not being of more help at this time.

    That’s okay. You can’t fix it if you can’t see it.

    The message box is good enough for use anyway.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.