Closed (fixed)
Project:
Provision boost support
Version:
7.x-1.1
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
22 Oct 2013 at 20:23 UTC
Updated:
2 Dec 2014 at 21:04 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
ergonlogicThis should just be a matter of renaming the Provision class(es) (i.e., Provision_Config_drushrc_site).
Comment #2
pauleb commentedI created a patch renaming the class like ergonlogic proposed. It works with provision 6.x-2.0-rc5.
Since it worked with provision 6.x-1.x before I assume the patch breaks it. Is there a possibility to check for the used version of provision and to use the propper class?
Or is there going to be a versioning scheme that goes in hand with the aegir / provision versioning?
At least it would be nice to have a few words on the project description page about compatibility with aegir 2.0.
Because the way it is now it's quite scary for simple users like me to upgrade.
I changed the version this issue affects from 6.1 to 7.1.1 since I wrote the patch against this branch and it is the only branch shown for downloading on the project page.
Nonetheless thanks for the great work and the hint with the class name!
Comment #3
lavamind commentedTested the proposed patch on my site and it worked after clearing the drush cache. Please commit.
Comment #4
garethhallnz commentedPatch in #2 works on aegir 2.1
Comment #5
bgm commentedYikes, old issue! Thanks for reviving. Applied the patch on the 7.x-1.x branch.