Closed (fixed)
Project:
Commerce Kickstart
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
30 Aug 2012 at 09:12 UTC
Updated:
15 Apr 2013 at 19:21 UTC
Right now the only memory check that we have is Drupal's 32M. We need to patch core so that the install profile can change that, and have it check for our 128M minimum. We also need to check for xdebug, so that we can avoid the crash due to max_nesting_level.
Comments
Comment #1
theo_ commentedCan't we juste write a hook_requirements() instead of patching core ?
Comment #2
bojanz commentedIt looks ugly when both requirements for memory fail. Imagine trying to install with 16M of memory. You get "Minimum: 32M" and "Minimum: 128M" in the same table :)
Comment #3
theo_ commentedOr define the DRUPAL_MINIMUM_PHP_MEMORY_LIMIT at 128M ? ugly too ?
Comment #4
vasikenew issue related opened for Drupal core #1772316: Allow install profiles to change the system requirements
Comment #5
vasikethere's a patch for the new Drupal core issue #1772316-1: Allow install profiles to change the system requirementswith this we can change the DRUPAL_MINIMUM_PHP_MEMORY_LIMIT value.
bad one
Comment #6
vasikethere's a new patch for the Drupal core that allows install profiles to change the system requirements:
#1772316-2: Allow install profiles to change the system requirements
so with this patch, all it's needed here it's a new line in the profile info file:
Comment #7
vasikeand there is the gerrit commit using the Drupal core patch:
https://code.drupalcommerce.org/#/c/411/
Comment #8
vasikepatch for Drupal core rebuilt #1772316-4: Allow install profiles to change the system requirements.
commit rebased : https://code.drupalcommerce.org/#/c/411/
Comment #9
spanac commentedFor me 128M didn't work (blocked at last step when inserting sample data), but with 256M installation worked fine.
Comment #10
bojanz commentedMerged. Well done!
Comment #11
bojanz commented@spanac
With a lower memory limit, when did it fail? Pre-configuration (before you select demo store / no demo store, create an account, etc), during installation of additional modules, or during importing of content?
Comment #13
japerryIn theory, if you try to use hook_requirements during in the install profile itself (aka comment #1), it won't work.
see #1971072: Install profiles cannot list their own requirements in drupal_check_profile for more