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.
No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.
| 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: Asia/Hong_Kong (GMT+08:00)
This topic contains 3 replies, has 2 voices.
Last updated by Luo Yang 2 years, 7 months ago.
Assisted by: Luo Yang.
Hi all,
A couple of weeks ago I send a ticket that updating to WP 5.8 broke stuff. Ben at Kadence looked into this and came to the conclusion Toolset was stripping our styling after updating and this the issue.
This still open at Toolset support: https://toolset.com/forums/topic/updateing/
Yet again, another issue.
As it stands we can't update to WP 5.8 because Toolset breaks certain front end styling.
Now we update Toolset Blocks to the latest version and again, it breaks something else.
Similar issue, we are using a Kadence Image Overlay block set to Square 1.1. After update the blocks looks the same on backend, in front end the styling is being stripped out. No caching on this site, its a dev. So yet again we roll the site back and all ok.
I know these are all small things however both Kadence and Toolset promote they work well together and yet, we can't update WP, and now can't update Toolset Blocks.
All this does is remind of the bad ole days of dreading updates from Elementor when we used to use that theme.
Anyway, thought it worth a mention,
Thanks, Pete
The topic ‘[Closed] Toolset breaking something else with Kadence’ is closed to new replies.
