Exyst

We have the same problem here after upgrading to v3.45.1 or 3.46 (fatal error “This site is experiencing technical difficulties”). We needed to revert to v3.45.0 to restore our website and dashboard.

I have created a support ticket in our MailPoet premium account.

[18-Feb-2020 16:34:48 UTC] PHP Fatal error:  Uncaught ReflectionException: Property MailPoet\Entities\NewsletterEntity::$children does not exist in /htdocs/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/common/lib/Doctrine/Common/Persistence/Mapping/RuntimeReflectionService.php:75
Stack trace:
#0 /htdocs/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/common/lib/Doctrine/Common/Persistence/Mapping/RuntimeReflectionService.php(75): ReflectionProperty->__construct('MailPoet\\Entiti...', 'children')
#1 /htdocs/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/Mapping/ClassMetadataInfo.php(849): MailPoetVendor\Doctrine\Common\Persistence\Mapping\RuntimeReflectionService->getAccessibleProperty('MailPoet\\Entiti...', 'children')
#2 /htdocs/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/Mapping/ClassMetadataFactory.php(589): MailPoetVendor\Doctrine\ORM\Mapping\ClassMetadataInfo->wakeupReflection(Object(MailPoetVendor\Doctrine\Common\Per in /htdocs/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/common/lib/Doctrine/Common/Persistence/Mapping/RuntimeReflectionService.php on line 75

We run MailPoet3 (+Premium), PHP 7.2, MySQL 5.6, WordPress 5.2.1 and Apache 2.4.

I get the same error message when activating the plugin:

– WordPress 5.2.1
– WP multisite network
– WP LiveChat 8.0.36
– PHP 7.2

The message appears on top of the dashboard as well as in front-end pages.

That’s a great new year resolution ??

Here is some statistics I found: gs.statcounter.com/screen-resolution-stats.

1920 px refer to 1080p, usually known as Full HD.
2048 px refer to 2K.

Me too. Same error message.

Hi Daniel,

thanks a lot for your quick response and improvement.

I have replaced the old code lines by the new one, and it worked right away.

No more rating stuff in the blog feed output.

Kind regards, Exyst

Thanks for your hint. I was wondering about that too.

Thanks for your quick response as my question was a bit vague. First of all, we would need to import posts from FirstSpirit into WordPress on a regular basis. Lets say, any time we log into our WP dashboard we could retrieve the latest posts from FS (and publish them in our WP site etc).

I did not find any extensions for that in the WP plugin directory (searching for “firstspirit”), neither in Google. I have read FirstSpirit provides an API too, but before we start developing it from scratch I wanted to ask if there are already hints or solutions available about that connection.

Great, thanks a lot for your quick answer. We are testing the upgrade at the moment on our WP multisite platform and it seems to be working.

The only little bug I found are these broken images on the URE settings page in the dashboard. The small help icons are not displayed.

But I could resolve it. There is a double slash // in the image source path. I opened the URE script “includes/class-ure-lib.php” and removed the slash in line 1319: ... URE_PLUGIN_URL . '/images/help.png" ... Then the help images were properly displayed.

We have similar problems after upgrading Polylang from 1.4.5 to 1.5.1 (in WP 3.5.1).

Our menu allocations (theme locations) suddenly get lost. After re-allocating and saving the menus (Appearance > Menus), they show up for a while, then disappear again in our blog pages. Example: they disappear right away when I reassign our header image and save it. When I reassign our menus, then the header image will be gone.

It worked well prior to the latest upgrade. I downgraded the plugin back to version 1.4.5 and everything is fine.

Thanks for your quick answer.

I found a warning in our PHP error log: “Input variables exceeded 1000. To increase the limit change max_input_vars in php.ini”.

That’s the solution. I added the directive to “php.ini”, restarted the web server and everything worked fine in BackWPup. Example:

max_input_vars = 1200

Indeed, “post_max_size” etc has to be large enough too.

I suppose, this topic can be regarded as solved.

… continued …

After my first attempt I also checked some other javascript files in WordPress, especially those provided by plugins. I found scripts with different file formats like ANSI, UTF, etc. I didnt find another UTF8 BOM in a file, but I disabled a plugin and the problem was gone.

I suppose this load-scripts error can appear in various situations, so there might not be a single way of solution. But the first thing I would check is the script files involved. Since load-scripts.php is concatenating several javascripts needed on a certain page they should definitely have a proper (and similar?) file format and encoding.

Hi,
I have the same issue with WordPress 3.5.1, showing me this Javascript syntax error, unexpected token illegal. What I found is a bug present in the current WP version concerning unnecessary BOM marks in UTF-8 encoded scripts: https://core.trac.www.ads-software.com/ticket/23315.

There is a UTF-8 BOM in ./wp-includes/js/jquery/jquery.query.js which you have to remove. You need an appropriate text editor like Notepad++ or UltraEdit and encode/save the file without BOM.

Nevertheless it didnt work for me so far. There are other complaints about this WordPress bug on the internet too.

Regards