• Resolved jimmybtd

    (@jimmybtd)


    Hi there,

    We’ve update Mailpoet to latest version 3.99.0 and get this error.
    Wordpress is in latest version also.

    Already tried deactivate all plugin except Mailpoet and switching default theme, still got this error.

    Some of the Error :
    MailPoet Error: PDOException: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry ‘WordPress Users’ for key ‘name’ in /home/public_html/staging/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:59
    Stack trace:
    #0 /home/public_html/staging/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php(59): PDOStatement->execute(NULL)
    #1 /home/public_html/staging/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/dbal/lib/Doctrine/DBAL/Statement.php(75): MailPoetVendor\Doctrine\DBAL\Driver\PDOStatement->execute(NULL)
    #2 /home/public_html/staging/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/dbal/lib/Doctrine/DBAL/Statement.php(102): MailPoetVendor\Doctrine\DBAL\Statement->execute(NULL)
    #3 /home/public_html/staging/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/Persisters/Entity/BasicEntityPersister.php(111): MailPoetVendor\Doctrine\DBAL\Statement->executeStatement()`

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Dani F. a11n

    (@danielinhou)

    Hi there @jimmybtd ????!

    Thank you for reaching out to MailPoet Support!

    We’ve update Mailpoet to latest version 3.99.0 and get this error.
    Wordpress is in latest version also.

    Oh, I’m sorry to hear you’re having problems with our plugin. It seems this issue requires further investigation and we will ask our dev team for advice on how to troubleshoot it. Once we have some news about what the next steps are, we will get back to you.

    By the way, can you confirm the error appeared after the update?

    Thanks for your patience.

    Cheers!

    Thread Starter jimmybtd

    (@jimmybtd)

    By the way, can you confirm the error appeared after the update?

    Yes, This error is on our staging site.
    In our live site, still using Mailpoet V 3.96.1, we haven’t update it yet. We’ve already activate debugging and no error coming up.

    Screenshot : https://prnt.sc/2C3SR6mSu0q6

    Plugin Author Bruna a11n

    (@bruberries)

    Hi @jimmybtd,

    Yes, This error is on our staging site.

    Can you please let us know if you have migrated your database from another place when creating your staging website?

    If that’s the case, could you please check your mailpoet_segments and mailpoet_subscribers tables and let me know if you have a different name for the wp_users column?

    Thread Starter jimmybtd

    (@jimmybtd)

    Hello,

    Can you please let us know if you have migrated your database from another place when creating your staging website?
    No, it was a clone in the same server/account.

    If that’s the case, could you please check your mailpoet_segments and mailpoet_subscribers tables and let me know if you have a different name for the wp_users column?

    We’re not quite understand the instruction. We’ve check the table and got this :
    https://prnt.sc/-YcZjTaNeZ5D
    When we try to rename the type “wpgs_users” to “wp_users”, Mailpoet already can be accessed and no error coming up. Tried to rename it back, error showing up again.
    wpgs_ is our database prefix.

    Thanks

    Plugin Author Bruna a11n

    (@bruberries)

    Hi @jimmybtd,

    When we try to rename the type “wpgs_users” to “wp_users”, Mailpoet already can be accessed and no error coming up.

    Yes, that’s exactly what you need to do. Please change “wpgs_users” to “wp_users” in this table, and also in the mailpoet_subscribers table. No need to change your database prefix though.

    Thanks!

    Plugin Author Bruna a11n

    (@bruberries)

    Hey @jimmybtd,

    We haven’t heard back from you in a while, so I’m going to mark this as resolved – we’ll be here if and/or when you are ready to continue.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Mailpoet Error PDO’ is closed to new replies.