Viewing 9 replies - 1 through 9 (of 9 total)
  • @thetigerstrings

    It should be compatible without an update – the update would only confirm the authors have tested and believe it works.

    Is there something specific that you feel is incompatible?

    Thread Starter thetigerstrings

    (@thetigerstrings)

    I do not know what has happened – but after the upgrade to wordpress 4.5.2 the subscription widget did not work any more.
    see: http://www.tschirp.at

    @thetigerstrings

    The form is showing fine for me and gave the right error message on entering a non-valid email.

    Thread Starter thetigerstrings

    (@thetigerstrings)

    ok, thanks. It works now!

    Notice: get_currentuserinfo is deprecated since version 4.5! Use wp_get_current_user() instead. in /wp-includes/functions.php on line 3658.

    @lukecavanagh

    Thanks for spotting that, I can update Subscribe2 HTML and I’ll see if we can get Subscribe2 updated.

    I edited the 2 files in Subscribe2 which called that deprecated function, and so far so good – we’ve got notifications going out again. For reference, they are:

    subscribe2\admin\your_subscriptions.php: line 12, change to:
    $user_ID = get_current_user_id();

    There are other references in that file, but they are guarded by $this->s2_mu and we’re not using wpmu, so I didn’t bother checking / updating them. If you are using wpmu, you’d be advised to search and update the others too.

    subscribe2\classes\class-s2-frontend.php: line 124, change to:
    $user_ID = get_current_user_id();

    What’s odd is that in that second file at line 12, there is the correct version ($user_ID = get_current_user_id();), but elsewhere it uses get_currentuserinfo() so perhaps it’s not a permanent fix – i.e. does the code rely on the other globals which get_currentuserinfo() used to update? I did search for them all and didn’t find them, so I’m 95% confident in this fix.

    OK – that may have been a red herring. Apparently there are other things wrong on our hosting provider which may be implicated in emails not being sent. So fixing this perhaps didn’t really change anything 🙁

Viewing 9 replies - 1 through 9 (of 9 total)

The topic ‘Compatibility to wordpress 4.5.2’ is closed to new replies.