Reviewed & tested by the community
Project:
Profiler
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
4 Jun 2012 at 14:27 UTC
Updated:
25 Sep 2015 at 19:06 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
thedavidmeister commentedI can confirm this is a problem. Just tried to disable update using the "dependencies[update] = 0" syntax and it failed.
Comment #2
TheBarnacle commentedSubscribe.
I just tried this with "dependencies[comment] = 0" and got the above error.
Comment #3
jaytennier commentedThe issue appears to be that when the install_verify_requirements() task verifies the profile it checks to make sure that the dependencies listed actually exist. It does this by checking only the values of the dependencies array so it runs into a problem when it gets to a module that's been disabled using Profiler's syntax (i.e. the module name it's checking for is "0").
I've created a patch that overrides and reuses the install_load_profile() task to remove any dependencies that have been disabled from the list of modules. This lets the verify task complete without complaining and because the other install tasks that have been overridden use Profiler's profiler_v2_load_config() function Profiler's install process will still correctly merge multiple profiles.
Comment #4
arnested commentedI can confirm the problem.
I debugged it and came to the same conclusions as jaytennier and his patch works as well.
Attached is the patched rerolled to 7.x-2.x.
Comment #5
arnested commentedComment #6
heddn+1 RTBC on #4