field_collection integration -- add hook for defining entity's owner

Try update?

I, too, have found that permissions for VIEWING OWN/EDITING OWN field is not working when that field is a subfield of a field collection.

To reproduce this problem, give View Own/Edit Own permissions to the authenticated user for a field collection "mycollection" and its subfield "subfield1" in a content type's "mytype". I've attached a feature with the setup I described above for testing. This feature uses:

• Features module for exporting (7.x-1.0-rc2)
• Field collection module (7.x-1.0-beta4)
• Field Permissions module (7.x-1.0-beta2)
• Drupal core (7.14)

I'm hoping I can move this back into the "needs work" category, since I provided lots more info in comment #3.

I got a similiar problem. I use the module to restrict access to files that users uploaded. I gave the role author the field permissions to create and view own value for such a field of the collection as "Manuscript", but NOT edit own field for that field. But the author can still edit it like removing it or uploading a new one.

Can anyone please tell me how to fix this? Thanks!

It looks like the major issue here is with function _field_permissions_entity_is_owned_by_account(). It's looking for each entity to have a uid property. Here's the code within the function:

  // Try to get the uid of the entity owner from the entity itself. If it's not
  // set (for example, if the entity type does not store a uid or does not have
  // a concept of "ownership"), we need to assume that the provided user
  // account does not own it.

However, with field collections, there IS no defined uid per entity.

What do you think of adding a hook to allow other modules to modify the assigned userid?
hook_field_permissions_userid_ENTITY_TYPE_alter(&$uid, $entity)

Adding this hook could be the first step to getting field collections to work with field permissions.

Patch attached.

Sorry, broke tests. New attempt (with diff between it and #6).

I've been using this solution (in combination with Field Collection) for quite awhile now on a few sites. No problems so far.

Renee S, do you using dev versions of both modules?

@sdudnik, I've been using the main releases with these patches, and have had no issues. More specifically, the module versions I'm using are Field Permissions 7.x-1.0 and Field Collection 7.x-1.0-beta11.

However, @Renee S is absolutely correct in setting the version to 7.x-1.x-dev. New patches should be applied to the -dev branch, not a release of a module.

Yeah just hit this snafu today.
Fortunately, the patches fix it.

#8 above
+
https://www.drupal.org/node/1954124#comment-10626332

Hopefully the field_collections and field_permissions maintainers are on board with the patches.

Now it is I who am the maintainer! Thanks me from the past! And everyone else. :)

Actually, setting this to Patched (to be ported) so the D8 peeps can review it for relevance.

Going to see if I can't get this solved in a way that doesn't rely on https://www.drupal.org/node/1954124.

Pulled this patch into the field permissions module instead:
https://www.drupal.org/node/1954124

So this is going back to the d8 branch for evaluation.

This feature may still have merit in 8.x. Moving back to previous status.