New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Multisite Uninstall #136

Closed
jaswrks opened this Issue Aug 8, 2015 · 3 comments

Comments

Projects
None yet
2 participants
@jaswrks
Member

jaswrks commented Aug 8, 2015

Overview

The uninstaller for Comment Mail should consider that each child blog in a network could have been running the Comment Mail plugin. For that reason, the uninstaller should attempt to iterate through each blog and apply the uninstall routines to each child blog in order to remove all traces.

Referencing: https://github.com/websharks/comment-mail/blob/150709/comment-mail/includes/classes/uninstaller.php#L52-L60

@raamdev

This comment has been minimized.

Contributor

raamdev commented Oct 8, 2015

Next Lite Release Changelog:

  • Bug Fix: Fixed a Multisite uninstallation bug that was preventing Comment Mail from taking Child Blogs into consideration when uninstalling, which was resulting in an incomplete uninstallation. See Issue #136.
@raamdev

This comment has been minimized.

Contributor

raamdev commented Oct 8, 2015

Next Pro Release Changelog:

  • Bug Fix: Fixed a Multisite uninstallation bug that was preventing Comment Mail from taking Child Blogs into consideration when uninstalling, which was resulting in an incomplete uninstallation. See Issue #136.

@websharks websharks locked and limited conversation to collaborators Dec 24, 2015

@raamdev

This comment has been minimized.

Contributor

raamdev commented Dec 24, 2015

Comment Mail v151224 has been released and includes changes from this GitHub Issue: See the v151224 announcement for further details.


This issue will now be locked to further updates. If you have something to add related to this GitHub Issue, please open a new GitHub Issue and reference this one (#136).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.