update 3.45.1 give me this error

  • today i have updated my mailpoet 3 plugin and the front end suddenly give a problem , activating the wordpress debug i receive this error:

    Notice: unserialize(): Error at offset 466 of 1824 bytes in xxxxxxxxxxxx/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/dbal/lib/Doctrine/DBAL/Types/ArrayType.php on line 57

    Fatal error: Uncaught MailPoetVendor\Doctrine\DBAL\Types\ConversionException: Could not convert database value “a:8:{i:0;a:7:{s:4:”t…” to Doctrine Type array in /xxxxxxxxxxxxxx/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/dbal/lib/Doctrine/DBAL/Types/ConversionException.php:48

    Stack trace:
    #0 /xxxxxxxxxxxxxxxxx/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/dbal/lib/Doctrine/DBAL/Types/ArrayType.php(59): MailPoetVendor\Doctrine\DBAL\Types\ConversionException::conversionFailed(‘a:8:{i:0;a:7:{s…’, ‘array’)
    #1 /xxxxxxxxxxxxxxxxxxx/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/Internal/Hydration/SimpleObjectHydrator.php(110): MailPoetVendor\Doctrine\DBAL\Types\ArrayType->convertToPHPValue(‘a:8:{i:0;a:7:{s…’, Object(MailPoetVendor\Doctrine\DBAL\Platforms\MySqlPlatform))
    #2 /xxxxxxxxxxxxxxxxxxxxxxx/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/Internal/Hydration/SimpleObjectHydrator.php(64): MailPoetVendor\Doctrine\ORM\Internal\Hydration\Simp in /xxxxxxxxxxxxxxxxxxxxxxxx/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/dbal/lib/Doctrine/DBAL/Types/ConversionException.php on line 48

    i have to disable mailpoet3 plugin (and so premium version) in order to avoid the error and correctly see the front end;
    can you help me to solve this problem?

    • This topic was modified 4 years, 9 months ago by urghesgrunt.
Viewing 4 replies - 1 through 4 (of 4 total)

  • Hi @urghesgrunt

    We are very sorry about that. Please contact us here so we can work on a fix for that issue: https://www.mailpoet.com/support/wordpress-forums/

    Thread Starter urghesgrunt

    (@urghesgrunt)

    testing the frontend we noticed the fatal error occurs when in the template there is the function get_the_excerpt() and the_content(), is possible that is someting related to the new addition :

    = 3.45.1 – 2020-02-11 =
    * Added: new option to automatically include signup forms below every post and page;

    even if this option is disabled?

    Thread Starter urghesgrunt

    (@urghesgrunt)

    we have done a roll back to the previuos 3.45.0 version to quickly fix, waiting for the next version that solve the problem..

    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.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘update 3.45.1 give me this error’ is closed to new replies.