• Resolved sankari

    (@sankari)


    Hi,

    Users get this PHP warning on the “Unsubscription confirmed” page:

    Warning: Undefined array key "list_name" in /home/httpd/vhosts/[domain.tld]/httpdocs/wp-content/plugins/email-subscribers/lite/includes/workflows/actions/class-es-action-send-email.php on line 189

    It seems to be related to the workflow “Subscriber: Unsubscribe email” as the warning does not appear if the workflow is inactive.

    Settings of the workflow:

    • Trigger: User Unsubscribed
    • Action: Send email
    • Send to: [a valid email address]
    • Email subject: [a subject with uppercase and lowercase letters, spaces and a colon]
    • Email content: [a single line of text, no tags]

    Icegram Express: 5.7.47
    PHP 8.2.25

    Thanks!

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Support Anupam Khatua

    (@anupamkhatua)

    Hi @sankari,

    Thank you for highlighting the issue!

    We have resolved the issue, and this fix will be included in the next release. Once the new version is available, I will promptly update you.

    Best,

    Thread Starter sankari

    (@sankari)

    Hey @anupamkhatua,

    That’s good news, thank you!

    Hello @anupamkhatua
    Same worry for me: for one year, all your versions have a warning when testing, as well as the last one (5.7.47): 2 PHP warnings ans 1 PHP notice.
    PHP Error Log for exemple:

    [02-Jan-2025 09:40:16 UTC] PHP Warning:  Array to string conversion in /wp-includes/formatting.php on line 1096
    [02-Jan-2025 09:40:18 UTC] PHP Warning:  Array to string conversion in /wp-includes/formatting.php on line 1096
    [02-Jan-2025 09:40:37 UTC] PHP Notice:  Function wp_enqueue_script() was called <strong>incorrectly</strong>. "wp-editor" script should not be enqueued together with the new widgets editor (wp-edit-widgets or wp-customize-widgets). Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.8.0.) in /wp-includes/functions.php on line 6114
    

    I like very much your plugin, but I dare not update it, nor update WP last version then. What can you do about it? Thank you very much.

    Plugin Support Anupam Khatua

    (@anupamkhatua)

    Hi @scribelle,

    Thank you for reaching out to us!

    I would like to clarify that the “wp-editor” is not enqueued by the Express plugin, so the error is not originating from our end. Additionally, the warning in the error message you provided does not reference the Express plugin. Therefore, we cannot determine if the error is related to the Express plugin.

    To investigate further, could you please install the Health Check plugin? Activate only the Express plugin and check if the error persists. Once you’ve done that, please share the report with us for further troubleshooting.

    We look forward to your response!

    Plugin Support Anupam Khatua

    (@anupamkhatua)

    Hi @sankari,

    I would like to inform you that we have resolved the queries from the latest release that you previously shared with us.

    I suggest that you update the plugin to the latest version, 5.7.48. After updating, please check and confirm if the queries have been resolved.

    Waiting for your input!

    Thread Starter sankari

    (@sankari)

    @anupamkhatua

    Thank you for resolving the issue!

    The warning doesn’t appear in version 5.7.48, therefore I’m closing this topic.

    Thanks!

    Hi @anupamkhatua
    First of all, thank you for your answer three days ago.
    For information, the error warnings are indicated by a plugin test that I use for ages and that is great: Plugintests.
    Whether for version 5.7.47 or version 5.7.48, nothing changed and the same warnings are still there. Look here:
    https://plugintests.com/plugins/wporg/email-subscribers/latest
    That is the reason why I’m still worried. 😉

    Thread Starter sankari

    (@sankari)

    @scribelle Oh, I am sorry, I was too early with marking the issue as resolved!

    Since those are different issues I suggest to create a new forum topic for them, but in the end I leave it up to you and @anupamkhatua how you want to handle it.

    • This reply was modified 3 months, 2 weeks ago by sankari.

    @anupamkhatua
    I see. Ok. Thank you.

    Thread Starter sankari

    (@sankari)

    @scribelle
    Sorry again for closing this topic too early.
    I created this topic for the issues you found and reported, so that the developers can look into it and update us.
    Have a great weekend!

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