New text editor automatically minimizes HTML when saved

Support
#1

The old text editor didn’t do this. It makes long blocks of text extremely difficult to read when using the HTML/Source side. Also, as mentioned by others, it used to be that you could leave line breaks in the HTML/Source editor and wpautop worked to add in the paragraph tags without them showing up directly in the code – or us having to methodically ADD them everywhere now.

Finally, we also lost the basic formatting that used to be in the HTML/Source side such as bold and italic. I know they weren’t much, but it saved a lot of time to just highlight and apply. Now you can only do that on the “Rich Text” side. We’re losing more and more functionality with each update. Not good…

Is there a fix coming to make it so it doesn’t automatically minimize the html when saved???

1 Like
#2

Hi There,

I will add a feature enhancement request for the text on HTML/SOURCE code not to be automatically minimize but the paragraph tag is part of how the new editor works. This request will be discuss internally first before it is considered. We can’t promise and ETA but rest assured that everything will be taken into consideration. Thank you for understanding.

1 Like
#3

Thank you for the consideration!

#4

Reminds me of the old Microsoft FrontPage days!

So, let me get this straight … you take away functionality … and that’s an enhancement? Is that akin to calling a bug a feature?

#5

Disable plugins, lost functionality … but we’re making progress!

#6

How is it a feature request when it was once a feature but no longer a feature? Seems to be more of a feature-broke-undo …

#7

Just so we’re clear. I depend on X Theme for my client sites. It’s a real world endeavor, not a hobby. So, these unforced errors are grief causing.

And truthfully, are poorly reflecting on your company. Examine my history, you will see I’ve been around since day one, bought a bunch of copies … but have slowed down, as this sort of poor software development being exhibited by X isn’t reassuring…

#8

Hi there,

Our developers are still on it, current editor is implemented due to previous issues that had to be fixed. This is on our list/issue tracker as usability/improvement. The editor is not the same in Wordpress editor due to many reasons, that includes the filters that are bound to it. Example, the_content is the main hook where content is processed, and all line breaks are converted as a whole. With cornerstone, we can’t allow that so we need to make sure it’s applied to the text element only (the sub-editor). And it’s been part of the issues from the start, and by removing default filters and add our own. Please understand, we don’t intend to remove them for good, that’s just part of the process.

Thanks!

#9

Thank you for the update!

#10

You’re most welcome!

#11

OK, I just need to understand this correctly - the old text element would allow me to type, press Enter and type - voila, two paragraphs that would show up on the site as two paragraphs.

Now, those paragraph breaks (and line breaks for that matter) disappear when I save. So I have to manually insert paragraph tags?

Is this right?

#12

Hello @nevillec,

In the old version, the text element will automatically convert line breaks and newlines into <br> and <p> tags.

In the new classic text element and V2 Text element, you will have to select Rich Text first, and then insert your texts along with line breaks and new lines so that it will be converted in <br> and <p> tags on the front end.

If you want to manually insert paragraph and break tags, you must select the HTML text editor and insert your tags.

@IareChaz:
You must have missed that option to select html and rich text option when inserting the text content. This wasn’t available in the previous versions of the classic text element.

Hope this helps.

#13

Thanks for the feedback folks - I should have clarified that I am using the WPBakery Page Builder - and that is where I am running into problems. As you’ve pointed out Cornerstone does not have this problem.

I can’t remember exactly why I chose to go with the WPBakery builder in the first place, but having looked at Cornerstone again tonight I realize that I should have spent the time to learn Cornerstone when it came out. I’ve now decided to bite the bullet and do that - but in the long run I think it will be a Really Good Thing.

I do have a problem with pages built with Cornerstone not honouring the X Customizer styles (heading don’t appear correct, body font not right etc) but I will plug away a bit to see if I can solve that before I cry for help.

Thanks for a great product - and great support! Happy Thanksgiving.

#14

You’re most welcome!
If you need anything else we can help you with, don’t hesitate to open another thread.

#15

heh… solved the problem - need to use the Classic elements which seem more obedient to the theme settings :slight_smile:

Will learn more about why the non-classics are there tomorrow.

Thanks for the help - have a good night!

#16

As always you’re welcome.

#17

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.