The Drupal Ladder install profile relies on Node access user reference. nodeaccess_userreference and entityreference are both listed in the install profile's .info file, but I think there's a race condition or something: nodeaccess_userreference_requirements() won't let the install continue because it checks module_exists('entityreference'), and entityreference is (I guess?) not yet enabled at that point in the installation process.
I'm really not sure how to handle this. That function could check the $phase argument, but that will be install during the installation process AND when the module is installed from the module list, after the site is up and running, so that's not right either.
Attaching a screenshot of the error that prevents installation.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | nodeaccess_userreference-install-profile-3.patch | 734 bytes | btopro |
| #2 | nodeaccess_userreference-install-profile.patch | 9.64 KB | btopro |
| #1 | 1774488-1.patch | 510 bytes | BrockBoland |
| Requirements problem | Drupal.png | 106.13 KB | BrockBoland |
Comments
Comment #1
BrockBoland commentedNOT A REAL PATCH
I'm only posting this here for use in the make file of an install profile to make my life easier for a little bit.
Comment #2
btopro commentedreal patch to fix this problem.
Comment #3
btopro commentedSorry, this is the correct patch for this problem
Comment #4
btopro commentedComment #5
BrockBoland commentedThat did it! Install process worked smoothly. On another site, I enabled this module without References or Entity Reference, and it enabled fine but showed the "One or more problems were detected with your Drupal installation. Check the status report for more information." error message, with the correct warning in the status report.
Looks good to me!
Comment #6
btopro commentedBecomes conjecture if the maintainer thinks this is intended behavior. You could validate that it's during the install routine but most modules don't bar activation unless there's going to be a mega-glitch without a project turned on (especially since this can't request one of two optional projects to work). As I don't think this is the case (total failure) I'd recommend the current solution.
Comment #7
BrockBoland commentedTrue, but that's the case of a patch on any issue where the maintainer isn't involved in the conversation, so we'll see what happens.
Comment #8
steveray commentedJumping in late here, but want to confirm that the patch at #3 cures the error message when Node Access User Reference is enabled as a Features dependency.
As for the module maintainer, it seems he's not working on this anymore.
Comment #9
Tschet commentedPatch #3 still works if anyone has this issue.
Comment #10
danielb commentedYeah that's fine