Push-to-live erases new subscribers!!!

[LanceHaverkamp]

I’m seeing a problem for websites who use a staging area to make changes to their website, then push-to-live the upgrades. This overwrites the newsletter subscribers in the database, with an older list of subscribers. Pushing a new website to live essentially erases all the new subscribers every time a revised website is pushed live.

If Newsletter kept its own database this wouldn’t happen; but with subscribers kept in/under wp_options, how can we push a new website live while preserving new subscribers?

[Stefano]

Newsletter stores the options on wp_options as every other plugin, and subscribers, newsletters, logs, …, on custom tables. So your publishing system is probably publishing even those custom tables.

[LanceHaverkamp]

So, what is the solution?

* Can Mailman handle the subscriptions & delivery?
* Can your plugin use different database?

[Author]

Posts