Norma Longhi

Forum Replies Created

Viewing 2 posts - 1 through 2 (of 2 total)
in reply to: Fatal Error – #183995

Norma Longhi
Participant

Hello Nayeem,

Thanks for replying. We were able to resolve the problem by updating to the latest version. We did have auto-updates enabled on WP, but it doesn’t appear to have been up to date.

Best,
Norma

in reply to: Fatal Error #183841

Norma Longhi
Participant

We are also getting a Fatal Error Message on our site. We are running on WordPress (version 6.1.1) on Kinsta, PHP 8, with DIVI Theme and your plug in It is not working.

Here is the message we got this morning:
Our monitoring systems detected that your site Coastal States Organization (Live) is not available and displays the following PHP error:
2023/02/17 12:59:14 [error] 52724#52724: *431661 FastCGI sent in stderr: “PHP message: PHP Fatal error: Unparenthesized a ? b : c ? d : e is not supported. Use either (a ? b : c) ? d : e or a ? b : (c ? d : e) in /www/coastalstatesorganization_868/public/wp-content/plugins/download-manager/widgets/class.Search.php on line 17PHP message: PHP Notice: Function is_embed was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /www/coastalstatesorganization_868/public/wp-includes/functions.php on line 5833PHP message: PHP Notice: Function is_search was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /www/coastalstatesorganization_868/public/wp-includes/functions.php on line 5833″ while reading response header from upstream, client: 35.194.36.163, server: http://www.coastalstates.org, request: “GET /?kinsta-monitor HTTP/1.1”, upstream: “fastcgi://unix:/var/run/php8.0-fpm-coastalstatesorganization.sock:”, host: “www.coastalstates.org:50344”

So, we deactivated the plug in and now we are unable to make it Active again since we keep getting the same error message.

Thanks!

Viewing 2 posts - 1 through 2 (of 2 total)