test
Viewing 15 posts - 16 through 30 (of 32 total)
  • Author
    Posts
  • woluweb Friend
    #494183

    Hi Joan,

    I think you can make the workaround work (my Joomla is 3.1 and yours is 2.5.x, but obviously, this does not change anything).

    I wanted to preserve your website intact, so I only did a minor change, namely adding a “icon-home” icon on the “home” menu in each language.
    See here the result in frontend:
    – language 1

    – language 2

    Now in backend:
    – language 1 : the megamenu does appear after having selected on same computer that given language in frontend in Internet Explorer (with me, it does not adapt if I use Google Chrome for example. Maybe a problem of cache ? Whatever)

    – language 2 : idem dito

    Note that after having switched language in front-end, you have to refresh the page in backend otherwise the megamenu will still not show up…

    Can you reproduce now ?

    Hope it helps 🙂

    Marc


    1. 2013-05-28_12h13_29
    2. 2013-05-28_12h13_46
    3. 2013-05-28_12h09_37
    4. 2013-05-28_12h11_28
    ejbjane Friend
    #494200

    I’ve also got the same problems and no resolutions means I can’t launch my sites. Checked github but it’s not helping me in any case for megamenu problem. Check here :

    http://www.joomlart.com/forums/topic/bug-mega-menu-submenu-with-multilanguage/

    Also I cannot seem to find a solution to the “compile LESS to CSS” unexpected error either.

    Liz

    woluweb Friend
    #494209

    Hi Liz,
    I checked earlier today the site of Joan & it worked.
    Have you tried to switch language in frontend first, refresh backend of corresponding language ?
    If you want, I can have a look at your site as I did for Joan. Just PM me a user account…
    Marc

    ejbjane Friend
    #494216

    Hi Marc,
    I’d really appreciate it. I’m going to have to put the site online for this which I will be doing this evening.
    Thanks, Liz

    jcsanjurjo Friend
    #494328

    <em>@woluweb 374565 wrote:</em><blockquote>Hi Joan,

    I think you can make the workaround work (my Joomla is 3.1 and yours is 2.5.x, but obviously, this does not change anything).

    I wanted to preserve your website intact, so I only did a minor change, namely adding a “icon-home” icon on the “home” menu in each language.
    See here the result in frontend:
    – language 1

    – language 2

    Now in backend:
    – language 1 : the megamenu does appear after having selected on same computer that given language in frontend in Internet Explorer (with me, it does not adapt if I use Google Chrome for example. Maybe a problem of cache ? Whatever)

    – language 2 : idem dito

    Note that after having switched language in front-end, you have to refresh the page in backend otherwise the megamenu will still not show up…

    Can you reproduce now ?

    Hope it helps 🙂

    Marc</blockquote>

    @woluweb
    Hi Marc, the workaround worked for me. Thanks a lot. At least we can continue our job, and provide some hope to our customer.

    Thank you

    joan

    woluweb Friend
    #494809

    Hi everybody.
    I have just seen a new workaround discovered by CyperBG,

    So easy and it did work for me : just – temporarily 🙂 – switch off the “System – Language Filter” plugin.

    Yesterday came new version of T3-framework (1,2,6). I was hoping this problem would be fixed… not unfortunately it is not…

    For the rest, I am still waiting for an answer of Joomlart on my two other initial points, especially the “compile less to css” which does not get through most of the time… (this is a kind reminder for Joomlart by the way 🙂

    woluweb Friend
    #494825

    One more thing :
    Now that we have a workaround to edit the megamenu for a multilanguage website, there is still a tricky behaviour : if some of the menus are not public (but for registered users for example), you cannot edit them either in Template Manager… except if you first log in in frontend. Otherwise they simply don’t appear…

    jcsanjurjo Friend
    #494834

    @woluweb

    Hi Marc, the workaround you suggested (switching languages in the frontend) allows me to edit megamenu settings for both languages in the backend. That’s ok

    But my problem now is that the behaviour of the megamenu in the frontend is quite weird, As you know I’m using 2 lang, and template styles for each:

    • in the frontend, if ES megamenu is showing correctly, then when switch to EN megamenu is showing just the 1st menu level, without expanding the menu tree,
    • I don’t know why, randomly the behaviour changes. If previously I can see EN correctly, and ES incorrect, there’s a point when the behaviour changes and then I can see the whole menu tree for ES and just the 1st level for EN. At this point, the megamenu loses the setup and I’ve to edit and configure again.

    I deeply appreciate if you can have a look to my site

    One of the points i realised is that in the Layout configuration of my styles, the megamenu module position is being represented with the text megamenu (english) in both styles, the spanish one as well the english. No idea how to change that, and no idea if this is being a source of problems. Please see an screenshot of my backend

    Thanks again Marc in advance

    joan


    1. screenshot
    woluweb Friend
    #494859

    I think you should give a try to the other workaround, namely disabling (just for the time of your configuration of megamenu) the “system – languague filter” plugin.
    Try this & let us know. If it doesn’t work, just PM me your credentials (or reactivate them).
    Yours,
    M

    jcsanjurjo Friend
    #494868

    No way Marc @woluweb, I tried deactivating the language filter but no way.

    Is any clue the fact i explained in my last post about the Megamenu Module Position (in edit styles > Layout tab) which is allways in english??

    The credentials are reactivated

    Thanks a lot for your help Marc

    joan

    woluweb Friend
    #495317

    Hi,
    Sorry I could not have a look at your site sooner. Was too busy + sick…
    Anyway, I’m back 🙂
    I had a look at your site.

    I tried the simple technique of temporarily disabling the language plugin and then edit megamenu in each language.
    Good news : it works !
    You will see : I just added an icon-home on your “home” menu, just to illustrate (feel free to get rid of it).

    I did not want to make any further changes, but I can only confirm what you mentioned, namely that it is always “megamenu-english” which does appear on the “layout” tab. As such, I don’t think it is a problem (your menus do work in both language).
    The only difference I see between your configuration & mine is the following :
    you have *assigned* the Spanish Style to some menu items & you have *assigned* the English Style to some menu items.

    For these templates where the choice of the menu is part of the parameters, I think it is not necessary to *assign* (unless your want to have English White / English Pink and Spanish Blue / Spanish Red for example, I guess).

    For example, in my case, for the three active languages, none of the styles is assigned (they are just pointed as default for each language).

    I hope it helps.
    Yours,
    Marc

    jcsanjurjo Friend
    #495335

    Hi Marc @woluweb

    Hope you feel good and healthy, summer is comming so… have to avoid to stay on bed 🙂

    Well, thank you for your time, you’re right I can use some workarounds to setup my megamenu on the backend. I can do that, but my real problem is now in the FRONTEND. The problem is that the Frontend just shows correctly the Megamenu in one of the two languages. If I can expand (deploy) the megamenu in the English page, when I switch to the Spanish page I’ll realise that I can’t expand the Spanish megamenu. No answer when clicking the Spanish megamenu items, I just can see the first menu level.

    Thats my problem. I can edit both megamenu languages in the backend using workarounds, but the FRONTEND just expands correctly the megamenu in one of the languages

    If this behaviour is familiar for you, any clue will be welcome

    Thanks again for your advice Marc. Take care !!!

    joan

    woluweb Friend
    #495337

    Hi @jcsanjurjo,

    My knowledge here is quite empirical, but given the fact I have had to “play” a lot with the megamenu, here is how I managed to “reset” your submenus, meaning they do show as well on frontend as on backend.

    I clicked on each menu item which was “not showing its submenu”.
    Instead of submenu items, the backend was only showing a blank rectangle.

    So I clicked on each menu item, selected “NO” for parameter “submenu”, saved the style.
    And then miracle : everything was reset, ie each menu was showing its submenu (having parameter “submenu” set on YES again).

    Try for yourself next time 🙂

    Yours,
    Marc

    ps : by the way, I would suggest you upgrade to the last version of Mero (1 ahead) and of T3-framework (2 ahead)…

    jcsanjurjo Friend
    #495340

    Great Marc !!!

    Hope this tip solve the situation. Yes, now i can expand both menus on the frontend.

    Well you have some cold beers next time you visit Barcelona

    Thanks again for your help

    joan

    woluweb Friend
    #497699

    So so.
    I set the status of this thread on “solved”, in the sense that we have a workaround.

    I sum up here the problem and the workaround

    • problem #1 : in multilingual site, the template manager shows MegaMenu only for selected language, making it impossible to edit the MegaMenu in all the other languages
    • problem #2 : independently of the multilinguage site, if some of the menus are not public (but are for example meant for “registered” of “guest” users), the Template Manager would only show the menu items that are viewable from frontend, therefore deleting all previous configurations of these menu items when “saving” the template

    The simplest workaround is the following : before making any SAVE in Template Manager
    1. disable the language filter plugin (therefore you will be able to see the megamenus for all languages in Template Manager)
    2. set all menu items (and potential modules appearing in megamenus) on “public”. After saving all your changes in Template Manager, reset the items as they were (“registered”, “guest”, …)

    This is it for the workaround.

    But, together with all the people facing this problem, we would greatly appreciate Joomlart correcting this bug in next release of T3 framework ! 🙂

Viewing 15 posts - 16 through 30 (of 32 total)

This topic contains 32 replies, has 4 voices, and was last updated by  woluweb 11 years, 4 months ago.

We moved to new unified forum. Please post all new support queries in our New Forum