Thread Starter
hj
(@hj)
…and just noticed that there is now a WARNING: code line at the top of my live site….
Warning: array_merge(): Argument #2 is not an array in /home/wywebsite/public_html/wp-includes/load.php on line 63
This line remains even if I deactivate the plugin or disable the Firewall. So it’s written some code into other system files, no doubt.
Hmmm, not so good!
Hi
NinjaFirewall calls session_start() to start a PHP session. But if you have a plugin or theme that throws a PHP notice or warning error before, PHP will send tons of warning because the session couldn’t be started.
Try to locate the warning/notice in your install and solve the issue. Afterwards, NinjaFirewall could be enabled.
Thread Starter
hj
(@hj)
Hi,
I’ve not seen any PHP notice or warning errors on the site before installing your plugin – everything was working fine.
And even in admin now, there are no “notices or warnings” that I can see. What should I be looking for?
Pre-Ninja, everything fine. Post-Ninja, errors everywhere!
Maybe it was not a notice or warning (or wasn’t visible) or it could be a space or just a line feed in a theme for instance.
1. Uninstall completely NinjaFirewall (click on the “Delete” link) to make sure it’s gone. It does not modify your WP core files. It may take 5mn for PHP to reload its config after the deletion.
2. Try to debug and find out what is being sent by your blog and forces HTTP headers to be sent earlier than expected.
Thread Starter
hj
(@hj)
Hi, thanks for response.
1. Uninstall completely NinjaFirewall (click on the “Delete” link) to make sure it’s gone. It does not modify your WP core files. It may take 5mn for PHP to reload its config after the deletion.
I will do this, yes. Although it does seem to have modified wp-config file with some lines straight after the <php opener. Maybe wp-config is not a ‘core’ file..??
2. Try to debug and find out what is being sent by your blog and forces HTTP headers to be sent earlier than expected.
I wouldn’t know where to start, sorry! I’m not a coder or dev, I’m just a user!
Thread Starter
hj
(@hj)
When I look at the main site in some other browsers under a different system (OSX Yosemite, Safari and Linux Mint, Firefox) the code line at the top of the live site does not show.
So because at the moment it’s only affecting login/logout, I can probably live with it.
In case you’re interested, the sequence of events is thus:
1. From Admin, click logout
2. Screen shows long list of code errors
3. Refresh the window and screen shows a dialogue saying “You are trying to logout of admin – do you want to continue? [logout link]”
4. Clicking that link returns me to the WordPress login screen
So it’s not disastrous – but it’s not as it should be!
regards
wp-config.php is not a core file (i.e., it is not part of the install package), but it is your WP configuration file which includes DB credentials etc. Plugins can write to it too.
When I look at the main site in some other browsers under a different system (OSX Yosemite, Safari and Linux Mint, Firefox) the code line at the top of the live site does not show.
Maybe a caching issue?
So it’s not disastrous – but it’s not as it should be!
Did you uninstall NinjaFirewall?
If you didn’t yet, try to post here all error lines referring to NinjaFirewall: they should contain the “/ninjafirewall” or “/nfwlog” sub-strings.
Thread Starter
hj
(@hj)
Yes I have deleted NinjaFirewall….and things have got worse!
1. The live site displays in all browsers an error code at top of page…
Warning: array_merge(): Argument #2 is not an array in /home/mywebsite/public_html/wp-includes/load.php on line 63
2. After deleting NF in the wp admin, I clicked to navigate to another admin page…but just got the long list of errors plus a wp login box beneath. However, was unable to login …
Error: Cookies are blocked due to unexpected output
3. If I try and access /wp-login.php directly I get these error codes plus the login box beneath:
Warning: array_merge(): Argument #2 is not an array in /home/mywebsite/public_html/wp-includes/load.php on line 63
Warning: Cannot modify header information - headers already sent by (output started at /home/sedpet85/public_html/wp-includes/load.php:63) in /home/mywebsite/public_html/wp-login.php on line 421
Warning: Cannot modify header information - headers already sent by (output started at /home/sedpet85/public_html/wp-includes/load.php:63) in /home/mywebsite/public_html/wp-login.php on line 434
The long and the short of it is…I can’t login to my admin anymore!
Check if you have a “php.ini” or “.user.ini” file in your root folder. If you find one, rename it, e.g. “php.ini.old” or “.user.ini.old”
If you have a caching plugin, you’ll need to flush its cache too.
Thread Starter
hj
(@hj)
Hi,
Thanks, that did the trick. But don’t I need a php.ini file?….
I also have files:
php.ini.ninja1522855119
php.ini.ninja1522855468
.htaccess.ninja1522855468
Should I delete those, too?
And after all that, where are we? Back to square one before I installed NF?
I’m with Siteground and had a long chat with their support people because I was unable to install the Full WAF…despite their server apparently meeting all the requirements. They were puzzled, too. So in the end I just installed the WordPress WAF…with resulting problems!
You can delete the *.ninja* files, they were backed up during the installation process.
We have customers using Siteground and I can’t remember anyone having the same kind of error.
Searching for “Warning: array_merge(): Argument #2 is not an array in wp-includes/load.php on line 63” on Google returns 11,400 results.
Thread Starter
hj
(@hj)
Searching for “Warning: array_merge(): Argument #2 is not an array in wp-includes/load.php on line 63” on Google returns 11,400 results.
Well I’m not ploughing through all those! 😉
We have customers using Siteground and I can’t remember anyone having the same kind of error.
Well, I can only say the Full NF wouldn’t install and I had to go for the WordPress NF. I can email you the transcript of the Siteground conversation if you want?
regards
No need to forward the transcript because this issue is related to your hosting account and I can’t provide support for that. Here’s another similar example: https://mrwweb.com/solving-array_merge-argument-2-on-load-php-line-63-on-siteground/
NinjaFirewall should work in “WordPress WAF” mode, as long as you select this option immediately during the installation process, because if you select “Full WAF” first, the installer will create a php.ini which will cause PHP to throw all those errors.
Thread Starter
hj
(@hj)
OK, no worries, and thanks for the link.
NinjaFirewall should work in “WordPress WAF” mode, as long as you select this option immediately during the installation process, because if you select “Full WAF” first, the installer will create a php.ini which will cause PHP to throw all those errors.
Ahh!….which is exactly what I did! Maybe starting from square one and only selecting the WordPress WAF will do the trick. Something to try.
I wonder why the installer creating a php.ini causes PHP to throw a wobbler?
