|
Matthew Olden
|
January 7, 2017 at 5:58 pm
[Sat Jan 07 16:49:23.714307 2017] [proxy_fcgi:error] [pid 1800:tid 140195953358592] [client 172.68.132.214:17240] AH01071: Got error ‘PHP message: PHP Warning: preg_match() expects parameter 2 to be string, array given in /var/www/wordpress/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/pue/pue-client.php on line 658\nPHP message: PHP Warning: preg_match() expects parameter 2 to be string, array given in /var/www/wordpress/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/pue/pue-client.php on line 658\nPHP message: PHP Warning: preg_match() expects parameter 2 to be string, array given in /var/www/wordpress/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/pue/pue-client.php on line 658\nPHP message: PHP Warning: preg_match() expects parameter 2 to be string, array given in /var/www/wordpress/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/pue/pue-client.php on line 658\nPHP message: PHP Warning: preg_match() expects parameter 2 to be string, array given in /var/www/wordpress/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/pue/pue-client.php on line 658\nPHP message: PHP Warning: preg_match() expects parameter 2 to be string, array given in /var/www/wordpress/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/pue/pue-client.php on line 658\nPHP message: PHP Warning: preg_match() expects parameter 2 to be string, array given in /var/www/wordpress/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/pue/pue-client.php on line 658\nPHP message: PHP Warning: preg_match() expects parameter 2 to be string, array given in /var/www/wordpress/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/pue/pue-client.php on line 658\nPHP message: PHP Warning: preg_match() expects parameter 2 to be string, array given in /var/www/wordpress/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/pue/pue-client.php on line 658\nPHP message: PHP Warning: preg_match() expects parameter 2 to be string, array given in /var/www/wordpress/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/pue/pue-client.php on line 658\nPHP message: PHP Warning: preg_match() expects parameter 2 to be string, array given in /var/www/wordpress/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/pue/pue-client.php on line 658\nPHP message: PHP Warning: preg_match() expects parameter 2 to be string, array given in /var/www/wordpress/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/pue/pue-client.php on line 658\nPHP message: PHP Warning: preg_match() expects parameter 2 to be string, array given in /var/www/wordpress/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/pue/pue-client.php on line 658\n’, referer: https://www.sincitymunitions.com/wp-admin/admin-ajax.php?action=wp_ewwwio_media_optimize&nonce=d82b4fb0a6
Why is this error repeating on our server?
|
|
Josh
|
January 9, 2017 at 8:40 am
Something on your server is highjacking the Plugin Update request from Event Espresso. Can you try deactivating the EWWW Image Optimizer plugin, then go to Event Espresso > General Settings, set the license key if you have not already done so, then save that settings page? You’ll be able to run a 1-click update after you save that page.
|
|
Matthew Olden
|
January 9, 2017 at 11:32 am
Yes, the newly reset license key was able to get the updates to occur. We shall monitor to ensure this is resolved by this.
|
|
Josh
|
January 9, 2017 at 11:55 am
You might see more of those PHP warnings if the EWWW Image Optimizer plugin gets reactivated.
|
|
Matthew Olden
|
January 9, 2017 at 12:41 pm
Yup, sure did see more once plugin was reactivated. I have again disabled it to see if the error remains away.
Why is the error though speaking to an EE parameter not being a string? Is that true? If true and corrected, would that mean these plugins could coexist?
|
|
Josh
|
January 9, 2017 at 1:01 pm
That parameter needs to be a string (it’s your Support License key). When it’s an array, that means something else is highjacking the communication between your site and ee.com and changing your license key to something else (in this case, an array).
|
|
Matthew Olden
|
January 9, 2017 at 3:10 pm
From the support team @ EWWW Image Optimizer plugin “the fact that EE is throwing crazy errors during the resulting call to admin-ajax.php indicates EE is doing something weird, but I’ve never used EE, so I have no idea what it could even be. As you did with EWWW, I suspect if you disable EE, things would work just fine as well, but there is some interaction between the two that brings things to a halt.”
Testing validates this; if one is disabled the other works without errors.
I have used EE for a year now and a dev installed EWWW just recently. I guess we will have to do away with EWWW.
|
|
Josh
|
January 10, 2017 at 8:17 am
The thing is, those are not actually crazy errors, and nothing is being brought to a halt. It’s a PHP warning, not a PHP fatal error.
The warning is a very simple error message that’s basically saying: “Hey, this script is expecting is string, in this case the string is your license key, but when this script is loaded on a request referred from EWWW, it’s getting an array.”
|
