- πΊπΈUnited States smustgrave
Thank you for creating this issue to improve Drupal.
We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.
Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.
Thanks!
- Status changed to Closed: outdated
4 months ago 3:09am 1 April 2025 - π¦πΊAustralia acbramley
I've looked at the code (now lives in NodeGrantDatabaseStorage::write) and I can't see how it would "blow up". Given the age of this issue and lack of activity I'm going to close it for now.
- Assigned to xjm
- Status changed to Active
21 days ago 2:26am 6 July 2025 - πΊπΈUnited States xjm
The code is still essentially the same, so I should probably try to determine what I was talking about in my review of [#7173848-187]. The problem that I believe I was talking about was the following codepath:
if (isset($grant['langcode'])) { $grant_languages = array($grant['langcode'] => language_load($grant['langcode'])); }
...in the scenario where the Language module or the language in question was not available.
language_load()
not defined β‘οΈ fatal. This potential problem goes away with post-release Drupal 8 now that the language manager is always available.Language not currently available on site β‘οΈ an array
[$langcode => NULL]
. Then the foreach would set it to a null langcode. That's the part I was asking for test coverage for, because this could potentially cause strange things for site owner expectations if a language is disabled and then re-enabled, for exampled. - πΊπΈUnited States xjm
Was going to assign it to myself to explain later but then ended up explaining it now.