Behaviour: File upload triggers warnings but is successful
warning: Parameter 2 to notifications_team_form_alter() expected to be a reference, value given in C:\xampp\htdocs\CODIS\groups\includes\common.inc on line 2883.
warning: Parameter 2 to purl_form_alter() expected to be a reference, value given in C:\xampp\htdocs\CODIS\groups\includes\common.inc on line 2883.
warning: Parameter 2 to spaces_form_alter() expected to be a reference, value given in C:\xampp\htdocs\CODIS\groups\includes\common.inc on line 2883.
warning: Parameter 2 to atrium_form_alter() expected to be a reference, value given in C:\xampp\htdocs\CODIS\groups\includes\common.inc on line 2883.
warning: Parameter 2 to atrium_book_form_alter() expected to be a reference, value given in C:\xampp\htdocs\CODIS\groups\includes\common.inc on line 2883.
warning: Parameter 2 to casetracker_form_alter() expected to be a reference, value given in C:\xampp\htdocs\CODIS\groups\includes\common.inc on line 2883.
warning: Parameter 2 to date_form_alter() expected to be a reference, value given in C:\xampp\htdocs\CODIS\groups\includes\common.inc on line 2883.
warning: Parameter 2 to date_timezone_form_alter() expected to be a reference, value given in C:\xampp\htdocs\CODIS\groups\includes\common.inc on line 2883.
warning: Parameter 2 to filedepot_form_alter() expected to be a reference, value given in C:\xampp\htdocs\CODIS\groups\includes\common.inc on line 2883.
warning: Parameter 2 to og_form_alter() expected to be a reference, value given in C:\xampp\htdocs\CODIS\groups\includes\common.inc on line 2883.
warning: Parameter 2 to wysiwyg_form_alter() expected to be a reference, value given in C:\xampp\htdocs\CODIS\groups\includes\common.inc on line 2883.
warning: Parameter 2 to og_access_form_alter() expected to be a reference, value given in C:\xampp\htdocs\CODIS\groups\includes\common.inc on line 2883.
warning: Parameter 2 to notifications_content_form_alter() expected to be a reference, value given in C:\xampp\htdocs\CODIS\groups\includes\common.inc on line 2883.
This seems to be a (in)compatibility issues with PHP5.3. The benale site has PHP5.2.1 installed and there it works fine. The icarda site has PHP5.3.1. ( it seems that something has changes in the way drupal_alter calls a module ?)
http://drupal.org/node/705512#comment-4050074 nr38 Posted by TwoD on February 5, 2011 at 12:20am@ionmedia, the real problem is in the code calling drupal_alter(), not in the date_form_alter() function signature.The caller should use '__drupal_alter_by_ref' like in the patch from #32 (it has already been comitted to CCK so it will no longer be the cause of this problem, but other modules can still do it the wrong way).
I can see 4 options to fix this
(1) Update
Upadte all the modules that have available updates in the hope that they have addressed the PHP issue. Also, try a newer version of OA. This should be done anyway, but is unlikely to fix the problem completely as not all modules will be updated.
Ok, php allows you to control what warnings are reported. The "eregi() error" is not in fact an error, but just a deprecation notice and can be safely ignored. To disable this warning you'll need to tell php to tone down it's reporting with a line like error_reporting = E_ALL & ~E_DEPRECATED & ~E_NOTICE in your php.ini file. That is, if you want to keep using php 5.3
Ahmad edited PHP.ini to suppress error reporting.
Behaviour: File upload triggers warnings but is successful
This seems to be a (in)compatibility issues with PHP5.3. The benale site has PHP5.2.1 installed and there it works fine. The icarda site has PHP5.3.1. ( it seems that something has changes in the way drupal_alter calls a module ?)
http://drupal.org/node/705512#comment-4050074 nr38 Posted by TwoD on February 5, 2011 at 12:20am@ionmedia, the real problem is in the code calling
drupal_alter(), not in thedate_form_alter()function signature.The caller should use'__drupal_alter_by_ref'like in the patch from #32 (it has already been comitted to CCK so it will no longer be the cause of this problem, but other modules can still do it the wrong way).I can see 4 options to fix this
(1) Update
Upadte all the modules that have available updates in the hope that they have addressed the PHP issue. Also, try a newer version of OA. This should be done anyway, but is unlikely to fix the problem completely as not all modules will be updated.
(2) suppress error reporting
Miccolis:https://community.openatrium.com/issues/node/2121
Ok, php allows you to control what warnings are reported. The "eregi() error" is not in fact an error, but just a deprecation notice and can be safely ignored. To disable this warning you'll need to tell php to tone down it's reporting with a line like
error_reporting = E_ALL & ~E_DEPRECATED & ~E_NOTICEin your php.ini file. That is, if you want to keep using php 5.3(3) Downgrade PHP
(4) edit common.inc (ugly hack)
http://drupal.org/node/710892
Option (1) update is not going to solve it:
The only modules that have updates available
The otyher 8 are up to date