[Solved] Error in Configuration in Evo 1.0

I’m using the new Evolution 1.0 just relased. And when I go to the Configuration screen in the manager I get this warning listed about 25 times. Does anyone know what this means and how I can fix it???

Warning: array_keys() [function.array-keys]: The first argument should be an array in /data/18/0/115/142/115631/user/117198/htdocs/manager/actions/mutate_settings.dynamic.php on line 1283

When making support requests, please make sure to provide information about your web server and your client machine:

Web Server:

• PHP version and how it’s running (suexec, mod_php, CGI, etc.)
• Apache or IIS version
• Operating System and version

Database:

• MySQL version
• List of any tables over 1MB in size

MODx:

• Version
• Any changes you’ve made
• Any snippets you’re running on the page that is not working properly
• Any plugins you’re running

Browser/Client:

• Browser name and version
• Operating System and version

This will go a long way towards being able to quickly resolve or duplicate and bugs as applicable, and should result in a better overall support experience.

Further, if you’re seeing problems with snippets not seeming to work right, make sure you’re enclosing parameters in back-tics, not single-quotes. On US-English keyboards that’s the key typically found at the top-left of the number row: `

Thanks!

I got the same error. Upgrading Downgrading to RC2 fixed it.

Hello,

I’m having the same problem with the error messages in configuration tab.

But ... "Upgrading to RC2" (that solved problem here:http://modxcms.com/forums/index.php?topic=39369.0) means to downgrade, as the date of MODx 1.0.0. RC2 (July 23rd) and RC3 (July 24th) is earlier than the GA version (July 31st)??

Thanks
Heinz-Guenter

Hmmm, now I’m confused! That’s really weird. I downloaded what I thought was the latest release which installed 1.0.0 RC over 1.0.0 but obviously it wasn’t an upgrade! Anyhow, it clears up the error message. Would be interested to know if anybody else got it. I upgraded modx elsewhere from 0.9.x to 1.0.0 without the error appearing so it must be a server configuration issue.

I’ve upgraded to 1.02 with the same problem. By deleting and replacing the manager directory (and backing up config file) it’s fixed the problem (instead of overwriting it as I’d done with the previous upgrades).

Some FTP programs don’t overwrite existing files. This is almost sure to corrupt a MODx install.

Using FTP to overwrite files is so hit-or-miss depending on FTP program configurations, etc., that I think we should recommend simply renaming your Manager directory to "Manager.old" and making a copy of the config.inc.php file into the new location. That way you have a fallback and a known-good Manager for the new version.

My opinion that config.inc.php really belongs in the assets directory is another issue for another day. Then the instructions would simply be, "Rename your existing Manager directory to Manager.old and upload the new one.

Quote from: rthrash at Nov 13, 2009, 06:39 AM

Using FTP to overwrite files is so hit-or-miss depending on FTP program configurations, etc., that I think we should recommend simply renaming your Manager directory to "Manager.old" and making a copy of the config.inc.php file into the new location. That way you have a fallback and a known-good Manager for the new version.

Good tip. I updated the Wiki.

Thanks Bob for taking care of that.