array_merge(): Argument #2 is not an array

weird … 2 questions to get the party started;

* did anything relevant change on your site since the last 7 days or so?
* are you indeed running easy digital downloads?

I’ve been discussing this with my co-developer and we don’t really see how this could be happening (as the 2nd argument is an array that is set in global scope). I have also tested with EDD (as the error happens in that code block) and I cannot reproduce this warning/ notice @danieliser. I’ll be happy to look into this more, but we’ll need more info (and potentially some debug logging) from you to understand what is happening @danieliser.

frank

We did move site to new server and updated multiple plugins I’m sure since then.

Yes using EDD with quite a few extensions as well as Monster Analytics to track purchases and our own plugin Ahoy which has EDD integration on purchase tracking.

I haven’t looked at the line in question honestly but will today.

What global is it that should be defined there. I’m wondering if these are over Cron or AJAX and that var isn’t getting set. It wasn’t happening a lot. Maybe once or twice a day.

This is a low traffic site at that.

What do you need from me in terms of logging? I can clone the server and give you a dev version as well if that helps. Cloudways also supports remote xdebug.

I think first order of business is to find out what type of request is being made when those occur. Will check if the logs had the request url.

If you prefer I move this to email or other more rapid communication like slack let me know. Will need that to send over server info anyways.

I can create a

• This reply was modified 6 years, 6 months ago by Daniel Iser.

relevant code is here; first default conditionals are added to the $ao_ccss_types array, after which the ao_ccss_extend_types function is hooked into the init action which gets the array from global and extend it with applicable non-core conditionals.

the fact that this only happens once or twice per day is interesting, would be great if you could link it with specific requests from your webserver-log.

and if you wan to join the technical discussion, come on over to https://github.com/futtta/ao_critcss_aas/issues/66

and if we get to the “giving me access to help debug”-stage, you can reach me on the WordPress slack as @futtta

frank

Closing as this will be fixed (well, worked around) in AOCCSS 1.9 ??