Critical Issue – E_ERROR on the line 1422
-
Hi, I am receiving the following critical error:
When you seek help with this issue, you may be asked for the following information: WordPress version 6.1.1 Active theme: Blocksy (version 1.8.59) Current plugin: MailPoet (version 4.1.0) PHP version 8.1.12 Error Details ================== An error of the type has occurred E_ERROR on the line 1422 from the file /public_html/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/UnitOfWork.php. Error message: Uncaught Error: Call to a member function setValue() on callable in /public_html/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/UnitOfWork.php:1422 Stack trace: #0 /public_html/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/Internal/Hydration/SimpleObjectHydrator.php(104): MailPoetVendor\Doctrine\ORM\UnitOfWork->createEntity() #1 /public_html/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/Internal/Hydration/SimpleObjectHydrator.php(41): MailPoetVendor\Doctrine\ORM\Internal\Hydration\SimpleObjectHydrator->hydrateRowData() #2 /public_html/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/Internal/Hydration/AbstractHydrator.php(119): MailPoetVendor\Doctrine\ORM\Internal\Hydration\SimpleObjectHydrator->hydrateAllData() #3 /public_html/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/Persisters/Entity/BasicEntityPersister.php(381): MailPoetVendor\Doctrine\ORM\Internal\Hydration\AbstractHydrator->hydrateAll() #4 /public_html/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/EntityRepository.php(78): MailPoetVendor\Doctrine\ORM\Persisters\Entity\BasicEntityPersister->load() #5 /public_html/wp-content/plugins/mailpoet/lib/Doctrine/Repository.php(69): MailPoetVendor\Doctrine\ORM\EntityRepository->findOneBy() #6 /public_html/wp-content/plugins/mailpoet/lib/Segments/SegmentsRepository.php(73): MailPoet\Doctrine\Repository->findOneBy() #7 /public_html/wp-content/plugins/mailpoet/lib/WooCommerce/Subscription.php(169): MailPoet\Segments\SegmentsRepository->getWooCommerceSegment() #8 /public_html/wp-content/plugins/mailpoet/lib/PostEditorBlocks/WooCommerceBlocksIntegration.php(101): MailPoet\WooCommerce\Subscription->isCurrentUserSubscribed() #9 /public_html/wp-includes/class-wp-hook.php(308): MailPoet\PostEditorBlocks\WooCommerceBlocksIntegration->registerCheckoutFrontendBlocks() #10 /public_html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters() #11 /public_html/wp-includes/plugin.php(517): WP_Hook->do_action() #12 /public_html/wp-content/plugins/woocommerce/packages/woocommerce-blocks/src/Integrations/IntegrationRegistry.php(48): do_action() #13 /public_html/wp-content/plugins/woocommerce/packages/woocommerce-blocks/src/BlockTypes/AbstractBlock.php(114): Automattic\WooCommerce\Blocks\Integrations\IntegrationRegistry->initialize() #14 /public_html/wp-content/plugins/woocommerce/packages/woocommerce-blocks/src/BlockTypes/AbstractBlock.php(70): Automattic\WooCommerce\Blocks\BlockTypes\AbstractBlock->initialize() #15 /public_html/wp-content/plugins/woocommerce/packages/woocommerce-blocks/src/BlockTypesController.php(64): Automattic\WooCommerce\Blocks\BlockTypes\AbstractBlock->__construct() #16 /public_html/wp-includes/class-wp-hook.php(308): Automattic\WooCommerce\Blocks\BlockTypesController->register_blocks() #17 /public_html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters() #18 /public_html/wp-includes/plugin.php(517): WP_Hook->do_action() #19 /public_html/wp-settings.php(617): do_action() #20 /public_html/wp-config.php(111): require_once('/...') #21 /public_html/wp-load.php(50): require_once('/...') #22 /public_html/wp-admin/admin-ajax.php(22): require_once('/...') #23 {main} thrown
I was reviewing the following post with a similar error, but they do not comment if it was solved.
https://www.ads-software.com/support/topic/critical-issue-mailpoet-version-4-1-0/
Cheers,
Viewing 2 replies - 1 through 2 (of 2 total)
Viewing 2 replies - 1 through 2 (of 2 total)
- The topic ‘Critical Issue – E_ERROR on the line 1422’ is closed to new replies.