Closed (fixed)
Project:
Navbar
Version:
7.x-1.0-alpha4
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
8 Mar 2013 at 22:31 UTC
Updated:
3 Dec 2013 at 20:50 UTC
Jump to comment: Most recent
Comments
Comment #1
jessebeach commentedI added
module_exists()calls around the two calls to breakpoints functions in thenavbar.installfile. That'll at least prevent fatal errors.Committed to 7.x-1.x (055eb10aca854f870675a8ace0d6e59eba7f8ab9).
The workaround you mention in the issue description seems like a valid enabling path. Can you explain in a little more details what went wrong in your first STR list? Were you using Drush or enabling the modules through the Modules page UI?
Comment #2
hass commentedHow are the breakpoints settings now installed? The code you commited will not really help here and than the breakpoints are not installed what may cause more troubles than today.
Normally core should enable all modules a module depend on automaticall. I have not debugged why this is not working here or causing this issues. I just files this issue with the facts. Core should enable the dependencies first and than the module itself. This looks more like a core bug than.
Comment #3
jessebeach commentedComment #4
jessebeach commentedAgreed, it will just end up masking a problem rather than solving it.
I'm removing the
ifand testing a standard install.Comment #5
jessebeach commentedOk, Navbar no longer has a dependency on jquery_update. I've remove the
ifcondition around the breakpoint creation innavbar_install.and breakpoints is declared as a dependency
dependencies[] = breakpointsThe Navbar module seems to be enabling and disabling without any problem.
I'm going to close this ticket barring any further evidence of error.
Addressed in 5db99b0f53f6db7265d75985fa2e8142bd76a559.
Comment #6
hass commentedSound good.