Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Simple find/replace fix.
Comment | File | Size | Author |
---|---|---|---|
#1 | language_none-1232836-1.patch | 7.43 KB | twistor |
Comments
Comment #1
twistor CreditAttribution: twistor commented... and the code.
Comment #2
emackn CreditAttribution: emackn commentedhmm.. is LANGUAGE_NONE the right thing to use? Shouldn't we use $entity->language instead?
Comment #3
franzI think we need to push it into major to get more attention. I'm a little ignorant of i18n implementations, but I feel we need to properly comply with it. Does $entity->language stores LANGUAGE_NONE by default as well or is it empty?
Comment #4
franzComment #5
franzemackn, I read a little, and it looks like $entity->language is not necessarily the field language, so it would be better to use LANGUAGE_NONE than that.
However, if we wish to implement better support, we should read it here.
Comment #6
franzI think we're also affected by #1495648: Introduce entity language support and #1376126: Fix language handling for translatable fields
Comment #7
twistor CreditAttribution: twistor as a volunteer commentedWe're fixing this in other issues.