Skip to content

Latest commit

 

History

History
96 lines (57 loc) · 3.56 KB

README.md

File metadata and controls

96 lines (57 loc) · 3.56 KB
Raw

blavetstudio/wp-cli-db-anonymize

Build Status

Quick links: Using | Installing | Contributing | Support

$ wp db-anonymize --help

Using

$ wp db-anonymize

Anonymizes WordPress users table:

  • user_login
  • user_nicename
  • display_name
  • user_email

And usermeta table:

  • nickname
  • first_name
  • last_name

$ wp db-anonymize --woocommerce

Anonymizes WordPress and WooCommerce usermeta table fields:

  • billing_*
  • shipping_*

...and postmeta table fields related to orders:

  • _billing_*
  • _shipping_*

$ wp db-anonymize --user-meta=blavet_

Anonymizes WordPress and all usermeta rows containing the string 'blavet_'. You can also pass a comma separated list to have multiple metas anonymized

$ wp db-anonymize --user-whitelist=1

Anonymizes all WordPress users but doesn't anonymize user with id 1

$ wp db-anonymize --no-confirm

Anonymizes all WordPress users without confirmation prompt

Installing

Installing this package requires WP-CLI v2.5 or greater. Update to the latest stable release with wp cli update.

Once you've done so, you can install the latest stable version of this package with:

wp package install blavetstudio/wp-cli-db-anonymize:@stable

To install the latest development version of this package, use the following command instead:

wp package install blavetstudio/wp-cli-db-anonymize:dev-master

Contributing

We appreciate you taking the initiative to contribute to this project.

Contributing isn’t limited to just code. We encourage you to contribute in the way that best fits your abilities, by writing tutorials, giving a demo at your local meetup, helping other users with their support questions, or revising our documentation.

For a more thorough introduction, check out WP-CLI's guide to contributing. This package follows those policy and guidelines.

Reporting a bug

Think you’ve found a bug? We’d love for you to help us get it fixed.

Before you create a new issue, you should search existing issues to see if there’s an existing resolution to it, or if it’s already been fixed in a newer version.

Once you’ve done a bit of searching and discovered there isn’t an open or fixed issue for your bug, please create a new issue. Include as much detail as you can, and clear steps to reproduce if possible. For more guidance, review our bug report documentation.

Creating a pull request

Want to contribute a new feature? Please first open a new issue to discuss whether the feature is a good fit for the project.

Once you've decided to commit the time to seeing your pull request through, please follow our guidelines for creating a pull request to make sure it's a pleasant experience. See "Setting up" for details specific to working on this package locally.

Support

GitHub issues aren't for general support questions, but there are other venues you can try: https://wp-cli.org/#support