[Waiting for user feedback] Critical error on editing pages when plugin is active.

[Author]

Posts

[audreyK]

I am currently trying to move my system over from WP Plugins Map Pro to your Maps/views as I really like your layout and system. Super cool except the plugin now won't work after I put a map on the page next to the view. I followed all the steps but it seems to have crashed.

My system is back to normal after deactivating the toolset plugins but really want it to work. Could the Maps Pro plugin be causing a conflict?

amindfulwalk.com

[Christopher Amirian]

Hi,

Welcome to Toolset support. Would you please nable the WordPress debug log to see what is the actuall error under the hood that is causing the issue?

Would you please access your website files and edit the "wp-config.php" file on the root folder of your WordPress installation and add the code below into the file:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', true );

Please add the code above the line below:

/* That's all, stop editing! Happy blogging. */

For more information:
https://wpml.org/documentation/support/debugging-wpml/

Please get back to us wth the error and I will be happy to follow up.

Thanks.

[audreyK]

Hi,

This is what comes back and it is literally a foreign language to me. Do I need to update my php?

Thanks for your help with this!

Audrey

1 PHP Fatal Uncaught TypeError: Cannot access offset of type array on array
Stack trace:
#0 /wp-content/plugins/toolset-maps/includes/toolset-common-functions.php(1473): Toolset_Addon_Maps_Common::get_coordinates_new(Array, false)
#1 /wp-content/plugins/toolset-maps/application/controllers/compatibility/gutenberg/editor-blocks/blocks/map/MapBlock.php(658): Toolset_Addon_Maps_Common::get_coordinates(Array)
#2 /wp-content/plugins/toolset-maps/application/controllers/compatibility/gutenberg/editor-blocks/blocks/map/MapBlock.php(599): OTGS\Toolset\Maps\Controller\Compatibility\Gutenberg\EditorBlocks\Blocks\Map\MapBlock->render_marker_from_address('map-4', Array, Array)
#3 /wp-content/plugins/toolset-maps/application/controllers/compatibility/gutenberg/editor-blocks/blocks/map/MapBlock.php(551): OTGS\Toolset\Maps\Controller\Compatibility\Gutenberg\EditorBlocks\Blocks\Map\MapBlock->render_markers_from_multiple_addresses('map-4', Array, Array)
#4 /wp-includes/class-wp-block.php(599): OTGS\Toolset\Maps\Controller\Compatibility\Gutenberg\EditorBlocks\Blocks\Map\MapBlock->render(Array, '', Object(WP_Block))
#5 /wp-includes/class-wp-block.php(579): WP_Block->render()
#6 /wp-includes/class-wp-block.php(579): WP_Block->render()
#7 /wp-includes/blocks.php(2383): WP_Block->render()
#8 /wp-includes/blocks.php(2466): render_block(Array)
#9 /wp-includes/class-wp-hook.php(341): do_blocks('<!-- wp:kadence...')
#10 /wp-includes/plugin.php(205): WP_Hook->apply_filters('<!-- wp:kadence...', Array)
#11 /wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php(1972): apply_filters('the_content', '<!-- wp:kadence...')
#12 /wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php(666): WP_REST_Posts_Controller->prepare_item_for_response(Object(WP_Post), Object(WP_REST_Request))
#13 /wp-includes/rest-api/class-wp-rest-server.php(1292): WP_REST_Posts_Controller->get_item(Object(WP_REST_Request))
#14 /wp-includes/rest-api/class-wp-rest-server.php(1125): WP_REST_Server->respond_to_request(Object(WP_REST_Request), '/wp/v2/pages/(?...', Array, NULL)
#15 /wp-includes/rest-api.php(594): WP_REST_Server->dispatch(Object(WP_REST_Request))
#16 /wp-includes/rest-api.php(2981): rest_do_request(Object(WP_REST_Request))
#17 internal function: rest_preload_api_request(Array, '/wp/v2/pages/64...')
#18 /wp-includes/block-editor.php(762): array_reduce(Array, 'rest_preload_ap...', Array)
#19 /wp-admin/edit-form-blocks.php(114): block_editor_rest_api_preload(Array, Object(WP_Block_Editor_Context))
#20 /wp-admin/post.php(187): require('/home/sites/40a...')
#21 {main} thrown in /wp-content/plugins/toolset-maps/includes/toolset-common-functions.php on line 1285
Plugin: Toolset Maps
File: /wp-content/plugins/toolset-maps/includes/toolset-common-functions.php
Line: 1285 Dec 18, 2025 - 15:53:03
(1 occurrence logged)
2 PHP Deprecated ltrim(): Passing null to parameter #1 ($string) of type string is deprecated
WordPress core
File: /wp-admin/formatting.php
Line: 4496 Dec 18, 2025 - 15:52:34
(7 occurrences logged)
3 PHP Deprecated Return type of WPML\Collect\Support\Collection::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Plugin: OTGS Installer
File: /wp-content/plugins/otgs-installer-plugin/vendor/wpml/collect/src/Illuminate/Support/Collection.php
Line: 1220 Dec 18, 2025 - 15:51:31
(2 occurrences logged)
4 PHP Deprecated Return type of WPML\Collect\Support\Collection::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Plugin: OTGS Installer
File: /wp-content/plugins/otgs-installer-plugin/vendor/wpml/collect/src/Illuminate/Support/Collection.php
Line: 1251 Dec 18, 2025 - 15:51:31
(2 occurrences logged)
5 PHP Deprecated Return type of WPML\Collect\Support\Collection::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Plugin: OTGS Installer
File: /wp-content/plugins/otgs-installer-plugin/vendor/wpml/collect/src/Illuminate/Support/Collection.php
Line: 1272 Dec 18, 2025 - 15:51:31
(2 occurrences logged)
6 PHP Deprecated Return type of WPML\Collect\Support\Collection::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Plugin: OTGS Installer
File: /wp-content/plugins/otgs-installer-plugin/vendor/wpml/collect/src/Illuminate/Support/Collection.php
Line: 1331 Dec 18, 2025 - 15:51:31
(2 occurrences logged)
7 PHP Deprecated Return type of WPML\Collect\Support\Collection::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Plugin: OTGS Installer
File: /wp-content/plugins/otgs-installer-plugin/vendor/wpml/collect/src/Illuminate/Support/Collection.php
Line: 1316 Dec 18, 2025 - 15:51:31
(2 occurrences logged)
8 PHP Deprecated Return type of WPML\Collect\Support\Collection::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Plugin: OTGS Installer
File: /wp-content/plugins/otgs-installer-plugin/vendor/wpml/collect/src/Illuminate/Support/Collection.php
Line: 1304 Dec 18, 2025 - 15:51:31
(2 occurrences logged)
9 PHP Deprecated Return type of WPML\Collect\Support\Collection::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Plugin: OTGS Installer
File: /wp-content/plugins/otgs-installer-plugin/vendor/wpml/collect/src/Illuminate/Support/Collection.php
Line: 1293

