This error occurred 2633 times during the upgrade, having passed all the preflight etc checks
Are these just warnings, if so what should be configured differently to avoid them?
Should the preflight have generated a warning and recommend the corrective action in future?
Am I safe to continue or should I do a clean install? So far only limited dummy test data so nothing to loose with a fresh install, but part of the testing process was to test upgrades and clearly I have much to learn
The install had not been upgraded previously, and no alterations of system parameters had been done
I’m a bit disappointed no one has replied with even a basic message, I’d really just like to know if this “issue” has been seen before, or should be added to the bug list, to save someone else the frustration and if it will need a fresh re-install or is safe to continue?
Clearly if there is a fix (change permissions etc) then maybe these could be added to the preflight checks, and the issue captured in a more user friendly way?
If I should have posted this on GIt, please just let me know and I will …
thanks for the reply, and links, but as the links contain confusing and conflicting information, I’ll add my as yet “untested” (as I’m not doing another upgrade till next release!) findings below for others who have this issue! The conflicting information relates to the second link:
Sadly this would still include the “strict” warnings, so the setting that is needed is
error_reporting=E_ALL & ~E_DEPRECATED
This install is on a shared host, so I had to get their support team to create a fresh “php.ini” file, and also make any changes they needed to (if any) to ensure it is properly included. Which they did within 10 minutes
So all happy, except
should the preflight checks not warn the user that “strict” warning are enabled and with that setting lots errors/warnings will be generated (potentially 2600+) and ideally provide a linked kb article on how to make the change?
can the upgrade not be changed or updated to comply with strict reporting without generating these warnings?
Sorry, given some incorrect information, the original line was correct, and not as I suggested. So this is correct :
error_reporting = E_ALL & ~E_NOTICE & ~E_STRICT
Sorry, followed blindly, but realised my errror! :S
final 2 points remain though:
should the preflight checks not warn the user that “strict” warning are enabled and with that setting lots errors/warnings will be generated (potentially 2600+) and ideally provide a linked kb article on how to make the change?
can the upgrade not be changed or updated to comply with strict reporting without generating these warnings?
Having the new 7.7.1 release today, I have been able to test the change (see below Php.ini entry) and it does indeed rectify the errors relating to strict, although a few others were logged…
