Adrian

Thanks @widecast for the temporary workaround.
I was on PHP 7.3.5.
After backing down to 7.1 or 7.2 the problem goes away (or is hidden).

I still think that fixing MailPoet 2 is the wrong approach.
There should be a way to display the MailPoet 2 newsletter archive without requiring MailPoet 2 to be installed.
Maybe some way to export the SQL table containing the MailPoet 2 newsletters and import as normal posts which don’t require any special wysija CSS classes.

I installed a debugging statement to display the variable which was causing the eval error.
The line of code in render_engine.php is

       $eval_string = sprintf ("if (%s){\$result=true;} else {\$result=false;}", $condition);
        @eval ($eval_string);

And the value of $eval_string which gives the error is
if ( #image){$result=true;} else {$result=false;}

PHP is not my speciality, but I think #image is an invalid variable name.
I’m not sure how to fix the problem, though.

• This reply was modified 5 years, 10 months ago by Adrian.
• This reply was modified 5 years, 10 months ago by Adrian. Reason: correct typo

I have the same error in MailPoet 2 after upgrading to WordPress 5.2.
It’s happening on one site I maintain but not on another site.
I suspected incompatibility with another plugin, but deactivating all other plugins doesn’t cure the problem.

I am working on upgrading to MailPoet 3 but I will need to leave MailPoet 2 activated so that the MailPoet 2 newsletter archive is accessible. Or is there another way to view the MailPoet 2 archive?

This is the message I see

The site is experiencing technical difficulties. Please check your site admin email inbox for instructions.

PHP ERROR:array(4) {
  ["type"]=>
  int(4)
  ["message"]=>
  string(36) "syntax error, unexpected end of file"
  ["file"]=>
  string(115) "/home/xxxxxx/public_html/web/wp-content/plugins/wysija-newsletters/helpers/render_engine.php(600) : eval()'d code"
  ["line"]=>
  int(1)
}

Many thanks, [cookie_audit] is now working again on my site.

[cookie_audit] is not working for me.
It produces no output
It used to be OK on my site.

I would like the GLOBAL POST LISTS SETTINGS to apply to the portfolio lists as well.
Is that possible?
Or should I try to implement that by a child theme?

Narrowed it down to a checkbox in Kaspersky Internet Security.

Under KIS Preferences/Protection/Web Anti-Virus,
if I deselect “Check Secure Connections (HTTPS)” then the jetpack facebook widget works OK.

Turns out the culprit is Kaspersky Internet Security which I installed about the same time as the upgrade to High Sierra 10.13.5.
It has optional browser extensions for Chrome, Safari and Firefox.
However I did not have those extensions activated.

It was only when I turned off Kaspersky Protection completely that those browsers started working as expected.

So the problem’s in Kaspersky – I’ll either have to get Kaspersky to fix it or use another security product.

Thanks for your help.

Thanks,
then maybe it’s a problem with a browser extension that is affecting my instances of Chrome, Firefox and Safari on 10.13.5 (but not 10.13.4) and not affecting Canary, Yandex or Opera.
I’ll do some more digging and update this thread.

I’ve made some more tests.
I tried disabling all plugins except Jetpack to see if there was a conflict. No difference.

Situation is
If I access a site running the jetpack facebook widget, the widget displays no output when I’m using MacOS High Sierra 10.13.5 and either Chrome, Safari or Firefox browser.
It works fine with the Opera, Yandex or Chrome Canary browsers.
It also works fine with Chrome, Safari or Firefox if I boot from a backup drive which is still on High Sierra 10.13.4

I’ve tested multiple browsers on Windows 10 and IOS 11.4 without problems.

Are you able to access my test site https://test.comptonshawford-pc.gov.uk/ from a machine running MacOS 10.13.5 and see if the widget produces any output for you?

Liz
thanks for your thoughts.
Is it possible to disable and reinstall the Jetpack facebook widget without reinstalling the whole of Jetpack?

My two sites run different sets or plugins (some the same and some different).

The jetpack facebook widget has stopped working on two different sites hosted on two different servers running different hosting software and different levels of php, different levels of Jetpack.
The common factor is that the widget now fails on MacOS 10.13.5 for all tested browsers except Opera, but it works fine on other platforms (IOS, Windows 10).
Have you tried accessing those two URLs from a MacOS High Sierra system? What happened?

Stef
thanks for giving me the chance to post my feedback on GitHub.
But I’m not familiar with that process, so I’d be very happy for you to create the issue.

My fault:
I was trying to modify the placeholder text which says “Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use. To find out more, including how to control cookies, see here:”

It turns out you can’t treat it like a normal editable block of text, delete some words and add others etc.
But you can type completely new text into the input textarea.
I guess this is how textareas are designed to work.
The normal usage of placeholder text is something like “enter your name here” when you would expect to replace the placeholder text completely.

The html snippet in question is

<textarea class="widefat" name="widget-eu_cookie_law_widget[3][customtext]" placeholder="Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use. 
To find out more, including how to control cookies, see here:"></textarea>

To make the placeholder text editable, could you use this instead

<textarea class="widefat" name="widget-eu_cookie_law_widget[3][customtext]" placeholder="Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use. 
To find out more, including how to control cookies, see here:">Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use. 
To find out more, including how to control cookies, see here:</textarea>

That would allow the user to fine tune your sample text and also to retrieve the placeholder text by clearing the input area.

• This reply was modified 6 years, 9 months ago by Adrian. Reason: correct typos, add final para

I didn’t post the URL before because I didn’t think it would help.
You can only see the problem when you have access to the customise widgets interface.

As I said, I’ve tried this on two different sites and both have the problem.
Here’s my test site: https://test.comptonshawford-pc.gov.uk/

@mymousepad my “WP_MEMORY_LIMIT” was already set to “256M” when I had the problem, it was setting max execution time for each scan stage to 20 that fixed it for me.

@wfalaa I would probably have found my solution more quickly if the “max execution time per scan stage” setting were accessible under Scan/Options as well as the general wordfence options tab.
It seems inconsistent to have the scan performance settings split across two different screens.