Hi Rikard,

Wow, now it turns out that Adam Levine (Maroon 5) is also working at Kriesi’s support… :P

Thank you for your help, Rikard!! Now a whole world of support tickets open to my eyes with this same problem. I see that the oldest with this kind of problem is from September 2015, so I think this is something that Christian (Kriesi) or his team are not very willing to fix.

I perfectly understand that a wrong html markup closure can give unpredictable results in a web page, but one thing is an unexpected behaviour, and another is this complete madness.

It has no sense at all, that this (simplifying the code)…

[av_heading heading='<strong>VENID A PROBAR GRATIS NUESTROS JUEGOSS<strong>'][/av_heading]

… I mean, ‘a string between single quotes’, that is a perfectly formatted code in terms of “shortcode programming” gives as result the complete break of the page.

If you want, don’t allow users to insert HTML markup in any text field that is not a WordPress rich content editor, or better, use Regular Expressions to inform the user of a bad formatted HTML markup, and not allow him to save.

But letting him save without notices is at best a design flaw, if not a BUG.

My customer has gone mad for a month to finish his website because of this. And you have to understand that even knowing basic HTML, you can make a mistake anytime (in HTML markup) that can lead you to destroy an entire page, or in other words, a work of hours !!

Anyway, Rikard, I request you to do this test, please:

1) Open “Cumpleaños – Prueba” in editor (I’m sending you the link in private content so it’s easier for you to reach the page).
2) I have left you the page only with the YELLOW block in it (i.e. Template: xxxfantasma).
3) Now we have here only one bad HTML markup closure. In: “VENID A PROBAR GRATIS NUESTROS JUEGOS”.
4) Before editing, go down the page, and take a look at the code generated by the editor. You’ll see that there is a lot, so a vertical scroll bar is needed.
5) Now click over the “VENID A PROBAR GRATIS NUESTROS JUEGOS” block, and fix the HTML markup. If you want, completely remove the “strong” tags. And click on Save (“Guardar”).
6) Go down the page again and take a look at the shortcode editor.

Now tell me that this can not be considered as a BUG. You can not condemn to a user (being a technical guy or not) to lose all his work just by this !!

I tell you more.

If you switch to “Standard Editor” (the blue button at the top of the Avia editor, in spanish: “Editor estándar”; SE from now on), you’ll find all this shortcode mess in the WordPress Rich Text Editor.

So a user could think: OK, so I’ll fix it here (using the HTML tab), update the page, and then come back to “Advanced Layout Editor” (ALE from now on) to continue with my work.

But it turns out that the changes made in SE are not reflected in the ALE. So I guess that SE code is only a copy of the underlying ALE programming, but with only the ALE -> SE sense and not the opposite.

So well, a user will then return to the ALE to fix the problem. And I guess he will have only two options:
1) Edit the wrong HTML markup block (NOT POSSIBLE, as you checked before).
2) Delete the wrong HTML markup block, and create it again.

But if you do the 2) option SAME THING HAPPENS !! Shortcode markup is reduced to the minimum and you lose everything.

So, the only solution right now to fix a malformed HTML markup that is already saved is to fix it in the text field enabled via DEBUG code in functions.php.

You still don’t see this as a BUG? Because I do !!

Thank you Rikard.