PHP error: Array to string conversion

Hi @herrzhull,

Thanks for choosing Neve!

Unfortunately I am not able to replicate this issue, the Customizer loads as expected on my end. Does this happen for you on a fresh installation of Neve as well?

Thank you!

Hello,

I started a new webserver today and installed a fresh WordPress with only the Neve theme installed to check this.

The customizer loads fine on PHP8.1 on a fresh install, however my logs are again flooded with the array to string conversion error mentioned above. As this is the only error I notice across all platforms so far this is something that may need to be looked into, regardless if the editor loads or not. Dropping to 7.8 removes the error, and also revives the customizer on my other (more fleshed-out) site.

I’m stuck to 8.1 on prod, and I love the theme, so with the error resolved I could check if I can reproduce the infinite load with the error gone.

Thanks again!

Update: I can now confirm the notice has nothing to do with the customizer not loading. I changed my child theme back to default settings (so an exact copy of the child theme with all custom JS and CSS, but without any of the stored changes I made on-site) and the customizer works. So there is a way somewhere to break the customizer from within the customizer. I’ll keep you posted as to how to reproduce this.

Update: in the default Neve child theme (perhaps also in Neve by default?), set the color for the buttons in the customizer (primary / secondary / hover etc). Save it, and the customizer will fail to load on PHP8.1.

Hello @herrzhull ,

Thank you for your detailed explanation!

I followed your instructions in trying to recreate the issue but to no avail (Neve default or child theme). I changed the button colors in all aspects in both the default and the child theme, saved the changes and I could access the Customizer as well as the editor in both situations afterward whilst using WP 5.9.2 and PHP 8.1. ( please note that PHP 8.1.2 is not yet a stable and secure version so errors can happen there)

No errors or warnings appear on the instance either. However, I did notice that particular warning appearing in the debug log. As mentioned by the message it is a warning, not an error, thus nothing will break the functionality or looks of the website.

Thank you for this and we’ll let our developers know about the warning so they can fix it in the future!