In most cases, working with the In-Context Editor requires a dedicated translation environment. There are two ways you can set up your environment.
The In-Context Editor is available when you choose the Pro plan or a higher plan. Working with it usually requires a dedicated translation environment. You can set up your environment in either of two ways.
Use a dedicated environment for translations only (recommended)
You can clone one of your staging environments to use it as a dedicated translation environment. In this environment, the In-Context Editor is always enabled. Translators can always browse the site as needed in order to translate all the new features you plan to release. This option requires some initial work to set up, but it leads to a better workflow and experience for your translators.
Use an existing environment with a feature switch
The phraseapp-in-context-editor-ruby gem stores settings on the current thread. This can cause unexpected behavior when working with multiple users in the staging environment.
If you don’t want to set up a dedicated In-Context Editor environment, you can use an existing staging environment and add an option to enable and disable the In-Context Editor as needed.
When using the phraseapp-in-context-editor-ruby gem in a Rails application, you might add that option like this:
PhraseApp::InContextEditor.with_config(enabled: params[:translate] == "1") do