[audreyK]

Here is a different view:

WordPress version 6.9
Active theme: Kadence (version 1.3.6)
Current plugin: Toolset Maps (version 2.2.1)
PHP version 8.3.28

Error Details
=============
An error of type E_ERROR was caused in line 1285 of the file /home/sites/40a/8/8913390e95/public_html/wp-content/plugins/toolset-maps/includes/toolset-common-functions.php. Error message: Uncaught TypeError: Cannot access offset of type array on array in /home/sites/40a/8/8913390e95/public_html/wp-content/plugins/toolset-maps/includes/toolset-common-functions.php:1285
Stack trace:
#0 /home/sites/40a/8/8913390e95/public_html/wp-content/plugins/toolset-maps/includes/toolset-common-functions.php(1473): Toolset_Addon_Maps_Common::get_coordinates_new(Array, false)
#1 /home/sites/40a/8/8913390e95/public_html/wp-content/plugins/toolset-maps/application/controllers/compatibility/gutenberg/editor-blocks/blocks/map/MapBlock.php(658): Toolset_Addon_Maps_Common::get_coordinates(Array)
#2 /home/sites/40a/8/8913390e95/public_html/wp-content/plugins/toolset-maps/application/controllers/compatibility/gutenberg/editor-blocks/blocks/map/MapBlock.php(599): OTGS\Toolset\Maps\Controller\Compatibility\Gutenberg\EditorBlocks\Blocks\Map\MapBlock->render_marker_from_address('map-4', Array, Array)
#3 /home/sites/40a/8/8913390e95/public_html/wp-content/plugins/toolset-maps/application/controllers/compatibility/gutenberg/editor-blocks/blocks/map/MapBlock.php(551): OTGS\Toolset\Maps\Controller\Compatibility\Gutenberg\EditorBlocks\Blocks\Map\MapBlock->render_markers_from_multiple_addresses('map-4', Array, Array)
#4 /home/sites/40a/8/8913390e95/public_html/wp-includes/class-wp-block.php(599): OTGS\Toolset\Maps\Controller\Compatibility\Gutenberg\EditorBlocks\Blocks\Map\MapBlock->render(Array, '', Object(WP_Block))
#5 /home/sites/40a/8/8913390e95/public_html/wp-includes/class-wp-block.php(579): WP_Block->render()
#6 /home/sites/40a/8/8913390e95/public_html/wp-includes/class-wp-block.php(579): WP_Block->render()
#7 /home/sites/40a/8/8913390e95/public_html/wp-includes/blocks.php(2383): WP_Block->render()
#8 /home/sites/40a/8/8913390e95/public_html/wp-includes/blocks.php(2466): render_block(Array)
#9 /home/sites/40a/8/8913390e95/public_html/wp-includes/class-wp-hook.php(341): do_blocks('

[Christopher Amirian]

Hi,

Thank you for the information. This does not seem to be a PHP version issue. The fatal error happens when Toolset Maps tries to read coordinates but receives an unexpected value (array instead of a single address/coordinate) for one of the markers.

1) Quick isolate (find the broken marker)

-Edit the page that has the Toolset Map block (the log shows map-4).
-Temporarily remove the Map block and confirm the editor opens normally.
-Add it back, but reduce markers/source (start with 1 item) until the error returns — the last added item usually has the problematic address data

2) Fix the marker source

Make sure the marker is using a Toolset Address field (not a repeating field / not a field group / not empty). Toolset Maps expects a single address value per marker.

3) Check if you have updated Toolset plugins:

- IMPORTANT STEP! Create a backup of your website. Or better approach will be to test this on a copy/staging version of the website to avoid any disruption of a live website.
- Go to "WordPress Dashboard > Plugins > Add new > Commercial (tab)".
- Click the "Check for Updates" button.
- Update Toolset and its addons there.

4) Check for a possible plugin conflict:

- IMPORTANT STEP! Create a backup of your website. Or better approach will be to test this on a copy/staging version of the website to avoid any disruption of a live website.
- Switch to the default theme such as "TwentyTwenty" by going to "WordPress Dashboard > Appearance > themes".
- Go to "WordPress Dashboard > Plugins" and deactivate all plugins except:
. Toolset Types
. Toolset Blocks/Views
. Toolset Maps
- Check if you can still recreate the issue.
- If not, re-activate your plugins one by one and check the issue each time to find out the plugin that causes the problem.

Thanks.