- 🇮🇳India sanket1007
Couldn't apply the patch #14 in latest Drupal version 10.3.1
- 🇷🇴Romania Kosa Ilma
I can confirm @sanket1007
I have tried on Drupal core 10.3.1 and it is working without the addition of the patch. - First commit to issue fork.
- 🇺🇸United States charginghawk
Unable to test 10.3 right now, but it seems like the outdated option should still be unavailable since the logic hiding it is still there:
https://git.drupalcode.org/project/drupal/-/blob/11.0.4/core/modules/con...
In any case that code should be removed. Also, we should have steps to reproduce.
Additionally, as a commenter noted, "Why does a new revision need to be created to mark it as outdated?" It doesn't. The condition at the end of markRevisionTranslationsOutdated() should use setSyncing(TRUE) to mark the latest translation affected revision as outdated:
$revision_id = $storage->getLatestTranslationAffectedRevisionId($entity_id, $langcode); if (!$revision_id) { continue; } /** @var \Drupal\Core\Entity\ContentEntityInterface $revision */ $revision = $storage->loadRevision($revision_id); $revision_translation = $revision->getTranslation($langcode); $metadata = $this->manager->getTranslationMetadata($revision_translation); if (!$metadata->isOutdated()) { $metadata->setOutdated(TRUE); $revision_translation->setSyncing(TRUE); $storage->save($revision_translation); }