search

ExpressionEngine / ExpressionEngine

ExpressionEngine is a flexible, feature-rich, free open-source content management platform that empowers hundreds of thousands of individuals and organizations around the world to easily manage their web site.
https://expressionengine.com
Other
458 stars 125 forks source link

Deprecation error following clean install 7.3.12 #3752

Open jcogs-design opened 1 year ago

jcogs-design commented 1 year ago

Description of the problem Clean install of EE 7.3.12 via download of zip from EE.com website. Installed onto a newly created host running php 8.1 Installed via EE install wizard (running /admin.php on empty setup) Setup completes fine. Logged in, named site, saved changes. Open URL & Path Settings to confirm that wizard has set base_path and base_url correctly. Save these settings with no changes made. Deprecation error triggered

Deprecated
Automatic conversion of false to array is deprecated

ee/legacy/core/Config.php, line 964

    Severity: E_DEPRECATED

On subsequent saves of the same page the error goes away.

How To Reproduce As noted above.

Error Messages As noted above

Environment Details:

matthewjohns0n commented 1 year ago

Thanks for reporting this. Were there any other steps involved? Do you have a custom config file you're using? Looks like this issue is related to Pages. Did you have that installed or have site_pages set in the config file?

TomJaeger commented 1 year ago

I run a quick test setting the config var site_pages... was unable to replicate. Tried PHP 8.1 and 8.2

jcogs-design commented 1 year ago

Just to clarify. This was a virgin cPanel installation for a new account created via WHM - all running running on a Litespeed server. Literally all that was done was to copy the distribution files from download to the new machine, configure a blank database and run the install wizard. No add-ons, no config files, no nothing. The site had no .htaccess set up either, so CP would work and the home page, but nothing else. That's why I reported it - if I had been mucking around with stuff I'd naturally assume it was something I'd done. We needed a site up to hold up a couple of "coming soon" pages, so it was literally a quick / hack job to do just that. After the error cleared (as noted in original post) the site has been operating normally since - though still minimally configured (but does now have a .htaccess file so has two pages!). I've never seen it before (but equally never done a super-clean install of 7 before) - hopefully you can deduce from error report where issue was coming from at least. HTH