When the content type has translatability enabled BUT none of the fields are, visiting the translation tab throws: Fatal error: Call to undefined function _field_ui_bundle_admin_path() in [....]/core/modules/translation_entity/translation_entity.pages.inc on line 116 When enabling at least one field for translation, the error goes away.
The expected result would have been a table with all languages that I could translate the node to with the operations column pointing me to set up at least one field for translatability as I've seen earlier.
Got this error while demoing the entity translation feature to an audience at Drupalcamp Hungary.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | node_field_translation_test-1849316-3.patch | 857 bytes | csg |
| #2 | node_field_translation_test-1849316-2.patch | 1.21 KB | csg |
Comments
Comment #1
csg commentedComment #2
csg commentedThis patch adds a test that checks if the Translate page of a translatable node type without any translatable fields is rendered correctly.
Comment #3
csg commentedAnd this is the fix for the issue.
Comment #5
swentel commentedRelated to #1824244: Tests for: Turn _field_ui_bundle_admin_path() into a public function (field_ui_bundle_admin_path())
- edit - the fix has been committed but catch wants some tests for that function.
So either close this one or the other, it's the same for me.
Comment #6
csg commentedLet's continue at #1824244: Tests for: Turn _field_ui_bundle_admin_path() into a public function (field_ui_bundle_admin_path()).