Warning: Undefined array key

thanks for reporting this issue with a very clear screenshot.

I’m going to look into it and hope to fix it soon.

Would you help me with the following information:

– the version of the plug-in – the version of your WordPress installation

– do you use the block directly, or the widget (via legacy widget block)

– Did you refresh the data after the last update with the Reset Id button (in advanced settings) or would you like to try that again?

Regards Bram

Plugin version 2.1.4
WordPress version 6.3
I use the widget
Tried th e ResetID button, no change

Regards Johan

thank you Johan, that helps me trying to reproduce the issue.

This is no excuse, I will try to solve the problem anyway

But warnings should not be shown in a production environment. It looks like your site has got a line

Define('WP_DEBUG', true)

in the wp-config.php file. This line should not be in production. If you remove it, or change true to false, the warnings will no longer be visible.

This could be a work a round for now.

Regards Bram

Hi Johan,

I managed to reproduce the issue and find a solution.
Fix implemented in version 2.1.5.

Reproduction:

1. Back to version 2.1.0., here less settings are available.
2. Insert legacy widget with similar settings. DB is now missing the new settings such as blockid.
3. Debug on: no warnings.
4. Update to v2.1.4. Refresh screen: Warnings about undefined array keys appear.

Solution 1: Update plugin to v2.1.5. Implemented in v2.1.5: All settings are now also initialized with legacy widget (this already happens with block, because settings are only saved there if they differ from the default).
No more warnings.

Solution 2: Transform Legacy widget block to ‘Simple ical Block’, warnings are also gone. Solution is not always possible, for example because page builders such as Elementor only support Legacy Widgets.

Solution 3: Change a setting and save it most warnings disappear. (unfortunately the one about anchorId remains plus in php 8 Deprecated messages) and disable debug.

Thanks for reporting the issue and apologies for the inconvenience.

Regards Bram

Problem solved with last version 2.1.5.

Many thanks for your fast respons and fix!

Regards Johan