Transcribe Documentation

Dynamic Field Replacement

Legacy EE2 feature: Automatic field replacement was available in Transcribe 1.x for ExpressionEngine 2. It is not implemented in the EE3+ version of Transcribe.

The legacy implementation used a double underscore followed by language abbreviations separated by single underscores. For example, a field named blog_body__he_ar supplied the value of {blog_body} when Hebrew (he) or Arabic (ar) was active.

On EE3+, creating blog_body__he_ar does not change the output of {blog_body}. Use language-assigned channel entries, or explicitly select the appropriate field in your template.

Support

Having problems setting up and/or using Transcribe? Support is offered from 10am to 4pm EST weekdays. Send us an email at help@eeharbor.com and we will respond as quickly as we can.