• Resolved major42

    (@major42)


    Hello,

    For an unknown reason, since a few weeks, no emails are being sent on my wordpress instance version 6.2.2. It may be since i update from 5.6.4, or a plugin update, but i’m not sure.

    On the system status page, i can see in “Last error” in the “Cron” section the following errors:

    While running PHP 8.0.30:

    SendingQueue: DOMDocument::loadHTML(): htmlParseEntityRef: expecting ';' in Entity, line: 230

    While running PHP 8.2:

    SendingQueue: mb_convert_encoding(): Handling HTML entities via mbstring is deprecated; use htmlspecialchars, htmlentities, or mb_encode_numericentity/mb_decode_numericentity instead

    Conflict test didn’t work because as soon as i activate Mailpoet in troubleshooting mode, it’s desactivated automatically by wordpress because of an (unknown) error.

    Is it a PHP version compatibility issue (i should run an older version) or a plugin conflict?

    Kind regards.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Gui A. a11n

    (@guicmazeredo)

    Hi there,

    Thanks for reaching out and for providing us with the error shown in System Status.

    We found a deprecation warning in the MailPoet plugin. Typically, a deprecation warning should not block email sending. I recommend checking if there is a custom error handling for PHP that could be causing these deprecation warnings to be thrown as exceptions.

    A fix for this issue will be released next week. In the meantime, if you have any further questions or need additional assistance, please don’t hesitate to reach out.

    We appreciate your patience and understanding as we work to resolve this issue for you.

    Thread Starter major42

    (@major42)

    Thanks for your feedback.

    Emails are working again, but i’m not sure why…! I don’t have any errors in the cron section anymore.

    The only change i could see is PHP version update from 8.2.20 to 8.2.21.

    Plugin Support Gui A. a11n

    (@guicmazeredo)

    Hey @major42 ! It’s curious that the error has gone before we release the update that was supposed to address this issue. But I’m happy to hear it autoresolved. ??

    Thanks for the update!

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