![]() This does not make a big difference currently when just using regular untranslatable fields as they are not visible on the edit form. Right now, using the createRevision() API to prepare a new revision uses the untranslatable fields of the current default revision. ![]() See #2833049-14: ContentEntityBase::hasTranslationChanges will compare a forward revision with the default one instead of the newest forward revision.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |