It seems that there is nothing take care regarding the existing users if you are installing this module on a running site. (thanks to @amateescu for the clarification)

Thus, we could add this information in the main page:

If you install this module on a running site, all existing users will be assigned the user bundle by default.

Is there other issues/questions we should think about?

ex:
-Views or any configuration which are using the user entity?
-Any (not compatible) module which are overriding the users forms or the user entity or anything which can collide?
-Anything with the Webprofiler (see https://www.drupal.org/project/user_bundle/issues/3143517)

Issue fork user_bundle-3143532

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

DuneBL created an issue. See original summary.

amateescu made their first commit to this issue’s fork.

amateescu opened merge request !10

amateescu’s picture

amateescu commented
Status: Active » Needs review

Wrote some info about the behavior after installation in the README and on the project page as well.

  • amateescu committed 0739808e on 8.x-1.x 
    task: #3143532 Document installing on a site with existing users

By:...
amateescu’s picture

amateescu commented
Title: Explain what to do if installing on a site containing some config » Document installing on a site with existing users
Status: Needs review » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.