Added a not on the inability to change account information on affected accounts unless the mail address is updated (if possible).
I've added ptmkenny as comaintainer.
I've also granted you rlhawk the right to add and remove maintainers. Perhaps I could transfer the entire project to you (not sure how though) ?
Patches appear to shuffle exceptions. In what way do they "fix" the original report?
invokeAllWith invokes a callable. See https://www.drupal.org/node/3000490 → . Patch updated.
I see a third option; to document using overridden config.
This bug happens when other delete hooks run while cer_entity_delete is in flight, for instance when deleting certain referenced items on hook_entity_delete that have a cer controlled field.
This causes \Drupal\cer\Entity\CorrespondingReference::synchronizeCorrespondingFields() to run with a list of entities that are in the loader cache, but no longer exist. EntityStorageBase won't be able to load the original anymore, causing $entity->original to be empty, triggering the exception.
I found that calling the following and checking for non-null during the inner loop in \Drupal\cer\Entity\CorrespondingReference::synchronizeCorrespondingFields() fixes the issue for that particular site.
$original = $this->entityTypeManager()
->getStorage($correspondingEntity->getEntityTypeId())
->loadUnchanged($correspondingEntity->id());
if ($original) {
$this->synchronizeCorrespondingField($entity, $correspondingEntity, $correspondingField, $operation);
}
Luke.Leber → credited Heine → .
The lack of a functioning release is blocking upgrades to Drupal 10.
Changing function signatures is a breaking change for classes that are considered API.
Could you please publish a release?
Not having an overlapping D9/D10 release means that users upgrading with the help of upgrade_status are not able to get a "green" board on D9. They have to track these updates manually.
Heine → created an issue. See original summary → .
Could you please move inability to exclude extensions to a separate issue? Marking this needs work to exclude local CSS/JS assets. We've scheduled time tomorrow to provide a patch.
Is the MR necessary? StageFileProxySubscriber could exclude paths already when initializing the AlterExcludedPathsEvent.
This happens on both Drupal 9 and 10. Not sure about the proposed fix as this would still proxy .css.gz and .js.gz assets.
IMO SFP should not proxy anything for assets (D10) or anything in public://css and public://js (D9).
I believe this is a duplicate of 🐛 Stage file proxy attempts to fetch aggregated JS/CSS. Fixed . SFP should IMO not proxy js and css.
Thank you for the offer. We've decided to decline it.
Thank you. I've added the release and checked that it is published.