Closed (fixed)
Project:
Provision
Version:
6.x-1.0
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
28 Feb 2011 at 00:31 UTC
Updated:
5 Sep 2012 at 08:21 UTC
I've just tried creating a site using the output from drushmake.me and Aegir says it installs as a platform and site fine, but I get a plain Drupal 6 install with no extra modules and a whole load of "Function ereg() is deprecated file.inc:941"s in the log. Any advice?
Comments
Comment #1
mxmilkiib commentedRetrying with a fresh start.
Building a platform using this .make works fine (is there anything controversial in that .make?). Building a site with that platform gives the problem. There were many more "Function ereg() is deprecated file.inc:941" errors in total.
Applying this hack (eek!) resolves the problem and I can now login to reset the admin password with a freshly created site.
Comment #2
anarcat commentedThis is an issue with Drupal 6 (#883038: PHP warning: Function ereg() is deprecated in includes/file.inc) or with drush that doesn't remove the DEPRECATED notices. (I think it's Drupal.)
One of three solutions:
* fix it in provision (hackish, ugly)
* fix it in drush (not too bad, would respect upstream bootstrap process)
* fix it in D6 (everybody wins)
Comment #3
drupalninja99 commentedWhere in drush would we fix it?
Comment #4
anarcat commentedIt's drush_errors_on() that doesn't respect your existing error reporting: http://api.drush.ws/api/function/drush_errors_on/4.x
That is the case even though examples/example.drush.ini tells you you can set error_reporting, drush_errors_on() actually bypasses that.
I am not sure I understand the way this works well enough, but I suspect we could hijack the DRUSH_ERROR_REPORTING context using:
drush_set_context(DRUSH_ERROR_REPORTING, E_ALL | E_NOTICE | E_STRICT)
... in provision.inc or similar, to get rid of those errors.
Comment #5
anarcat commentedI have opened an issue upstream with drush: #1129332: drush doesn't respect existing error_reporting settings.
Comment #6
j0nathan commentedSubscribing.
Comment #7
steven jones commentedLooks like this has been fixed upstream in Drush now, if you can still reproduce this error, please re-open.