When creating a new taxonomy term, an error is thrown. The error is thrown when the description text editor is in the WYSIWYG CKEDITOR editor or HTML editor. If the editor is plain text, the error is not thrown.

The error is thrown regardless of whether or not the description is empty.

The following is an example of the error that is thrown when creating a new taxonomy term:

The string taxonomy:term:f90cd0ad-b633-4119-918d-e231a9603d6e:description for textgroup taxonomy is not allowed for translation because of its text format.

Comments

sonofxavier’s picture

Issue summary: View changes
sylus’s picture

Assigned: Unassigned » spotzero
Status: Active » Needs review

I don't this is an actual error just reported as such.

Usually you would solve this by: setting up the text formats allowed for translation on: Configuration > Multilingual settings > Strings

Where you would check the full_html format for i18n.

However we are using Entity Translation and think this warning is moot since we are have fields for each language and don't need an i18n string for it.

Looking at the logic this seemed to confirm my opinion so we should ride an override on this error handling to bypass if using Entity Translation.

Maybe @spotzero can have a look and confirm is the right track for this.

spotzero’s picture

This error comes from trying to run "rich text" through Drupal's localization functions. Since the description on taxonomy terms is an entity propriety, it cannot be translated with entity translation unless it's replaced with a field (like how title field works), so it's localized by the localization functions.

The two options are to either enable localization for "rich text" as Sylus explains above, or to replace the description with a field.

It's likely, that you want to treat the the term description as site content and not translation strings, so you probably are better off replacing the description with a field.

This is configured by default on the "Categories" taxonomy that's configured by Wetkit, however, it does need to be configured on any new taxonomy vocabularies that are created.

To solve this issues, go to "/admin/structure/taxonomy//fields" on your site, and click the "replace" link on the description line. This will replace the description propriety with a field that can be entity translated.

sylus’s picture

Status: Needs review » Fixed

@spotzero is bang on so closing this as confirmed fixes.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.