Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #831343

    Hi
    After updating to 4.1 and then to 4.1.2 the secondary menu is not visible because of this entry in the layout.css:

    html_burger_menu_active .menu-item {
        display: none;
    }
    

    I can override in the style.css by putting in “display:block” but I’m running quite some sites with enfold…

    Maybe you can provide me with a more substancial solution?

    Thanks
    Fabian

    #831345

    On https://parnass-zermatt I fixed it with CSS-entry: .html_burger_menu_active .menu-item { display: block;}

    #831825

    Probably I found the reason why the secondary menu is dissapearing:
    As long as you display “Menu Items for Desktop” as text => no problems with secondary menu. But “Display as icon” => secondary vanishes and only reappears at width: 767px.

    I think this is really a flaw: The secondary menu is very important for business websites -> on top of every page visitors have immediate access to phone number, email-address and the language switcher.

    Thanks.

    #832698

    Hi,

    Thanks for share your solution!

    Best regards,
    John Torvik

    #833246

    Hi John Torvik

    It’s not a solution, it’s a makeshift which I had to apply to all my customers enfold sites – quite a loss of time. Besides that and as I wrote before: The secondary menu is an important Thing for business sites, especially hotel websites.

    I think it’s a bug which is in dire need to be fixed – same like the non-clilckable links which aren’t working any more…

    Thank’s for considering and notifying.

    #835518

    Hi,

    That is how it works on Enfold.
    It is not a bug, but how Kriesi has setuped things.

    Regarding the links – yes that one is a bug which is getting shorted.

    Best regards,
    Basilis

    #836300

    Hi, Basilis

    Thanks for your reply.
    “Bug or not bug?”, that”s a question I really don’t wish to discuss :-). The problem is that after the update to 4.1/4.1.2 all my Enfold-sites weren’t working properly any more, that I had to fix one by one manually and that – according to your reply – from now on I will have to fix them for all future enfold updates until the end of eternity. That’s quite a perspective…

    A little bit more straightforward:
    I own a small web agency. I do sites from scratch, work with lots of different CMS and frameworks. General impression: to complicated and/or to support-intensive and/or not very usable for the clients. All in all: too boring and too expensive. And then some years ago I discovered Enfold and I felt that sudden “touch of fresh air which marks the beginning of a new area”. Yes, I really did – and I still do.

    But:
    If you change a system the modifications added should change its future but not its past: “Backward” engineering is very bad thing. It’s known from the abyss of apps and […] consumer products and also as the core message of pseudo-economical theories: “Why care about backward compatibility? As long as you gain more new clients than you loose old clients your going to write black figures in your earnings”.

    Please don’t do that.

    Because there is something really special with enfold – that 59$ “graphical interface” which is so easy to understand and which allows to create websites in such a fast and such an intuitive way – with WordPress, the world’s most used CMS, compatible with WPML, with WooCommerce. It’s such a BRILLIANT idee.

    No more bricking around. So much potential for developers and their clients. So elegant. Such a fine thing out of its own.
    If its development is based on reliability – part of it is backward compatibility.
    Like it was until now.

    And so at last you have been right: It’s not a bug.

    I don’t mind if you leave my reply hang out to dry; at least there is no question in it. Just notifiy.

    Best regards
    Fabian

    #838585

    Hi,

    Thank you for using Enfold and reporting this.

    I agree with you, that this is an inconsistent behaviour. I pointed this out to Kriesi and added your fix to github for the next release.

    Sorry for the inconvinience you had.

    Best regards,
    Günter

    #838797

    Hi Günter,

    Thank you very much for your comprehension in this matter.

    Kind regads,
    Fabian

Viewing 9 posts - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.