-
Notifications
You must be signed in to change notification settings - Fork 1
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
Consider adding --dry-run as an option for destructive wp post and wp user commands #89
Comments
Hi @davemac, Thanks for the suggestion. Can you explain in greater detail how this might work? What's the problem you're trying to solve? |
@danielbachhuber I recently ran the following on a staging site (deletes all thumbnail images from a post type):
The Of course, this would not substitute for backing up the database. |
Just to tease out the idea further, how would this be helpful? Can't you already do this with |
You are correct, and in fact I ran that command before doing the delete. That's when I thought maybe just adding a --dry-run to the delete would be a nice option and make dry runs more accessible to users. If done globally on destructive |
Makes sense, thanks @davemac. I think implementing a |
I think this would be useful for lots of different commands. For instance, |
When deleting post and user data/meta, it would be handy to have a
--dry-run
option to see what the results of running that command may be.The text was updated successfully, but these errors were encountered: