Closed (fixed)
Project:
Open Atrium
Version:
7.x-2.0-alpha3
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
3 May 2013 at 19:55 UTC
Updated:
12 Nov 2013 at 20:50 UTC
Jump to comment: Most recent
Get an install error because the - node_access_rebuild(); is undefind in file oa_core.profile.inc.
A quick fix to get the install to work is to edit the file, like this
// prevent notice after install to rebuild permissions
// node_access_rebuild();
Comments
Comment #1
mpotter commentedMoved this to the oa_core_install hook. Committed to 5a6c366. Hopefully that's a better fix. Sorry I didn't catch this before the Alpha-3 release. It seems that our profile simpletest doesn't catch every problem in the installer.
Comment #2
panchoBetter, but not quite there, I'd say...
As I said in the other task,
Now, moving it into the 'install_finished' task would be fine but unfortunately didn't work, so I'm considering adding a separate hidden task right before 'install_finished'.
By the way, I'm surprised why we're implementing both 'hook_install_tasks' and 'hook_install_tasks_alter'. I think either the one or the other would be cleaner.
Tonight I'm going to have time for taking a closer look on this, therefore assigning to me.
Comment #3
panchoNo, we're definitely not there. In the new place the rebuild does no harm, but doesn't work either. After install it's still saying "The content access permissions need to be rebuilt."
(My notion on implementing both 'hook_install_tasks' and 'hook_install_tasks_alter' was bogus though.)
I did some research on this but have not yet finished deciding what would be the right place for this and other post-install tasks. I'm gonna post a followup patch until Monday morning though, and will fix some more issues with installation, so you can roll a beta4 later on Monday.
Comment #4
Argus commentedbeta4 hurray! ;)
Comment #5
thejtate commentedNice, can't wait!
Comment #6
panchoActually this is no
beta4alpha4 blocker - install works again after the commit in #1.I hope to get this and some of the remaining bugs fixed tonight. Sorry, that it took longer than I had thought.
Comment #7
mpotter commentedI think he means "ALPHA 4" btw ;)
Comment #8
panchoOh, of course, no beta in sight, just an alpha4... ;)
Comment #9
Argus commentedI think this is fixed, never getting this error anymore.