Support » Plugin: Mailgun for WordPress » PHP Deprecated: Invalid characters passed for attempted conversion

  • robscott

    (@robscott)


    Plugin file:

    /wp-content/plugins/mailgun/includes/wp-mail-api.php on line 368

    $boundary = base_convert(uniqid('boundary', true), 10, 36);

    Throwing a deprecation warning in PHP 7.4. Posting here as I’m about to patch.

Viewing 5 replies - 1 through 5 (of 5 total)
  • I’m seeing a similar warning:

    
    PHP Deprecated:  Invalid characters passed for attempted conversion, these have been ignored in /plugins/mailgun/includes/wp-mail-api.php on line 332
    

    Same file, but different line.

    Thread Starter robscott

    (@robscott)

    @alexclst mine still is line 368. You may be on an older or edited version of the Mailgun plugin?

    This function pops up in a few SMTP plugins too – in a couple I’ve found how they’ve fixed this warning; in my case, we have replaced with custom code because we don’t need all the features of Mailgun’s plugin.

    • This reply was modified 5 months, 3 weeks ago by robscott.

    @robscott, it is possible that I once opened the plugin file, which may have then formatted it with my code editor. I definitely haven’t intentionally edited the plugin. It isn’t asking for an update, so I’m running the latest version. That is fine. If the error is the same, then it should be fixed in a later release regardless.

    @robscott what version is current, though? My sites that I use this on all have 1.7.1 with not being able to update further in any way, but I see in the changelog there is a 1.7.2. On the command line, when I try to reinstall the plugin with wp-cli, it complains of an inability to verify 1.7.2, and I guess just reinstalls 1.7.1. Maybe may server is somehow stuck at assuming 1.7.1 is current, and that is the heart of line numbering differences?

    Thread Starter robscott

    (@robscott)

    1.7.1 in mine. Yeah code editor adding double lines is highly possible 🙂

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