Forum Replies Created
-
Posts
-
I’ve managed to hide the flags by adding:
.av-language-switch-item {
display: none !important;
}
to the quick CSS.
Not my preferred way of working, but at least my client is happy now.Hi Rikard,
Thank you for the hint. It never occurred to me that ‘display: none’ would also remove the line break behavior.
Super tip! However, this line of CSS also removes all other -intentional- breaks on that page, and is limited to that page only.However, you pointed me in the right direction and I modified the CSS rule to apply only to the menu by using the custom class that I had on that layout element. So this did the trick:
.magma-on-page-menu br { display:none !important; }Thanks again and best regards,
Kristoff
Hi Elliot,
Thank you for your swift reply.
The site hasn’t been launched yet and is still on a development environment, but I’ll send you the link.I’ve managed to find a workaround by activating the development view in the editor and adding HTML comment tags <!– –> in between the button shortcodes.
However, each time I change something in the button menu, the comment tags disappear and I have to add them again. A bit cumbersome and not workable when my client starts editing the content himself. So any other more permanent solution would be most welcome.
Thanks,
Kristoff
