sdboyer has some hackish fixes in versioncontrol api that help it get autoload to work right when testing and early in module life. Seems like this would be an issue while enabling modules and possibly during cache builds in some cases. Similar fixes should probably be applied to dbtng to make it and modules that depend on it testable.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 0001-957262-by-neclimdul-Make-sure-autoload-registry-is-s.patch | 1.71 KB | marvil07 |
| #1 | 957262-dbtng-populate-autoload-registry.patch | 1.3 KB | neclimdul |
| #1 | dbtng.install.txt | 149 bytes | neclimdul |
Comments
Comment #1
neclimdulpatch and .install file.
Comment #2
marvil07 commentedMoving to one patch, but maybe is better to ask autoload maintainers about this before commiting it(aka avoid re-hack in two module and fix upstream if possible).
Comment #3
marvil07 commentedI opened an issue at autoload queue asking about this #959600: simpletest problem?
Comment #4
neclimdulfixing tags
Comment #5
mikey_p commentedpulling into sprint 4
Comment #6
mikey_p commentedComment #7
mikey_p commentedWe don't support autoload 1.x and I haven't found any need for the hook_menu hack with the tests I've backported from Drupal 7.