Can anyone tell me if the 7.2 release is compatible with php 5.5 or 5.6? I’ve been running earlier installs at 5.3 as I believe there were issues with anything beyond 5.3 with previous versions.
Thanks
Can anyone tell me if the 7.2 release is compatible with php 5.5 or 5.6? I’ve been running earlier installs at 5.3 as I believe there were issues with anything beyond 5.3 with previous versions.
Thanks
SuiteCRM 7.2.x will work with PHP 5.5 and PHP 5.6.
You will need to modify your php.ini to not show Strict Standards warnings/errors.
Thanks,
Will.
hi, try install suitecrm 7.2 on my mamp pro.
with last version of php 5.6 i get this error:
[i][color=#00000]"Strict Standards: Declaration of SugarEmailAddress::save() should be compatible with SugarBean::save($check_notify = false) in ROOTSUITECERM/include/SugarEmailAddress/SugarEmailAddress.php on line 1113
Strict Standards: Declaration of Person::create_export_query() should be compatible with SugarBean::create_export_query($order_by, $where) in ROOTSUITECERM/crm-root/include/SugarObjects/templates/person/Person.php on line 44
Strict Standards: Declaration of User::retrieve() should be compatible with Person::retrieve($id = -1, $encode = true, $deleted = true) in ROOTSUITECERM/modules/Users/User.php on line 44
Strict Standards: Declaration of User::create_export_query() should be compatible with Person::create_export_query(&$order_by, &$where, $relate_link_join = ‘’) in ROOTSUITECERM/modules/Users/User.php on line 44
Strict Standards: Declaration of User::create_new_list_query() should be compatible with SugarBean::create_new_list_query($order_by, $where, $filter = Array, $params = Array, $show_deleted = 0, $join_type = ‘’, $return_array = false, $parentbean = NULL, $singleSelect = false, $ifListForExport = false) in ROOTSUITECERM/modules/Users/User.php on line 44
Strict Standards: Declaration of User::list_view_parse_additional_sections() should be compatible with SugarBean::list_view_parse_additional_sections(&$list_form) in ROOTSUITECERM/modules/Users/User.php on line 44
Strict Standards: Declaration of Currency::retrieve() should be compatible with SugarBean::retrieve($id = -1, $encode = true, $deleted = true) in ROOTSUITECERM/modules/Currencies/Currency.php on line 239
Strict Standards: Non-static method UploadStream::register() should not be called statically in ROOTSUITECERM/include/entryPoint.php on line 184
Deprecated: Non-static method SugarConfig::getInstance() should not be called statically, assuming $this from incompatible context in ROOTSUITECERM/include/SugarLogger/LoggerManager.php on line 76
Deprecated: Non-static method SugarConfig::getInstance() should not be called statically, assuming $this from incompatible context in ROOTSUITECERM/include/SugarLogger/SugarLogger.php on line 121
Strict Standards: Non-static method LogicHook::initialize() should not be called statically in ROOTSUITECERM/include/utils.php on line 3017"[/color][/i]
with 5.3 version the advices desapear.
so i have to edit php.ini files to not show Strict Standards warnings/errors.? can i ask why isn’t important to show this kind of warnings?
Getting these errors as well. Found this thread after double checking that this was a common issue.
Mainly responding to @nonchiedercilaparola and I guess anyone else coming across these errors.
So E_STRICT was added to E_ALL in php 5.4 … which is the reason that these errors are showing up.
http://php.net/manual/en/function.error-reporting.php
E_STRICT errors are indicative of bad / non-standard code that needs to be changed to reflect more modern PHP programming standards.
http://php.net/manual/en/errorfunc.constants.php
So in other words, disabling the E_STRICT errors in your INI is a BAD practice, but because these issues haven’t been fixed yet in SuiteCRM, disabling them is the only way to get SuiteCRM to work properly.
Please remember to turn them back on when you go back to working on other projects!