Thanks for the nifty module.
I'm not entirely sure this is expected behaviour but currently when we visit a user edit page for a user without permission to see X field we still see the markup around X field even though the contents are not there.
See the attached image as an example. The Twitter text field input is removed but the markup of the typical field markup remains.
Is this expected behaviour or do you think we have something interfering with the rendering of these fields like the theme?
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | multiple_registration_markup_remains_2908303-8.patch | 1.31 KB | ysamoylenko |
| Screen Shot 2017-09-12 at 11.00.59 AM.png | 30.29 KB | pribeh |
Comments
Comment #2
pribeh commentedComment #3
sillo commentedAny plans on fixing this? I see this issue was created about a year ago, and no replies so far.
Comment #4
ysamoylenko commentedComment #5
rodman1980 commentedComment #6
ysamoylenko commentedComment #7
ysamoylenko commentedHello, I've investigated the problem.
It is related to the core 'field' module logic (field_access hook), it restores the field wrapper to the page.
I've implemented the patch for solving the problem but it needs to be tested.
Please try to apply it.
Comment #8
ysamoylenko commentedI've updated the patch. (Removed extra whitespace)
Comment #9
IreneV commentedReviewed & tested. Looks good!
Comment #11
ysamoylenko commentedThe patch was committed. Thank you for the report and review.