The confirmation form function for building forms has changed and TranslatableForm needs to include the request object in buildForm. See: #2049569: Delete multiple for nodes is broken
Also, the field handling of the code is not quite correct, and show some errors.
This form is accessible when a field is translatable and has content in it, editing the field settings of the field will show a 'Disable translation' link that redirects to the form.
Attaching a partial patch that includes dawehner code moved from #2049569: Delete multiple for nodes is broken
Comment | File | Size | Author |
---|---|---|---|
#1 | 2050359_translatableform-1.patch | 6 KB | pcambra |
Comments
Comment #1
pcambraHere's the partial patch, need to check with someone more familiar with d8mi before progressing on it.
Comment #2
pcambraTagging
Comment #3
plachThe migration code is going be removed as soon as we are done with the EntityNG refactoring. Not sure it's worth spending time on this.
Comment #4
andypostRelated but not duplicate #2089853-1: TranslatableForm totally broken
Comment #5
andypost#1946462: Convert content_translation_translatable_form() to the new form interface