Editor in 1.2

[bttrym8]

I’ve run across a few problems with the editor since upgraded to 1.2.

1. If i use the new V2 text element, the preview isn’t loaded on the blog page. It appears completely empty.
2. Prior to update, i was able to copy/paste text from Word/YouTube etc into the Rich Text portion of the cornerstone editor. I could then switch over to the HTML portion and edit out extra spaces or random chunks of HTML that made it look poor. Now, when i switch from Rich Text to HTML, it seems to minify everything and remove all spacing, making it nearly impossible to clean up the HTML. (This also occurs if i paste from HTML to Rich Text).

Currently, i’m having to use the classic text element if i want previews to load on the main blog page. I haven’t figured a workaround for the Rich to HTML editor portion.

[bttrym8]

Summary

web url is https://elknetwork.com

[christian]

Hey @bttrym8,

1.) I’m sorry but I don’t understand what you mean by:

@bttrym8

the preview isn’t loaded on the blog page. It appears completely empty.

If you mean the excerpt of the content, that will be the case because the new V2 elements stores its contents in the post meta rather than in the content. If that is no what you mean, please give us a screenshot of this.

2.) This is currently the case so what I recommend for now is use the Rich Text editor if you want a visual editor. If you want to convert text from Word to HTML, you can use the Plain text mode of the Rich Text editor or use this site https://word2cleanhtml.com/.

Thanks.

[bttrym8]

1. Yes, excerpt is what i meant - brain fart. What’s the reasoning behind having a text box that doesn’t fill in the excerpt? It seems like that just adds an extra step to the whole process. I’m sure you guys had a reason for it.

2. Unfortunately, if you paste directly into the rich text editor, it will add random spaces in certain places. I’ll give that site a shot and see what happens. If you use the plain text mode, we lose all formatting. Curious as to why this was changed in the first place?

Thanks for the quick response Christian.

[friech]

Hi There,

As Christian said above, V2 elements store its contents in the post meta rather than in the content, But that should not be a problem as WordPress provides an excerpt meta box.

Directly pasting a copy text from the internet to Visual editor (Rich Text) is a no-no, as you’ll end up copying a lot of unnecessary HTML tags, Classes, IDs, and other attributes. Worst, it is possible that you can copy a malformed HTML tag and break your markup. You should paste it into a Text editor first to get rid of the unnecessary HTML tags and its attributes and then format it manually.

Thanks,

[bttrym8]

Thanks Friech, as I said above, i’m curious “why” the V2 element is portrayed that way.

As for the Visual Editor, it worked fine on the previous version of cornerstone. When switching back into the HTML view, i could edit unnecessary tags/attributes/etc that you were referencing IF they were there. Often times, from YouTube or from a Word document, they weren’t there. However, now that it minifies everything, it’s impossible to go through and do it. Pasting into a text editor requires me to go back through and add bold, to add hyperlinks and other formatting pieces and greatly extends my process-flow.

I’m sure that you believe it’s a “no-no,” but it made significantly more work for putting content onto the site.

My questions above weren’t meant to berate your changes, but merely to ask “why” and what the reasoning for it was.

[christopher]

Hi there,

Thank you for your message. It seems that the minification was an extra try to make the theme as lightweight as possible but I see now this may cause issues for guys like you which use the approach of pasting the stuff in the visual editor, and then try to clean up the HTML code in the plain text mode.

I will inform our development team regarding this specific use case. They will check the case and decide further if they will change the minification process or not.

At the time being, I suggest that you add a page in the WordPress and use the normal editor of the WordPress itself to do the cleanup in a separate browser tab, and paste the final code in the plain text mode of the V2 element editor.

I know it is an extra step and it may slow down your development process, but unfortunately, we do not have anything more to offer at the time being for this kind of usage.

Thank you for your understanding.

[bttrym8]

Christopher,

First off, i just want to say thank you. It seems like so often, genuine concerns like the one i was raising above, get met with animosity and defensiveness from developers. More often than not, it comes across as “We did it this way because it’s right! You’re an idiot for the way you do things!”

This is honestly one of the first times i’ve had a developer or staff say that they understand my problem. That is all I want when i post here. I completely understand where the intentions of the code change came from, and it IS probably for the better. I am most likely the minority in how i do my current process flow.

Your suggestion, albeit a little ugly, seems to work decently for me. So I am happy and satisfied. I sincerely appreciate the EFFORT!

[Joao]

Thanks for the kind words.

Have a great evening!