Skip Navigation

[Resolved] Impossible to edit page since WP update to 6.5.5

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Kolkata (GMT+05:30)

This topic contains 5 replies, has 3 voices.

Last updated by Minesh 6 months, 3 weeks ago.

Assisted by: Minesh.

Author
Posts
#2704398

I am trying to:
Edit a page

Link to a page where the issue can be seen:
hidden link (white page when trying to edit)

I expected to see:
an editable page

Instead, I got:
react-dom.min.js?ver=18.2.0:10 TypeError: e[t].toHTMLString is not a function
at index.js?ver=254000:2:583
at Array.forEach (<anonymous>)
at a (index.js?ver=254000:2:505)
at ya (index.js?ver=254000:2:265188)
at Na.<computed> (index.js?ver=254000:2:269307)
at index.js?ver=254000:2:782480
at load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,hoverIntent,utils,wp-polyfill-inert,regenerator-runtime,wp-polyfill,wp-hooks&ver=6.5.5:15:2773
at Ur (blocks.min.js?ver=6612d078dfaf28b875b8:19:9393)
at Fr (blocks.min.js?ver=6612d078dfaf28b875b8:19:9485)
at blocks.min.js?ver=6612d078dfaf28b875b8:19:38594

#2704419

Mateus Getulio
Supporter

Languages: English (English )

Timezone: America/Sao_Paulo (GMT-03:00)

Hi,

Thanks for contacting us.

Before your ticket is assigned to one of my colleagues, please allow me to walk you through some initial debugging steps. This will help speed up the support process.

Can you please test minimal, using a default theme(if applicable) and with all non-Toolset and essentials plugins disabled to see if the error persists. If possible make a backup of the site before doing it or test on a staging copy.

In addition to that, I'd like your help enabling the debug mode to help us track the error down, please add the following code to the wp-config.php file:

// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
  
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );
  
// Disable display of errors and warnings 
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
  
// Use dev versions of core JS and CSS files (only needed if you are modifying these core files)
define( 'SCRIPT_DEBUG', true );

Please check following links to read more about debugging with WordPress.
- https://codex.wordpress.org/Debugging_in_WordPress
- https://codex.wordpress.org/Debugging_in_WordPress#Example_wp-config.php_for_Debugging

After adding the code above, please try to reproduce the issue again and check if you'll find a debug.log file inside the wp-content folder.

If you locate it there, please send us the last lines here in the ticket.

After you send the WP debug logs, we'll analyze them and get back to you with further steps.

Looking forward to helping you resolve this issue.

#2704422

Hi Mateus,

Yes, we tried disabling plugins already, but to no avail. The only meaningful debug log we are having is deprecation notice on Toolset code:
[25-Jun-2024 20:41:30 UTC] PHP Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in .../wp-content/plugins/types/vendor/toolset/types/embedded/admin.php on line 168
[25-Jun-2024 20:41:30 UTC] PHP Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in .../wp-content/plugins/types/vendor/toolset/types/embedded/admin.php on line 168

#2704602

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hello. Thank you for contacting the Toolset support.

This seems to be known issue and here is the errata page.
- https://toolset.com/errata/block-editor-failing-to-open-for-some-pages/

I suggest you should create a staging site and install the shared beta version with above errata on your staging site and check if that help you to resolve your issue.

If it works then wait a bit and we do have plan to release official hotfix version in couple of weeks. You can even use the beta version on your production site but we do not recommond it.

#2704618

Hi and thank you. We tried to install the pre-release version of Block, which crashed the whole site and got that debug log, FYI:
[26-Jun-2024 09:55:37 UTC] PHP Fatal error: Could not check compatibility between OTGS\Toolset\Twig\Node\Node::getIterator(): OTGS\Toolset\Twig\Node\Traversable and IteratorAggregate::getIterator(): Traversable, because class OTGS\Toolset\Twig\Node\Traversable is not available in /var/www/next.dcvmn.net/htdocs/wp-content/plugins/toolset-blocks/vendor/toolset/toolset-common/lib/Twig/src/Node/Node.php on line 179

We finally reinstalled the current release and the bug is gone, surprisingly.
Thanks anyway !

#2704841

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

That is great and strange as well.

Can you please try to use the following latest beta version of Toolset Blocks on ***staging*** site first and check if that help you to resolve your issue.
- hidden link

If the beta version help you to resolve your issue with your **staging** site, I suggest you should wait a bit and we will suppose to release official hotfix version in coming one or two weeks.