I see that title_field_attach_form() inherits any existing #access before setting the legacy field access to FALSE. For some reason I was having an issue with one of my content types not displaying the new field. I ended up adding some dpm's in and saw that in this case title_field_attach_form() was being called twice. I'm using the FAQ and FAQ Ask modules, and replaced the title field for the FAQ content type, so I think there is something one of those modules is doing to have hook_field_attach_form() called again, but it would be nice if #field_replacement was TRUE not to inherit the #access, which is now FALSE.

Comments

jojonaloha’s picture

Status: Active » Needs review
StatusFileSize
new1.21 KB

The attached patch checks to make sure #field_replacement is not TRUE before inheriting the #access.

pol’s picture

Status: Needs review » Reviewed & tested by the community

hi,

This patch makes sense, thanks !

alex_optim’s picture

+1

  • Pol committed ba1bd71 on 7.x-1.x authored by jojonaloha
    Issue #2206257 by jojonaloha: Replacement field access being set to...
pol’s picture

Status: Reviewed & tested by the community » Fixed

Thanks!

Status: Fixed » Closed (fixed)

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