Population does not work for Users in Users-Permissions

[kamal-choudhary]

Bug report

When we try to populate the relational fields on the user-permissions => users model, the response doesn't populate the relational fields.

Steps to reproduce the behavior

1. Create a user in the Users-Permissions
2. Create some other collection type and link it with user
3. Enable public find permission on both
4. Send a GET request to the /users with "?populate=*"
5. Response won't contain the relational field

Expected behavior

Appending ?populate=* to the API request to the user-permissions => users model, the response should contain the relational fields.

System

• Node.js version: 14.15.3
• NPM version: 6.14.9
• Strapi version: 4.0.0
• Database: MariaDB
• Operating system: MacOS

Additional context

PR #11795 is about fixing filtering on the same User-permissions => users model. I have also added that new code changes to my project. Filtering does work, but the population doesn't.

[creative-ae]

facing same issue

[derrickmehaffy]

This issue has been mentioned on Strapi Community Forum. There might be relevant details there:

https://forum.strapi.io/t/populate-users-permissions-to-get-user-avatar/13701/2

[joh-sch]

We're having the exact same issue with getting user roles. No matter the population parameters, the user role is not in the response.

[Devisione]

to many issues with populate.... mb we can return default mechanism? or how we can help to resolve that problem?

[joh-sch]

to many issues with populate.... mb we can return default mechanism? or how we can help to resolve that problem?

looks like a fix is on the way: Fix unable to populate User in Users-Permissions

[derrickmehaffy]

to many issues with populate.... mb we can return default mechanism? or how we can help to resolve that problem?

No there is no way to return to the v3 format, we expected bugs in the first few releases.

[iicdii]

Temporary workaround to enable populate in /api/users/me and /api/users

// path: src/extensions/users-permissions/strapi-server.js
module.exports = plugin => {
  const sanitizeOutput = (user) => {
    const {
      password, resetPasswordToken, confirmationToken, ...sanitizedUser
    } = user; // be careful, you need to omit other private attributes yourself
    return sanitizedUser;
  };

  plugin.controllers.user.me = async (ctx) => {
    if (!ctx.state.user) {
      return ctx.unauthorized();
    }
    const user = await strapi.entityService.findOne(
      'plugin::users-permissions.user',
      ctx.state.user.id,
      { populate: ['role'] }
    );

    ctx.body = sanitizeOutput(user);
  };

  plugin.controllers.user.find = async (ctx) => {
    const users = await strapi.entityService.findMany(
      'plugin::users-permissions.user',
      { ...ctx.params, populate: ['role'] }
    );

    ctx.body = users.map(user => sanitizeOutput(user));
  };

  return plugin;
};

I forced to populate role in example but you can edit it with your own.

[kevinvugts]

Adding a connecting an image to a users-permissions "user" model after creation also doesn't seem to work fokes.

After creating a user account and trying to upload the image to strapi and connect it to the users object only the upload seems to work. The coupling between upload and model is not happening for some reason.

update: mentioned in here for anyone who is looking for an active #11919

       data.append("files", {
          uri: image,
          name: filename,
          type: `image/${filename.split(".").pop()}`,
        });
        data.append("ref", "user");
        data.append("refId", response.data.user.id);
        data.append("field", "profilePicture");
        data.append("source", "users-permissions");