Resolved
In Blocks 1.6.15 we fixed an issue related to problems with Toolset Blocks and dynamic sources that affected templates and pages using dynamic sources.
A new issue has surfaced where opening the block editor can trigger other errors which prevent the editor from loading correctly.
In the browser console an error appears:
TypeError: e[t].toHTMLString is not a function
at index.js?ver=254000:2:583
from react-dom.min.js?ver=18.2.0
Fixed in Blocks 1.6.16.
Hi i set upload_max_filesize to 128M and installed both.
when i install and activate one of these beta’s i get a critical error when i try to edit the homepage 🙁
You should only have one version of Blocks or one version of Views installed and active.
You would want to deactivate whichever of these plugins you currently have installed, and add the beta of the same plugin and activate it. If you activate Views and Blocks at the same time it could produce an error.
If you only have one of either Blocks or Views active and it produces an error, could you please check your debug log for details of the error, create a support ticket, and share details of the error, thanks.
I’m seeing this problem (white screen when editing some pages) but we only use Types and Views. I isolated the problem to Views. Do I need to open a ticket for that, or are you working on the Views problem separately from Blocks?
On May 30 I updated the Views plugin to 3.6.15. WordPress updated to 6.5.4 on June 5. I first noticed the problem June 7.
php 8.1.28, Astra Pro theme.
Thank you, let me know.
Hi there. As described above, we will release a fix for this soon, but there are links to pre-release versions of Blocks or Views plugins including the fix if you don’t want to wait.
When will you release the fix? This is a crucial error.
There are a couple of other issues the developers want to complete to include in the same fix; it shouldn’t be much longer. I would encourage you to use the links above for versions of either Blocks or Views you can update with that include the fix for this problem.
When we updated to this beta version, we were unable to access containers.
> Your site doesn’t include support for the “toolset-blocks/container” block.
I tested on my local site if I encountered any problems with the Container block with the beta version, but everything worked as normal.
Could you please create a support ticket describing your problem, as we will likely need access to your site to investigate further.
Thanks
We have these problem still with new Blocks Version 1.6.16 on some pages.
Errormessage:
TypeError: Cannot read private member #e from an object whose class did not declare it
at get text (rich-text.min.js?ver=dd125966cf6cc0394ae0:2:9520)
at get length (rich-text.min.js?ver=dd125966cf6cc0394ae0:2:9401)
at WI.isEmpty (block-editor.min.js?ver=868d782fcb169133c92b:41:51967)
at VI (block-editor.min.js?ver=868d782fcb169133c92b:41:43290)
at B (element.min.js?ver=cb762d190aebbec25b27:9:6435)
at Z (element.min.js?ver=cb762d190aebbec25b27:9:7430)
at Y (element.min.js?ver=cb762d190aebbec25b27:9:6890)
at B (element.min.js?ver=cb762d190aebbec25b27:9:6189)
at Z (element.min.js?ver=cb762d190aebbec25b27:9:7430)
at Y (element.min.js?ver=cb762d190aebbec25b27:9:6890)
ar @ react-dom.min.js?ver=18.2.0:10
react-dom.min.js?ver=18.2.0:10
That looks like a different issue, the error isn’t the same.
Could you please open a support thread so that we can get more details from you, as we’ll likely need access to your site to try to identify the specifics of what triggers the error.