We just updated to the latest version of the plugin and discovered that the text widget is now adding line breaks
<br>inside of
<style>tags.
This broke all of our newly published posts, so we’ve had to start using the SiteOrigin Editor widget in its place, which is not really an ideal widget for adding raw html/css/js to posts.
Hope this can get fixed soon.
/Chris
Any update on this? These random break tags are causing massive problems for any page we try and update, and have more than doubled our workload. Not sure how this passed QA.
Hi Chris,
Unfortunately, we’re not responsible for the text widget, the core WordPress developers are. In WordPress 4.8, there was a large text widget overall to give it more of a standard TinyMCE feel. This is a welcome change but sadly certain things were disregarded – like the most common use for the text widget (adding HTML and JavaScript).
As you can guess, there was a huge outcry. In response, 4.8.1 introduced a new Hcustom TML widget (which is basically the old text widget < you should use this for HTML) and an updated text widget that should handle things slightly better but honestly… it's still not very good.
I'm sorry that you're having issues with this and I wish it was something that we could have prevented.
Oh crap… we have thousands of pages on 5 sites that are using that widget, and each time one gets updated (or cloned) it’s causing issues.
It seems that every time the text widget is opened it defaults to the “visual” view rather than “text” (despite being a TEXT widget), and that visual view is inserting all the garbage.
It appears to be a simple bug to resolve. It looks like they just neglected to account for tags. I noticed that any code between tags is not having line breaks (
) added, but any code between tags is.
I’m hoping a solution arrises that does not require us going through thousands of articles, adding a new type of widget, opening the old widget, copying its contents, deleting the old widget, and pasting the contents into the new widget. I can’t even imagine how many days that would take.
Appreciate the feedback!
Hi Chris,
I’ve previously used this plugin to disable the visual editor functionality for the text widget. I would give it a try but I’m unsure if it’ll allow you to avoid this issue.