Closed (won't fix)
Project:
Navbar
Version:
7.x-1.0-alpha4
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 Mar 2013 at 14:01 UTC
Updated:
21 Mar 2013 at 04:33 UTC
Jump to comment: Most recent file
Comments
Comment #1
hass commentedDrupal 7 checks it's dependencies as I know. I think this is by design as we cannot change the way how the update hooks are working. You need to make sure you install Breakpoints and upgrade afterwards.
I had #1937722: Navbar enable cause Invalid argument supplied for foreach() in element_children() and enabled jquery_update and breakpoints manually before I installed navbar. This way it worked. If all 3 modules are disabled you get the error #1937722: Navbar enable cause Invalid argument supplied for foreach() in element_children(). Not sure if this can be solved, but I never seen such an issue yet.
Comment #2
mixxmac commentedI ran into this issue also. The site breaks when navbar alpha3 is enabled and upgrades to alpha4, which now has a dependency on the breakpoints module, which wasn't installed.
To fix, I had to disable the navbar module by setting its status to 0 in the system table in phpmyadmin (if I remember this right). Then I tried to flush the caches or ran update.php, to allow me to get to the /admin/modules page. Then installed and enabled the latest dev version of the breakpoints module. Then enabled navbar alpha3, and upgraded it to alpha 4. Which then works.
Comment #3
jetwodru commentedMee too, I'm using Panopoly and run the update which then asked me to install the Breakpoints, then I downloaded and put the Breakpoints into the Modules folder and clicked try again, Bang, my whole site is now down with no way of accessing back to the Admin session due to the Nav Bar error as what you encountered when I googled for the solution.
Comment #4
jetwodru commentedfortunately is a test site, I deleted the whole database and reinstalled again. I doubt if it's a Drupal Core Update Issue, when it prompted me that there's a dependency on the breakpoint before I could carry on the database update process, I downloaded and put it into the modules folder, then I clicked Try Again, it could carry on but it still broke my site ! What about later other existing Modules have new dependencies on other Modules during the Update Process, should I still put the newly dependent modules into the modules folder and click Try Again directly ? I wonder
Comment #5
alexander.sibert commentedI have updated with breakpoints module successfully but now the nav bar works not correct. See my attached screenshot. If i click on the menu the navbar open only the content and not the menu. I tried with jQuery 1.5, 1.7, 1.8 with jQuery Update module. What make i wrong?
It was my failure. I refreshed now the Browser cache and it works fine.
Comment #6
mixxmac commentedHi... I had the same thing, at first. I think this may be the reason... Navbar has mismatching closing tag. The last line in navbar.tpl.php should be
</nav>.Comment #7
jessebeach commentedThank you for the reports everyone. Please remember that this is an alpha release. You use it on production sites at your own risk.
Comment #8
hmartens commentedYes thank you :) I wanted to say afterwards that I appreciate the work done on this module...for FREE! I used strong words in the title because I was severely stressed at that specific moment.
I am truely thankful to each and every module developer, they are the unsung heroes!
Comment #9
geoffmallo commentedYou can install and activate the breakpoints module using drush when the site is broken on update and you can't access the modules page.
drush dl breakpoints
drush en breakpoints
(then yes at the prompt)
Comment #9.0
geoffmallo commentedForgot to add the error code