woylon

That’s strange – suddenly I can comment here again after this thread was not editable a few days ago. The Avada team responds to my emails within 48 hours. Would you like me to try contacting you? I may need an email address or something similar for that.

A downgrade can not be the right solution or what do you say @ironikus

Otherwise: Where can I get the old version?

You want me to change my 1-star rating just because you’re working on the bug? Sorry, but that makes no sense! When the bug is finally fixed, then maybe I’ll reconsider, but definitely not before!

I also left a rating HERE because there are enough good alternatives and I do not depend on this PlugIn. With my rating, I just wanted to “warn” other users. A change to the classic support is therefore not necessary for me.

Thank you for the detailed reply. I have already discovered the function for deleting the data, but this obviously remains without function, and THAT upsets me.

Unfortunately, the error persists. It can’t be a solution that I always have to deactivate your plugin to be able to update other plugins.

Attached again the last error message I received by email.

Wenn du Hilfe bei diesem Problem suchst, wirst du m?glicherweise nach einigen der folgenden Informationen gefragt:
WordPress-Version 5.8.3
Aktuelles Theme: Avada (Version 7.6)
Aktuelles Plugin: MailPoet 3 (New) (Version 3.76.0)
PHP-Version 7.4.26

Fehler-Details
==============
Ein Fehler vom Typ E_ERROR wurde in der Zeile 2 der Datei /home/www/mydomain.de/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/dbal/lib/Doctrine/DBAL/Driver/AbstractMySQLDriver.php verursacht. Fehlermeldung: Uncaught PDOException: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away in /home/www/mydomain.de/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOConnection.php:2
Stack trace:
#0 /home/www/mydomain.de/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOConnection.php(2): PDO->query(‘SELECT w0_.name…’)
#1 /home/www/mydomain.de/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOQueryImplementation.php(2): MailPoetVendor\Doctrine\DBAL\Driver\PDOConnection->doQuery(‘SELECT w0_.name…’)
#2 /home/www/mydomain.de/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(2): MailPoetVendor\Doctrine\DBAL\Driver\PDOConnection->query(‘SELECT w0_.name…’)
#3 /home/www/mydomain.de/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/Query/Exec/SingleSelectExecutor.php(2): MailPoetVendor\Doctrine\DBAL\Connection->exec

I have now had my hosting provider set the values requested in the article. Unfortunately without success.

I have now tried the debugging tool Query and got this error when I was in the wordpress backend. So here is definitely an error in the PlugIn and not with me.

see the bug: https://ibb.co/QF1JJnk

I hosted my website and do NOT run my own server. It’s a pity that this PlugIn was written so resource-hungry that a database connection breaks, which otherwise never happens.

After consulting with my hoster, the problem was solved. Unfortunately I didn’t get any details about the solution, but I’m glad it wasn’t this plugin. I have changed the rating from 1 star to 5 stars. ??

If this is the case, why is the opening of the additional Terms & Conditions plug-in more attractive/programmed differently?

This is just a suggestion to adapt it.

After several tests I have now found out what caused the error: In the redirects was referred to logout page. This caused a loop. Perhaps a check should be built into the redirects to avoid such loops?

I have exactly the same problem and have identified this plugin as the cause via FTP. I must now look for an alternative, because this plugin seems to be very buggy.