Page 1 of 1

Slideshow Layout set to Use as Intro

Posted: 08 Jun 2022, 04:20
by AYAPOV
It suddenly stop working at all. Different bowsers, different macs and smartphones - no intro.
Please help to restore functionality. Any suggestions? (https://www.open.kz)

Re: Slideshow Layout set to Use as Intro

Posted: 08 Jun 2022, 05:59
by mjau-mjau
Check now.

You need to be careful with orphan tags in your content. I found an orphan </div> tag, which forces the browser to re-arrange the document structure, which could causes problems like this.
Image

Re: Slideshow Layout set to Use as Intro

Posted: 08 Jun 2022, 08:05
by metallissimus
mjau-mjau wrote: You need to be careful with orphan tags in your content.
I learned that the hard way recently – my contact form didn't work anymore. Maybe there's a way to have that specific problem checked for when saving changes?

Re: Slideshow Layout set to Use as Intro

Posted: 08 Jun 2022, 08:47
by mjau-mjau
metallissimus wrote:I learned that the hard way recently – my contact form didn't work anymore. Maybe there's a way to have that specific problem checked for when saving changes?
Of course that would have been the best solution ... It's not something I can personally code, as opening/closing tags may all look different, some contain attributes and classes, and some tags like <br><hr><img> are non-strict and can be used like <br/><hr/><img/> with a single tag. Besides, this is not really a wysiwig HTML-editor but a SRC editor that supports markdown. It might be possible with one of the HTML wysiwig editors out there, but then you are locked to html mode.

One of the beautiful things with markdown, not only is it easier to read and write, but you will never have any html mistakes. Unfortunately, markdown is limited to "rich text formatting" and HTML is required for more advanced layouts and X3 content plugins.

It's something I will be thinking about for panel 2.0 (at some point).

Re: Slideshow Layout set to Use as Intro

Posted: 08 Jun 2022, 09:32
by AYAPOV
mjau-mjau wrote: Check now.

You need to be careful with orphan tags in your content. I found an orphan </div> tag, which forces the browser to re-arrange the document structure, which could causes problems like this.
Image
Great! Thanks - It is up and running now in proper way