Rostislav Wolny
Forum Replies Created
-
Forum: Reviews
In reply to: [MailPoet - Newsletters, Email Marketing, and Automation] Not great.Hi there,
Thank you for reaching to us!since setting up an email template to send AUTOMATICALLY when a new post is published on my site, this plugin has NEVER worked properly. Every time I publish a new post, the supposed new post notification email never deploys, so I have to disable it, duplicate it, and try the process all over again
Sorry to hear about the issue. The functionality should work without the need of duplicating the post-notification template. The notification email is scheduled immediately after it is activated and then each time a new post is published. It looks like the first part works for you, but the automatic scheduling is broken. Publishing a post is an action used by many plugins, so there is a chance that this might be a plugin conflict.
Can you switch your theme to a default one (Twenty Twenty-Four) and disable all your plugins and see if automatic post notifications in MailPoet works? I would suggest disabling all post notifications you have created and keeping just one set to a testing list.If it does work, enable your theme and all your other plugins one after the other until MailPoet breaks again. You’ll be able to tell us what’s at fault.
You can refer to this article: https://kb.mailpoet.com/article/204-how-to-test-for-plugins-conflict
Let us know how that goes!
Forum: Plugins
In reply to: [MailPoet - Newsletters, Email Marketing, and Automation] Database CleanupHi there,
The existence of the tables indicates that the plugin used to be installed on the site. MailPoet doesn’t remove tables on uninstall so that users don’t lose data.
I see that on the list there are not all tables that MailPoet plugin currently uses (e.g.wpstg0_mailpoet_migrations
is missing) so this seems to be from an older version.If you don’t mind losing the data from previous plugin usage, these tables are safe to remove. The plugin will recreate empty tables when installed again.
Hi there, the issue was fixed in v 4.40.0.