Message TypeError: array_key_exists(): Argument #2 ($array) must be of type array, null given in array_key_exists()

Thanks for this bug report, @Darsana Prasad. The 3.0.x-dev version is being stabilized, so it is very helpful to have testers reporting any issue they find.

did an rc1 release can you confirm if you're still seeing the issue.

After updating to 3.0.0-rc1, the issue remains.

Hi,
I have fixed this issue "Message TypeError: array_key_exists(): Argument #2 ($array) must be of type array, null given in array_key_exists()"
and also attached patch ,
please review and verify .

The patch has some unrelated changes from IGNOREME.txt and introduces some formatting changes that seem unrelated, so it needs work.

Conceptually this probably makes sense.

I guess another solution would be to save the settings to get the data more complete? I wonder which check isn't being found after upgrading to 3.0.x

Yea I’d like to track down where this is getting null vs just putting if not null

Just tested on a fresh install of 10.2.x and rc1 and with the steps in the issue summary not able to replicate.

What about an upgrade of 2.0.2 to 3.0.x?

Maybe, so much changed in 3.0.x that upgrade path from 2.0.x was low priority for me.

I did get an error in rc1 and just released rc2 though as I had a typo. But wasn't this warning at all though.

Because of the refactoring of the configuration not sure there is an upgrade path between 2.0.x and 3.0.x to be had. And security review doesn't have a huge number of configuration to begin with I think uninstalling 2.0.x, upgrading, installing 3.0.x should work. I added that to the homepage.

Rajab Natshah → made their first commit to this issue’s fork.