Strange formatting issue since recent updates

[fogonthetyne]

Hi Guys,

Since the recent updates, I’m finding some serious layout issues on my site.
I’ve being using X-Theme for a while, so most of my text is built with “Classic Text”…

If I go in to edit/add to any of my text within a Cornerstone block, without even typing, it suddenly reformats, changing my linebreaks. I’m not sure of the terminology, but where I’d shift-returned before, full line breaks with a gap now appear.

So, where my site would have had:

Interviewee Name: John Smith
Specialised in photography and writing
See the interview here

It now reads:

Interviewee Name: John Smith

Specialised in photography and writing

See the interview here

Except, I have lists of these things, so the page has gone a bit crazy.

I’m very interested in any thoughts/help!

Thanks,

Andy

P.S.
The site is a subscription based membership site, so may be a little more complicated if anyone is wanting to dive into it.

[jade]

Hi Andy,

A fix was pushed out in X 6.1.4, and Cornerstone 3.1.4 which includes relevant fixes for this issue. The previous version was filtering out the

tags added by WordPress around the content bands. Please update to the latest version.

Let us know how it goes!

[fogonthetyne]

Hi Jade,

I’m on today’s updates, so X 6.1.5 and Cornerstone 3.1.5

Just some notes on my experience today, in case it’s useful to anyone else.

The pages that were damaged with this issue were still irreparable… effected elements could not be altered/reformatted - they have a life of their own defying any logic. Even brand new “classic text” elements on these pages isn’t working for me. These are new elements with no old code/text in them.

What I have managed to do is re-create the required parts of these pages using the modern text elements (not "classic text). Copy and pasting the old text into these new elements, via wordpad, to lose any formatting. I’ve then had to format it all as desired and re-add in all of the hyperlinks.

At a guess, there might still be an underlying issue here with the classic elements… or, perhaps it was just me, as my site encountered this issue before the fixes and something was still an issue in the background…

So, I think I’m good - but I’m not 100% convinced whatever the issue is will be gone going forward.

[fogonthetyne]

In fact, scratch that, I’ve just gone to alter it and it’s all gone haywire again.

I think someone might have to have a look at this - it might be an issue only I’m having, but my formatting is still mad on this page.

[fogonthetyne]

I’ve done a spot more testing, and I’ll leave it there for now.

I created a brand new page, and imported one of my templates.

Typing in one of the “classic text” elements, formatting does indeed not work as I’d expect. When typing the text as “text”, rather than as HTML, both a return and a shift-return do the same thing, a full line-break with a gap. So, putting a line underneath a line without a gap, isn’t possible.

Also, when block selecting a full body of text to change the alignment, various sentences behave differently from one another.

I’m not sure if this issue is just me, but it’s peculiar.

[Prasant]

Hello @fogonthetyne,

Thanks for updating the thread and sharing the details.

The problem you are facing is quite odd. Can you please share website login details along with URL and FTP login details in a secure note for us to take a closer look?

Thanks.

[fogonthetyne]

Hi Prasant, replying now - will attach a secure note. Thanks.

[Alaa]

Hi @fogonthetyne

I’ve tested that at my end and I can reproduce this issue on the Classic Text Element, not the V2 one, this screenshot shows that pressing “Return” key and “Shift+Return” results in the same look (new <p> tag instead of <br> inside a <p> tag).

I’ve reported this issue to our dev team for further investigation, for now I suggest using the V2 Text Element instead.

Thanks.

[fogonthetyne]

Thanks a lot.

It’s genuinely nice to know it’s not just me - usually I ask a query and then my ignorance is just highlighted as I’ve done something stupid!

Thanks for looking into this, I appreciate your time.

Andy

[ruenel]

No Problem.
Our development team will be releasing another update soon.
Please watch out for it.

[alexander]

Hi there,

I just wanted to let you know we figured out the cause of this and it’s fixed in the upcoming release.