Rajat Sharma

Hi,
Please follow below steps to replicate this issue:
1. Login to the WordPress Dashboard(WP Admin).
2. Go to the Media Admin Menu.
3. Choose any image.
4. Click “Delete Permanently” link.

When you click on the link you we see the error alert message “Error in deleting the attachment”.
Once we reload the media backend page. The media attachment is able to delete but it is showing that error message which is confusing to the user.

Please fix this ASAP.

• This reply was modified 4 months, 3 weeks ago by Rajat Sharma.

Any update on this?

We are getting this message in a form of alert box. We are not getting any error message in the error log while performing this action.
In the JavaScript console we didn’t get any error. In the Ajax action callback response in the network tab the response is showing 1. I hope this information will help you to solve this issue.

Hi,

I have reviewed all the points and performed the suggested activities.

Could you please provide a solution for this issue?

We have sufficient memory limit, found no errors in the error log during this process, and no errors in the browser console. We also have sufficient user and file permissions.

The media is being deleted and does not appear after a page refresh, but we consistently receive the error “Error in deleting the attachment” during the deletion process. The Ajax response returns 1.

Hi @omarfpg ,

We have generated the request through WooCommerce.com but we didn’t get any response from them.

We have two tickets the latest one is 8217727 and the previous one is 8204599.

We have also replied back to the [email protected] and [email protected]. However we only received the bot message as a reply.

Please fix this ASAP. We can share the transaction details and the purchase receipt that we got.

• This reply was modified 6 months, 1 week ago by Rajat Sharma.

Still, we are getting the same error with update plugin also.

[07-Mar-2023 09:36:02 UTC] PHP Fatal error:  Uncaught MailPoetVendor\Doctrine\ORM\ORMInvalidArgumentException: A new entity was found through the relationship 'MailPoet\Entities\SendingQueueEntity#task' that was not configured to cascade persist operations for entity: MailPoet\Entities\ScheduledTaskEntity@9764. To solve this issue: Either explicitly call EntityManager#persist() on this unknown entity or configure cascade persist this association in the mapping for example @ManyToOne(..,cascade={"persist"}). If you cannot find out which entity causes the problem implement 'MailPoet\Entities\ScheduledTaskEntity#__toString()' to get a clue. in /wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/ORMInvalidArgumentException.php:45
Stack trace:
#0 /wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/UnitOfWork.php(1827): MailPoetVendor\Doctrine\ORM\ORMInvalidArgumentException::newEntitiesFoundThroughRelationships()
#1 /wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/UnitOfWork.php(138): MailPoetVendor\Doctrine\ORM\UnitOfWork->assertThatThereAreNoUnintentionallyNonPersistedAssociations()
#2 /wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/EntityManager.php(171): MailPoetVendor\Doctrine\ORM\UnitOfWork->commit()
#3 /wp-content/plugins/mailpoet/lib/Doctrine/Repository.php(118): MailPoetVendor\Doctrine\ORM\EntityManager->flush()
#4 /wp-content/plugins/mailpoet/lib/Logging/LogHandler.php(65): MailPoet\Doctrine\Repository->flush()
#5 /wp-content/plugins/mailpoet/vendor-prefixed/monolog/monolog/src/Monolog/Handler/AbstractProcessingHandler.php(18): MailPoet\Logging\LogHandler->write()
#6 /wp-content/plugins/mailpoet/vendor-prefixed/monolog/monolog/src/Monolog/Logger.php(114): MailPoetVendor\Monolog\Handler\AbstractProcessingHandler->handle()
#7 /wp-content/plugins/mailpoet/vendor-prefixed/monolog/monolog/src/Monolog/Logger.php(218): MailPoetVendor\Monolog\Logger->addRecord()
#8 /wp-content/plugins/mailpoet/lib/Cron/Daemon.php(63): MailPoetVendor\Monolog\Logger->error()
#9 /wp-content/plugins/mailpoet/mailpoet-cron.php(61): MailPoet\Cron\Daemon->run()
#10 {main}
  thrown in /wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/ORMInvalidArgumentException.php on line 45


[07-Mar-2023 09:37:02 UTC] PHP Fatal error:  Uncaught MailPoetVendor\Doctrine\ORM\ORMInvalidArgumentException: A new entity was found through the relationship 'MailPoet\Entities\SendingQueueEntity#task' that was not configured to cascade persist operations for entity: MailPoet\Entities\ScheduledTaskEntity@9790. To solve this issue: Either explicitly call EntityManager#persist() on this unknown entity or configure cascade persist this association in the mapping for example @ManyToOne(..,cascade={"persist"}). If you cannot find out which entity causes the problem implement 'MailPoet\Entities\ScheduledTaskEntity#__toString()' to get a clue. in /wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/ORMInvalidArgumentException.php:45
Stack trace:
#0 /wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/UnitOfWork.php(1827): MailPoetVendor\Doctrine\ORM\ORMInvalidArgumentException::newEntitiesFoundThroughRelationships()
#1 /wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/UnitOfWork.php(138): MailPoetVendor\Doctrine\ORM\UnitOfWork->assertThatThereAreNoUnintentionallyNonPersistedAssociations()
#2 /wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/EntityManager.php(171): MailPoetVendor\Doctrine\ORM\UnitOfWork->commit()
#3 /wp-content/plugins/mailpoet/lib/Doctrine/Repository.php(118): MailPoetVendor\Doctrine\ORM\EntityManager->flush()
#4 /wp-content/plugins/mailpoet/lib/Logging/LogHandler.php(65): MailPoet\Doctrine\Repository->flush()
#5 /wp-content/plugins/mailpoet/vendor-prefixed/monolog/monolog/src/Monolog/Handler/AbstractProcessingHandler.php(18): MailPoet\Logging\LogHandler->write()
#6 /wp-content/plugins/mailpoet/vendor-prefixed/monolog/monolog/src/Monolog/Logger.php(114): MailPoetVendor\Monolog\Handler\AbstractProcessingHandler->handle()
#7 /wp-content/plugins/mailpoet/vendor-prefixed/monolog/monolog/src/Monolog/Logger.php(218): MailPoetVendor\Monolog\Logger->addRecord()
#8 /wp-content/plugins/mailpoet/lib/Cron/Daemon.php(63): MailPoetVendor\Monolog\Logger->error()
#9 /wp-content/plugins/mailpoet/mailpoet-cron.php(61): MailPoet\Cron\Daemon->run()

Please fix this issue.

@asmipatel – We are already following that configuration.

We have found that when we are accessing the site as a logged-in user then the campaign is translated into both languages.

but when we are accessing the site as a non-logged-in user then the popup is showing the default language content only.

Please fix it ASAP.

Hi,
Is there any update?

https://www.falconsound.org/main-calendar/