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

Allow import from WP User Avatar / ProfilePress #80

Closed
jeffpaul opened this issue Jul 14, 2021 · 2 comments · Fixed by #85
Closed

Allow import from WP User Avatar / ProfilePress #80

jeffpaul opened this issue Jul 14, 2021 · 2 comments · Fixed by #85
Assignees
Labels
type:enhancement New feature or request.
Milestone

Comments

@jeffpaul
Copy link
Member

Is your enhancement related to a problem? Please describe.
As seen on WP.org, folks are migrating to Simple Local Avatars from WP User Avatar / ProfilePress and looking for help migrating in their users avatars.

Describe the solution you'd like
Leverage Gist to help script this migration (properly crediting the author of course).

Designs
Possibly include an “Import settings from…” option in settings to import settings from competing plugins starting with WP User Avatar.

Describe alternatives you've considered

Additional context

@jeffpaul jeffpaul added type:enhancement New feature or request. help wanted labels Jul 14, 2021
@jeffpaul jeffpaul added this to the 2.3.0 milestone Jul 14, 2021
@claytoncollie
Copy link
Contributor

Hi @jeffpaul @helen Sent me this issue and said it would be a good one to get my feet wet with the OSS practice. Below is how I would tackle this issue. Please send me your direction and I'll work on this over the next week or so :)

  • Write function from gist linked in main issue to migrate from Wp User Avatar
  • Wrap script into wp-cli command wp simple-loca-avatars migrate wp-user-avatar
  • Add button to options-dicussion.php to run script from wp-admin using either REST API or AJAX

The only part I do not agree with within the gist is to delete the Wp User Avatar value in the database. It should not be the responsibility of a plugin to remove another's data. A site owner might wish to go back to the original plugin and need the original data there. Also, if the script fails halfway through, having the original data present can aid in re-running the script from the start.

@jeffpaul
Copy link
Member Author

@claytoncollie the other part to consider is functionality in multisite, as I got a report that the gist wasn't working on multisite so you'll want to check that as you get into crafting the function. Otherwise your approach sounds good! 🚀

@claytoncollie claytoncollie mentioned this issue Oct 19, 2021
6 tasks
@claytoncollie claytoncollie linked a pull request Oct 19, 2021 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:enhancement New feature or request.
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants