Has been discussed here: #1848282: Can't see the link to flag a user & here: #1710522: Wrong ui limit settings on flag fields but as the DS module creator said is a different issue so I'm opening a new one here.

Summary: Flag links are correctly showed on User profiles until a DS template is applied (several test are described on the other post to arrive to this conclusion). DS creator says is not a bug but an unimplemented feature.

Comments

I'm having the same issue.

Yes I need this feature too. The flag integration appears to be for nodes only. It would be good to have this available for all entity types.

Version:7.x-2.0» 7.x-2.x-dev
Status:Active» Needs review
StatusFileSize
new1.14 KB

I think we need to support all entities. I have created a patch which allows the flag field to be enabled on all of them.

StatusFileSize
new1.79 KB

Actually just realised the links were not working correctly. Here is a confirmed working version that should support other entities but needs testing.

Re-roll against latest dev?

I'm not sure this patch is needed now that Flag 3.0 is out. That provides an option to expose flag links as extra fields.

It is still needed, I think, because I'm using display suite to render user profiles, and I can't find a flag link anywhere except in the user's edit form.

Profile are not users, they are another type of entity. So they don't show the user's flags, but the flags on the profiles.

If you want to show user flags on profile entities, then you want a wholly new feature -- similar to the feature request for commerce product flags to show on nodes.

Status:Needs review» Needs work

Really? If I have selected the 'Display link as field' option for my flag, shouldn't I find it on the manage display form for users? Seems logical enough, but maybe I am mistaken.

> If I have selected the 'Display link as field' option for my flag

Is your flag a flag on Users or on Profiles?
If it's a flag on Users, then yes it should. If it doesn't, please file a bug.

If it's a flag on Profiles, then it won't.

It's a flag on users, but I guess this bug has already been reported here https://drupal.org/node/1848282 and here https://drupal.org/node/1849378

EDIT: last issue is actually this one

So, in short, I tried the patch and didn't find anything changed, unfortunately.

Status:Needs work» Active

I'm not sure what the patch is meant to do. At any rate, it's obsolete, since Flags as pseudofields are now part of Flag 3.

What we'd need for this is for a flag on entity A to be available to display on entity B, based on a relationship between A and B. This could be done as a Display Suite field type. You'd get the relationships from Entity API's entity metadata: any property which is a single-valued entity relationship could give you a relationship flag to display.

Issue tags:+flag integration

tagging flag issues

Issue summary:View changes
Status:Active» Postponed (maintainer needs more info)

Ok can someone explain to me what has to be done (or provide a proper patch?) :)

If I understand the last comment correctly we can only do this by relying on entity api?
That is not going to happen, so I hope I'm wrong.

I *think* what is being requested is the ability to show flags for users on user profiles, or flags for user profiles on users.

I think the best way to accomplish this would be a DS field type.

And I think the mose useful and reusable way to do this would be allow chaining through relationships, to get any DS field at the end of the chain.

So, if you wanted to show a user flag (or indeed any user display field) on a node, you'd use the 'author' relationship that Entity API defines on nodes.

This would probably be best tackled in a new contrib module.

Isn't this something flag module can provide in seperate flag_ds module?

I'd rather not have more to maintain in the Flag project!

Furthermore, it could be generic for all fields, and not dependent on Flag.

Same for DS :)
I feel your pain...

I still don't understand what has to be done here...
I'll leave this issue open for now, maybe I get it when I read it a few times in the following weeks :)

As I see it, a new DS field type which lets you chain through relationships.

So, for example, suppose I have a field on users called 'birthdate'.

I create a new 'chained' field called 'node author birthdate'.

I tell this chained field:

- you apply to nodes
- follow the 'author' Entity API property on a node
- on the entity you now have, get the display of the 'birthdate' field

I can then show the birthdate of the node author on each node.

So the OP's request becomes a new chained field with these settings:

- you apply to users
- follow the 'profile_foo' property of the user to get the 'foo' profile for the user
- on the entity you now have, get the display of the 'flag_bar' pseudofield

This could be new contrib module which would obviously depend on DS, and also on Entity API because it would use the relationships defined in Entity API metadata. The fact that flags would work with it would be a mere byproduct of flags being exposed as pseudofields.