Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Yuliyan Slavchev

    (@yuliyan)

    I apologize for the confusion with my initial reply. I initially wrote that I had reproduced the issue, but after looking into it further, I realized that what I was seeing was actually the case described in my follow-up reply – the subscribers in the Trash were all WooCommerce customers, so the Empty Trash action skipped deleting them, which is the expected behavior.

    Other than that, I couldn’t find any issues with the Empty Trash button. When triggered on standard subscribers, they were permanently deleted as expected.

    Since I haven’t been able to reproduce the problem, it’s possible there’s an issue specific to your site’s setup that we’ll need to investigate further. As you’re a MailPoet customer, could you please open a support ticket through our support system so we can continue troubleshooting there?
    https://www.mailpoet.com/support/premium/

    In the meantime, as a workaround, you could try changing the status of the subscribers you’re trying to delete to Unsubscribed. Unsubscribed subscribers are not counted toward your subscriber limit, so this should help reduce the total count.

    Plugin Author Yuliyan Slavchev

    (@yuliyan)

    Hi again, @ldekay,

    One thing worth checking – are the subscribers in your Trash also WooCommerce customers or WordPress users?

    If that is the case, MailPoet intentionally does not permanently delete subscribers who are connected to a WordPress or WooCommerce account, because these records are linked to orders, logins, and other site data. Therefore, when you click Empty Trash, any linked subscribers will remain.

    If these subscribers are already Unsubscribed, they should already be excluded from the total subscriber count. You can use the Recalculate action to make sure the count is updated.

    Regarding the Trash listing, we will update the UI to make it clearer that WooCommerce customers and WordPress users cannot be permanently deleted.

    Plugin Author Yuliyan Slavchev

    (@yuliyan)

    Thank you for reporting this, and I’m sorry for the inconvenience.

    I was able to reproduce the issue, so it does appear to be a bug. Our team is looking into it now, and we’ll work on getting it resolved as soon as possible.

    I’ll keep you updated as soon as we have a fix or have more information to share.

    Plugin Author Yuliyan Slavchev

    (@yuliyan)

    Hi, @elcolorino.

    Following up on this – in the latest MailPoet version 5.31.0, we added a notice for emails that have already been sent, along with a quick “Duplicate” action directly within the email editor. This should make it clearer why the email can’t be sent again and provide an easier way to reuse it.

    Thanks again for the feedback!

    I’ll close this thread for now, but feel free to reopen it if you have any further questions or run into any issues.

    Plugin Author Yuliyan Slavchev

    (@yuliyan)

    Hi, @elcolorino.

    Thanks for the feedback. We’re still working toward feature parity with the classic editor, so feedback like this is very helpful.

    For test emails, we don’t currently limit the recipient address based on the selected list or segment. That’s the same behavior as in the classic email editor.

    For the disabled “Review and send” button, as you discovered, emails that have already been sent can’t be sent again. To reuse the email, you’ll need to duplicate it first. We’ll work on making this clearer in the block editor so it’s easier to understand what’s happening and what to do next.

    Thread Starter Yuliyan Slavchev

    (@yuliyan)

    I found Are_Paypal plugin which includes everything I want, but it also includes paypal integration and I want something simple.

Viewing 6 replies - 1 through 6 (of 6 total)