Needs review
Project:
Drupal.org customizations
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
30 Oct 2015 at 02:13 UTC
Updated:
18 Feb 2016 at 22:07 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
japerryUpdate is in hash 3e66f26a123483fa9df5146a359fecee57384c96 in the 7.x-group branch of the drupalorg module.
I have this after the panelizer patch, it'd be great to do it in that order to avoid having to rename updates. But its not a huge deal.
Comment #3
japerrywell that didn't work. DB query was added but somehow status got put back to 0. I guess the other approach is to remove the install code and enable the profile normally.
Comment #4
japerryHere is the patch we can include with core to remove installer, I'll try this on a new dev deployment in the morning.
Comment #5
drummWhat exactly are these errors?
Comment #6
japerryAlso happening on prod (where errors are suppressed):

Comment #7
japerryOkay, tested this one locally and on dev and appears to work better with removing the .install file from the profile.
Hash: e160299a4e8ab2c2e343d8bd37e80bd65cdb0907
Once the update is deployed, we can remove the core hack.
Comment #8
japerryHere is the install script from the 7.x-groups branch.
Comment #9
drummI cleaned up the patch's comments, which still mentioned the DB query approach, updated the hook_update number and committed to the branch.
Still needs testing and deployment instructions.
Comment #11
drummAdding deployment notes to the issue summary.
Comment #12
drummI tried this out on a dev site, but it did not remove the notice. I'm left with
minimalin thesystemtable, withstatus = 0.According to the core issue for this, #1170362: Install profile is disabled for lots of different reasons and core doesn't allow for that:
Comment #14
drummI tried out
UPDATE system SET status=1 WHERE name='standard';on a fresh dev site. That removes the notice message.