Get i18n_field submodule working

backdrop-contrib / i18n

Collection of modules to extend Backdrop CMS multilingual capabilities

https://backdropcms.org/project/i18n

GNU General Public License v2.0

2 stars 5 forks source link

Get i18n_field submodule working #11

Closed indigoxela closed 4 years ago

indigoxela commented 4 years ago

Maybe not the most important, but after all an easy to port submodule.

i18n_field (Field translation) provides translation for field properties like labels and help text.

indigoxela commented 4 years ago

A PR is available.

How to test:

Enable this submodule with its dependencies.
Add custom field(s) to a content type via field UI
Go to admin/structure/types/manage/YOURTYPE/fields/YOURFIELD/translate and translate properties
Add new content of YOURTYPE in the language you translated properties to and verify that translations (like labels) are there
Inspect dblog for any errors

... and report any problems here. (Make sure not to have metatag module enabled, which currently has a bug with i18n_string.)

indigoxela commented 4 years ago

~~This submodule still causes a php error:~~

Error: Class 'i18n_field_instance' not found in i18n_get_object() (line 456 of .../modules/i18n/i18n.module).

UPDATE: no, everything's OK. I switched between branches and forgot to disable the module not fixed in that branch. That's why errors appeared. (Problem existed between desktop and chair :rofl: )

indigoxela commented 4 years ago

How to test: follow the instruction from my previous comment.

One option is to apply the PR patch to your local clone of i18n dev.

Another option is to clone the indigoxela i18n fork: https://github.com/indigoxela/i18n/tree/i18n-field and checkout the i18n-field branch.

Be aware to always disable (uninstall) the submodules not fixed in that branch. To be on the safe side, you better uninstall all i18n modules and start fresh after cloning / switching branches.