Skip Navigation

[Resolved] toolset content template update button is not working.

This support ticket is created 3 years, 9 months ago. There's a good chance that you are reading advice that it now obsolete.

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
9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 - - 9: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: Africa/Casablanca (GMT+01:00)

This topic contains 2 replies, has 2 voices.

Last updated by Juice Rocket® 3 years, 9 months ago.

Assisted by: Jamal.

Author
Posts
#1948487

I am trying to: update my content template page but the update button is not working, I reported you this issue earlier too.
The support person asked me to deactivate the cache plugin and again to reactivate it and purge all the cache. After doing so update button starts working. But the problem . But now the problem has recurred. Please tell me permanent solution for this.
I turn on the debug mode ,the error in console are:
-wp.editor.RichText.Content is deprecated. Please use wp.blockEditor.RichText.Content instead.
-wp.editor.Inserter is deprecated. Please use wp.blockEditor.Inserter instead. deprecated.min.js:2:1625
-Button isDefault prop is deprecated. Please use isSecondary instead. deprecated.min.js:2:1625
-MouseEvent.mozPressure is deprecated. Use PointerEvent.pressure instead. tinymce.min.js:2:8856

#1948773

Hello and thank you for contacting the Toolset support.

Would you allow us temporary access to check this issue? Your next reply will be private to let you share credentials safely. ** Make a database backup before sharing credentials. **

I remember, in chat, that this did not happen for a new content template. For what content template the issue happen?

We may need to take a copy of your website for further analysis. Let us know if that's fine with you.

#1954569

My issue is resolved now. Thank you!