WordPress.org

Ready to get started?Download WordPress

Forums

WordPress Firewall 2
Warning after Setting Whitelisted IPs (18 posts)

  1. Melowout
    Member
    Posted 3 years ago #

    Warning notice I received upon setting IPs:
    Warning: unserialize() expects parameter 1 to be string, array given in /home2/whispev2/public_html/dream/wp-content/plugins/wordpress-firewall-2/wordpress-firewall-2.php on line 567

    Is this an issue with the plug-in or the theme? What needs to be done to resolve?

    http://wordpress.org/extend/plugins/wordpress-firewall-2/

  2. pavy
    Member
    Plugin Author

    Posted 3 years ago #

    I'll check on this and get back to you.

  3. elianab
    Member
    Posted 3 years ago #

    I am getting the same warning notice.

  4. rreddick
    Member
    Posted 3 years ago #

    Me too.

  5. wpsecuritylock
    Member
    Posted 3 years ago #

    I just got the same error too. Any news on how to fix this?

  6. SeanFromIT
    Member
    Posted 3 years ago #

    Ditto. I also get it if I try setting a whitelisted form variable.

  7. manton
    Member
    Posted 3 years ago #

    Hey,

    I get the same warning message. When I click on "set email" box above this, without changing anything, the error message goes away. I don't know if this fixes anything. Just thought I'd put in my 2 cents. Any thoughts?

  8. pavy
    Member
    Plugin Author

    Posted 3 years ago #

    Everyone,

    I will be releasing an update for WordPress Firewall 2 in the next week or so. This version should (hopefully) correct this issue, among others.

    Thank you for your feedback! It's appreciated.

  9. theroundwell
    Member
    Posted 3 years ago #

    Same with me:

    Warning: unserialize() expects parameter 1 to be string, array given in /public_html/wp-content/plugins/wordpress-firewall-2.php on line 606

    Warning: unserialize() expects parameter 1 to be string, array given in /public_html/wp-content/plugins/wordpress-firewall-2.php on line 607

  10. theroundwell
    Member
    Posted 3 years ago #


  11. Kalrog
    Member
    Posted 3 years ago #

    I'm still seeing this message (exactly as theroudwell mentioned - down to the line numbers). Has there been an update or any information I can add?

  12. ScroogeHDL
    Member
    Posted 3 years ago #

    Still get basically the same message, but for line 567 as at the beginning of this thread. Also, if I add my IP to the Whitelist, it has no effect.

  13. Piet
    Member
    Posted 3 years ago #

    same problem here

  14. Tippy
    Member
    Posted 2 years ago #

    So what's going on with this? I'm still getting this error for line 567. It's been months Pavy. Why don't you answer with a fix for this?

  15. Tippy
    Member
    Posted 2 years ago #

    Thought I would check on this thinking that the web developer Matthew Pavkov would reply to this problem with WP Firewall 2.

    But he hasn't.

    He said he had a fix but it didn't fix nothing.

    Why am I getting this warning?

    /home/xxxxxx/public_html/mydomain.com/wp-content/plugins/wordpress-firewall-2/wordpress-firewall-2.php on line 567.

    This has been asked in WP forum but you have done nothing about this warning.

    Why, after months, is this still an issue?

  16. tryminenow
    Member
    Posted 2 years ago #

    Well instead of paying out on the guy try using WP Firewall original and see how that goes.

  17. pavy
    Member
    Plugin Author

    Posted 2 years ago #

    I understand everyone's frustration with this issue. Please understand that my full-time job must come before this, as well as many other things.

    I do fully intend to update WordPress Firewall 2 as soon as possible. I've had some fixes and a few new features already done, literally for months now. I know I said it would be much, much sooner; I know a lot of time has gone by. Regardless of how much I can get done in the next 1-2 weeks, I will release an update, so you all can see at least some progress.

    Please continue to report issues - I do check this forum, I am aware of the most annoying problems, and I do intend to have at least the serialize/unserialize issue fixed in this update.

    A final note, the serialize/unserialize errors are not fatal errors. WF2 will continue to operate, even when encountering these errors. If you have WF2 installed, even if you get these errors, the plugin is still protecting your site.

  18. dajuan
    Member
    Posted 2 years ago #

    Pavy, just installed your plugin after viewing a security presentation and encountered the same warnings. Thanks for the assurance the plugin is still providing security as we await the update!

    Regards,
    Dajuan

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic