This thread is resolved. Here is a description of the problem and solution.
Problem:
The customer was unable to save their content template and encountered JavaScript errors when updating the Kadence Pro plugin, which prevented access to the content templates. The customer reported issues that seemed to stem from changes in WordPress 6.6, affecting Toolset dynamic sources.
Solution:
We escalated the issue to our second-tier support, who identified that the problem was due to changes in WordPress 6.6 affecting Toolset dynamic sources and resulting in JavaScript errors. We applied a workaround on the customer’s development site, which involved several steps:
- Deactivated Toolset Blocks.
- Registered a temporary custom post type for viewing templates.
- Made a minor edit to the affected template titles to enable the Update button.
- Saved the templates and then unregistered the custom post type.
- Reactivated Toolset Blocks and attempted to edit the repaired templates.
After applying these steps, the customer was able to access and edit the content templates successfully. A video was provided to demonstrate the process.
The customer confirmed that the workaround worked, resolving the issues with saving and accessing their content templates.
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.
I am having a few issues with content templates. Currently one I'm having is that I can't save my content template. I literally have to go out and go back in and do a restore. This is a major issue, as it doesn't always save in order to restore.
I am trying to: Save my content template
Here is one: Template for SL Locations
I also can not update the Kadence Pro plugin, once I do I can't get into the content templates at all. They just won't open. I have chatted with them and they state that there is javascript issues with your plugin.
Here is what they told me to tell you:
When using Kadence Blocks inside Toolset, they are overriding how our blocks function. Unfortunately, we don't have any control over how this is done. I don't know what is causing the error without looking at the Toolset source code. I would pass along this console error to their support and let them know it's happening when using a Kadence Image Overlay block inside a Content Template. They should have more insight into the issue and can hopefully provide a fix.
Uncaught TypeError: Cannot read private member #e from an object whose class did not declare it
at get text (rich-text.min.js?ver=4021b9e4e9ef4d3cd868:2:8521)
at get length (rich-text.min.js?ver=4021b9e4e9ef4d3cd868:2:8402)
at UT.isEmpty (block-editor.min.js?ver=f989eae66982c6c90d6e:21:739395)
I would like to request temporary access (wp-admin and FTP) to your site to take better look at the issue. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Our Debugging Procedures
I will be checking various settings in the backend to see if the issue can be resolved. Although I won't be making changes that affect the live site, it is still good practice to backup the site before providing us access. In the event that we do need to debug the site further, I will duplicate the site and work in a separate, local development environment to avoid affecting the live site.
- Please make a backup of site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: hidden link
Please, let me know if you need any additional details. Have a nice day.
I'd just like to confirm that this is a test/staging site, it looks that way based on the URL but I wanted to make sure that it is OK for me to perform changes in the site like disabling plugins, themes, etc.
I have escalated this ticket to our 2nd tier of support where our 2nd tier specialists will take a deeper look at this issue and will try to find a solution.
I will get back to you as soon as I get an answer from them.
Our 2nd tier team identified that the issue stems from changes in WordPress 6.6 which broke Toolset dynamic sources resulting in the same JS errors that can be seen when trying to edit a Content Template on the site. We fixed that issue in Blocks 1.6.16. Kadence may have been affected by the same problem, and they look to have fixed it in a recent release of their Pro extension. But when editing a Content Template including the Kadence blocks, those same errors prevent Kadence from upgrading its own blocks to fix the problem, and in this context we are stuck.
To resolve this, I applied a workaround to the "Template for SL Locations" on your development site. The steps I took are as follows:
- Deactivate Toolset Blocks
- Register a post type with slug of "view-template" using Custom Post Type UI, this will add a Dashboard menu option for the post type. Use this to view a list of templates.
- Edit an affected template (e.g. the "Template for SL Locations")
- You will need to make a tiny change to release the Update button; I suggest just adding a space at the end of the template title
- Save the template, and repeat for any other affected templates
- Unregister the post type "view-template"
- Re-activate Toolset Blocks
- Go to Toolset > Content Templates and try to edit one of the repaired templates
After these steps, I was able to open and edit the template successfully.
I’ve recorded a video demonstrating the process: hidden link
Please review the development site and confirm everything is working as expected. Once confirmed, you can apply the same steps to your live site.
