errors with new update 2.2.2

  • Resolved chezsheles

    (@chezsheles)


    7 years, 5 months ago

    Hi,

    After you kindly updated age gate plugin so that iphone users would not be redirected to the middle of a page after adding in their dates of birth, (version 2.2.2) I am now seeing new errors.

    This is from our debug log:
    [26-Dec-2018 15:41:24 UTC] PHP Warning: array_filter() expects parameter 1 to be array, integer given in /home/ wp-content/plugins/age-gate-2.2.2/admin/class-age-gate-advanced.php on line 100
    [26-Dec-2018 15:43:23 UTC] PHP Warning: array_filter() expects parameter 1 to be array, integer given in /home/ wp-content/plugins/age-gate-2.2.2/admin/class-age-gate-advanced.php on line 100
    [26-Dec-2018 15:50:16 UTC] PHP Notice: Undefined index: lang in /home/ wp-content/plugins/age-gate-2.2.2/admin/class-age-gate-messaging.php on line 111

    And – this might not be at all related to Age Gate – all of my settings and special css has disappeared from the site. We are using a caching plugin. But when I updated the latest version of your plugin, and then tested it, the styles remained as they should be.

    A few days later now we’re seeing it all gone.

    Do the error messages above have anything to do with this?

    Also, when going to another page on the site — the age gate appears again and won’t let us in.

    Any help with this is much appreciated. Thanks again.

Viewing 1 replies (of 1 total)
  • Plugin Author Phil

    (@philsbury)

    7 years, 5 months ago

    Hi @chezsheles,

    I found the first error and that should be fixed in 2.2.3 when I get that out. I’ll need to check the line 111 one as I’ve not seen that one. Neither should cause any issues though really. Hopefully have this fixed and updated this week.

    Where are you setting the custom CSS that was missing? Age Gate shouldn’t interfere with any other settings, though I have had reports with Divi that there’s sometimes a conflict with their styles, though I haven’t been able to reproduce it myself.

    THanks
    Phil

Viewing 1 replies (of 1 total)

The topic ‘errors with new update 2.2.2’ is closed to new replies.