Flag pseudofield doesn't show in display options without a manual cache clear [#2056271]

After setting a flag to output as a pseudofield, a manual cache clear is required. This is due to caching in https://api.drupal.org/api/drupal/modules!field!field.info.class.inc/fun....

Conversely, after removing the pseudofield option from a flag, the pseudofield persists in the entity's display options.

Comment	File	Size	Author
#3	2056271.4.flag_.pseudofield-setting-cache-clear-and-refactor.patch	5.17 KB	joachim
#3
#1	2056271.flag_.pseudofield-setting-cache-clear.patch	1021 bytes	joachim
#1

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

joachim CreditAttribution: joachim commented 2 August 2013 at 08:33

Status:

Active

» Needs review

File	Size
2056271.flag_.pseudofield-setting-cache-clear.patch	1021 bytes

Comment #2

joachim CreditAttribution: joachim commented 2 August 2013 at 08:34

Come to think of it, maybe we should tackle #2056275: refactor _flag_clear_cache() parameters first, and THEN fix this, as the current patch won't fix the problem when importing flags.

Comment #3

joachim CreditAttribution: joachim commented 2 August 2013 at 08:58

File	Size
2056271.4.flag_.pseudofield-setting-cache-clear-and-refactor.patch	5.17 KB

Here's a more dramatic patch which includes the refactoring.

Comment #4

joachim CreditAttribution: joachim commented 21 August 2013 at 07:04

Issue tags:

+3.1 blocker

Tagging as 3.1 blocker.

Comment #5

shabana.navas CreditAttribution: shabana.navas commented 26 August 2013 at 06:27

Status:

Needs review

» Reviewed & tested by the community

I have tested this out. Before the patch, I had to do a manual 'Clear cache' for the field to be removed from my entity type's 'manage display' section. After the patch was applied, the field was automatically removed once I unchecked the 'Display link as a field' option for the flag. So, the patch definitely works and should be committed.