Skip to content
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

Safe deactivation / fallback status #186

Open
stevejburge opened this issue May 17, 2024 · 3 comments
Open

Safe deactivation / fallback status #186

stevejburge opened this issue May 17, 2024 · 3 comments

Comments

@stevejburge
Copy link
Member

If you move posts to a custom status and then disable PublishPress Statuses, those posts will disappear from the WordPress admin

Can we decide on a fallback approach?

@stevejburge stevejburge added this to the 1.0: Bug Fixes milestone May 17, 2024
@agapetry
Copy link
Contributor

@stevejburge This would need to be associated with a very intentional "delete plugin data" type of operation. On a normal Statuses plugin de/re-activation, it's important that posts retain their custom status. I think archiving / restoring assigned custom statuses for each post would be unwieldy and asking for trouble.

@agapetry
Copy link
Contributor

Moving milestones, as this is a significant task and it's time to move on with the current release.

@agapetry agapetry changed the title Do we need a fallback status? Safe deactivation / fallback status Sep 16, 2024
@agapetry
Copy link
Contributor

I think it's important for us to think through the logistics of this and design an implementation that clarifies intentions, not rush into a change in the default deactivation behavior based on a few suggestions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants