This has been an ongoing problem. The site admin will clone a page to make edits, but after trying to go back in to edit ends up with just a white screen. If I disable Toolset I can get back in. The only Toolset block (if any) used is the container.
I set up a copy of the site and installed the Gutenberg plugin to try to help troubleshoot (as otherwise no actual errors appear) and get this:
TypeError: e[t].toHTMLString is not a function
at hidden link
at Array.forEach (<anonymous>)
at a (hidden link)
at ya (hidden link)
at Na.<computed> (hidden link)
at hidden link
at hidden link
at $r (hidden link)
at Ur (hidden link)
at hidden link
What can we do to prevent this from happening? We are considering completely removing Toolset from the site if we can't resolve it.
Can you please try to use the following beta version of Toolset Blocks on ***staging*** site and check if that help you to resolve your issue.
- hidden link
If the beta version help you to resolve your issue, I suggest you should wait a bit and we will suppose to release official hotfix version in coming one or two weeks.
Great, that seems to get rid of the error. Are there any things to be aware of in using this beta in production now? Are there particular changes that might cause other issues, that we should be aware of in testing before doing so?
Also, we are getting a lot of "This block contains unexpected or invalid content." errors on the page we're trying to work with (with standard Gutenberg blocks). They all resolve when we click "Attempt Block Recovery" but we're still trying to get to the root of that problem. Is there a possibility of that being Toolset related? I did seem that the existence of these (needing bock recovery) is what caused that Toolset-related JS error which blocked editing, but I don't know if Toolset might be related to that issue itself.
Note - I know you said "If the beta version help you to resolve your issue, I suggest you should wait a bit and we will suppose to release official hotfix version in coming one or two weeks." but we really CAN'T. The client needs to be editing things now.
*** Please make a FULL BACKUP of your database and files from production.***
Then try to use the beta version I shared and check if that helps and works without any issue. However - You should first try and see on staging if everything seems normal then you may try to use beta version but again we do not recommond.
If you see any side-effect of Toolset Blocks beta version then you can revert back to the stable Toolset Blocks version.
Thanks. I would do that, and am using staging first.
My question is - based on the nature of changes with this beta, are there particular blocks/types of usage that I should be particularly on the lookout for issues with? Functionality that the beta could potentially have broken?
My question is - based on the nature of changes with this beta, are there particular blocks/types of usage that I should be particularly on the lookout for issues with? Functionality that the beta could potentially have broken?
===>
I do not have any idea about that and probably it will not brake anything but possibility are there.
When are you planning the final release of this update? The current version is causing MAJOR issues for our sites. The beta seems to resolve them, but I am hesitant to put that into Production.
*** Please make a FULL BACKUP of your database and website.***
Cam you please update ALL Toolset plugins to it's latest official release version and check if that help you to fix the issue.
