Hello asanacori,
Thanks for reaching out.
This warning shouldn’t normally appear. There are guardrails in place to prevent this situation, so it’s not clear why it’s happening in your case.
Could you let us know where exactly you see this warning? For example:
- Do you see it while performing a specific action in the admin?
- Or does it appear in logs only?
- Is any part of the email editor or sending functionality not working as expected?
This information will help us investigate further and suggest the right fix.
Hello,
this error appeared in the server log files, during normal usage activities of your plugin no error appears.
Thanks for getting back to us with more details!
Could you please follow the instructions to re-install the plugin via FTP and let us know if this error will go away? This will ensure no plugin files are missing or corrupted.
Don’t worry, you won’t lose any data from the plugin since it’s saved in your database, not the plugin files. However, whenever making any changes like this, we recommend making sure you have a full backup of the site just in case.
Hello.
I reinstalled the plugin manually but the error continues to be reported only in the logs:
AH01071: Got error ‘PHP message: PHP Warning: Undefined array key “blocks” in /wp-content/plugins/mailpoet/lib/Newsletter/Renderer/Blocks/Renderer.php on line 78
PHP message: PHP Warning: Undefined array key “blocks” in /wp-content/plugins/mailpoet/lib/Newsletter/Renderer/Columns/Renderer.php on line 12′
Indeed, in the newsletter in composition there are some content blocks that still need to be enhanced.
Hi @asanacori, have you installed version 5.12.8 which was released two days ago? It should include the fix, so if you still experience the issue, there might be different issue.
Hi Jan, I installed version 5.12.8 on my wordpress 5.12.8, now I always get an error message but only on line 12, namely: Got error ‘PHP message: PHP Warning: Undefined array key “blocks” in ../wp-content/plugins/mailpoet/lib/Newsletter/Renderer/Columns/Renderer.php on line 12’.
Hi @asanacori, there was indeed still a way to generate this warning. It’s fixed in this PR, and it should be included in the release next week (probably in version 5.12.10).
Hi @neosinner, I’ll wait, thank you.
Hi @asanacori, we just released version 5.12.10 – could you please try it out to see if it helped fix the issue?
Yes, the problem has been resolved, thank you.
