List of Deprecated warnings in EE 6.2.7
Development and Programming
Here’s a list of various warnings I get as super admin. Would be great if these were fixed for next release.
Deprecated str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated ee/ExpressionEngine/Addons/rte/ft.rte.php, line 408
Severity: E_DEPRECATED Warning foreach() argument must be of type array|object, null given ee/ExpressionEngine/Library/Parser/Conditional/BooleanExpression.php, line 130
Severity: E_WARNING Warning foreach() argument must be of type array|object, null given ee/ExpressionEngine/Library/Parser/Conditional/BooleanExpression.php, line 130
Severity: E_WARNING Warning Cannot modify header information - headers already sent by (output started at ee/legacy/core/Exceptions.php:120) ee/ExpressionEngine/Boot/boot.common.php, line 475
Severity: E_WARNING
Deprecated preg_split(): Passing null to parameter #3 ($limit) of type int is deprecated ee/ExpressionEngine/Service/Formatter/Formats/Text.php, line 51
Severity: E_DEPRECATED Warning Cannot modify header information - headers already sent by (output started at ee/legacy/core/Exceptions.php:120) ee/legacy/libraries/Functions.php, line 458
Severity: E_WARNING
The warnings are mostly informational, as new methods are being replaced in PHP or have can be fixed with some minor code changes. The problem is that many things, including add-ons and other functions which developers use, still rely on the legacy files. It would require a re-write which they are slowly doing. If they just remove legacy code, it would cause havoc, because some things still have no replacement. If you check the documentation, you will see that many things can only be used with the legacy methods and are used in many EE websites. There is no way to do some specific things unless you use those legacy methods.
Thx…all clear for me