Closed (fixed)
Project:
The Better Mega Menu
Version:
7.x-1.0-alpha4
Component:
User interface
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
3 Jul 2013 at 14:54 UTC
Updated:
2 Mar 2016 at 17:13 UTC
Jump to comment: Most recent
Comments
Comment #1
cbrody commentedSeems I had overlooked the jQuery Update dependency (not enforced by the module.) Working now, thanks!
Comment #2
RyanX commentedI had the same issue after reinstall modules many times, still not fixed.
@cbrody, could you pls. explain more about what you've done to fix it.
Comment #3
RyanX commentedSorry to ask again. The issue bothers me a lot. No matter what I configre in the TB mega menu, click SAVE or RESET, the progress bar appeared at the top, but then nothing happened.
I use jQuery version both 1.7 and 1.8, Production compression level and None UI CDN.
What do you mean by "overlooked" the jQuery Update dependency? Do you use version 1.7 or 1.8?
Comment #4
RyanX commentedComment #5
wranvaud commentedI just had this problem too, the module does not require it's "jquery update" dependency upon installation. After installing jquery update (left it at default v1.5) it works fine.
Edit: version 1.7 is recommended according to the project page.
Comment #6
cbrody commented@RyanX I installed jQuery update and the problem went away for me.
Comment #7
khadijamajid commentedChanges not saved when press save button in megamenu toolbox of tb-megamenu. kindly help.
Comment #8
amyar65 commentedI have the same problem here. whatever I do, when I click save, I just get the progress bar forever. I tried the jquery update menitoned above, but I got nothing. I even tried adding the jquery file to the .info file, still nothing.
Comment #9
khadijamajid commentedcan any one help me in it
Comment #10
khadijamajid commentedi guess there is no one to response. i am trying to solve for two weeks. kindly help if any 1 know
Comment #11
wranvaud commentedJust a small comment if I may. These problems are probably related to javascript. Check the console on firebug to see any error or warning on the page. Trying with another browser is a good practice too, in case your browser has a javascript bug. You also need to clear your Drupal CSS & Javascript cache when making changes to your site!!
I'd recommend that you try removing modules that deal with javascript becaus they might cause conflicts (and they do cause js conflicts quite often actually). It's hard to know without having your particular installation available. Another approach would be to install the module on a clean drupal 7 install and then add the modules that you want, verifying that everything works at each step.
Hope it helps those that couldn't make it work.
Comment #12
rschouten commentedI am experiencing the same problem. This issue seems to be in the jQuery dependency. My site is running jQuery 1.4.4 (Drupal Commons) and the config interface for the TB Megamenu requires a feature only available in jQuery 1.5 and up. Specifically, it is expecting a deferred object to be returned in the ajax call within the saveConfig function. Instead, an XmlHttpRequest object is returned, which lacks a "done" method.
As a workaround, in the debugger I can set a breakpoint just before the "deferred" object is meant to be returned, add a "done" noop to this object and get the config to save. Would be nice to get this fixed.
Additionally: TB Megamenu was working with this version of jQuery before. It's almost as if a race condition is exposing the bug. I can't track down any changes to jQuery or the TB_Megamenu module since it was working but did note that our site gained much more content over that time.
Comment #13
cbrody commentedComment #14
scheban commentedIf you click reset before making a change and then clicking save it works for me.
Comment #15
rschouten commentedTested and this workaround does not work for me. As an aside, it does not make sense that clicking reset would upgrade jQuery to a version supporting promises.
Comment #16
alexander.sibert commentedI have the same issue with my last menu item. In the backend it shows me 6 6 columns. In the frontend it shows me 12 12 columns. Then i have a error message in my frontpage http://neofelis.de
It shows me also the views block not in the frontend. Only the last item it shows me the views block.
Comment #17
alexander.sibert commentedSorry, that was my failure. The views block had the permission to view only on administrators. In the same time the error message is away.
Comment #18
alexander.sibert commentedI changed the menu structure of the last item and it saves now the columns but how can it sort?
Comment #19
hai nguyen commentedUnsavable problem happens because I used $.ajax.done and done doesn't work in jQuery 1.4 (default of Drupal). I've just updated to use $.ajax.complete to fix this bug. Please update version 7.x-1.0-alpha4.
Comment #20
jiamh commentedwhen update to 7.x-1.0-alpha4+0-dev, click save and it show save completed.
But actually , nothing is saved, everything is not changed.
Comment #21
kylahuff commentedI'm getting the same issue. I have Jquery update on, have upgraded to 7.x-1.0-alpha4.
When hitting save it comes up with the progress bar - says it has saved but on refresh it hasn't (have cleared cache)
This only appears to be happening if I try and remove the submenus, everything else seems to be working smoothly.
Comment #22
alpersari commentedI have the same issue. I use 7.23 with i18n and 7.x-1.0-beta2 when I save a menu the site keep settings but breaks same menu's other language version.
Comment #23
alpersari commentedI've solved the issue. I've disabled all i18n properties and cloned the menu. The separated two menu is working well with the alpha4.
Comment #24
michaelngodh commentedDownload the latest version. This problem is fixed with other things.
Comment #25
michaelngodh commentedComment #26
caw67 commentedsame error here. the dev- version doesnt work better than the other
Comment #27
caw67 commentedchanges are not saved!
and if i create a new menuentry tb mega menu adds new column! both versions!
Comment #28
clair.stevenson commentedWe discovered that if you are using the Rename Admin Paths module as well, it also causes this issue to happen, because the TB Mega Menu module is looking for the traditional /admin/ path to post the changes.
Our work around was to deactivate Rename Admin Paths during the time we needed to make changes to the menu configuration. Once the changes were made and saved, we could reactivate the Rename Admin Paths module.
I hope this helps others with this issue, This was a hair-puller, for sure.
Comment #29
susanb commentedI found an issue with the Administration language module also. Turning the module off allowed me to make changes to my menu again.