Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Permissions on a couple of fields on my site were misbehaving (being switched around and such). I was able to resolve this, but while poking around, I found that previously deleted fields had left some permissions behind (see attached).
Sets of permissions from two deleted fields remain.
Comment | File | Size | Author |
---|---|---|---|
People _ Permissions _ orphaned.png | 68.88 KB | matt.rad |
Comments
Comment #1
shaisamuel CreditAttribution: shaisamuel commentedThis is an amazing module, with essential functionality that should make it to core, together with "Content Access". I see there are active major issues from even 2 years. Hope they will get cleared shortly. I wish I could code, but not yet.
This is a major issue since it leaves a mess in the DB. It is definitely a code error, since the functionality for handling a call from field module, of a field about to be deleted should be in place.
Comment #2
apmsooner CreditAttribution: apmsooner commentedI finally tracked an issue i was having down to this one. Because field settings are cached and the permissions aren't deleted, when i copied database down to the test environment on pantheon, i was getting errors for table not being found for the deleted fields. I resolved this by manually deleting the rows related to the deleted field referenced in the role_permissions table.
Comment #4
mariacha1 CreditAttribution: mariacha1 at ThinkShout commentedShould be fixed now via a field_permissions_field_delete_field($field) hook implementation.