How to configure and connect Beebox to Wordbee Translator

Owned by Former user (Deleted)
Last updated: Dec 03, 2020
3 min read

This article provides useful guidelines for configuring Beebox in such a way that you can benefit from all the features when connecting it to Wordbee Translator.

How to configure Beebox

CMS and regular Beebox projects may consist of:

  1. Source language

  2. One or multiple target languages

  3. One Translation Memory.

They can be connected to a Wordbee Translator project or to a different TMS or CAT tool.

Pass-trough projects do not contain a translation memory because they aim at sending jobs to Wordbee Translator or other TMS in their native format. No file processing is done.

More than one Beebox project can be connected to the same Wordbee Translator project, even when the source language is different.

We recommend you to connect only one Beebox project to the same Wordbee Translator project when you plan to set up separate workflows, vendors, pricing policies, and linguistic databases (resources),

When you configure Beebox, remember to:

  1. Enter the target website in the CMS Connector tab and enable the preview function in the Translation Vendor tab if you are using Live Preview.

  2. Review whether the Preview landing page is still valid.

  3. Link the project to the corresponding Wordbee Translator platform from the Translation Vendor.

Troubleshooting

Click on the expand arrow to view a couple of known issues and how to solve them.

Issue 1: Translation is not delivered.

  • Check if all workflow steps were completed in Wordbee Translator.

  • You or another authorized user might be logged into the Beebox UI. All operations will be on-hold till the user logs out OR till the user clicks Start Auto-run.

  • Check the file/job status in Beebox. If you are using the feature that splits documents into a specific number of segments, it could be that Beebox is still waiting for other parts of the file to be completed before delivering.

Issue 2: Nothing appears in Wordbee Translator.

  • Check whether the file appears in the IN folder. It could be that it was removed.

  • Check if the file appears in the out folder. If all file segments were pre-translated from the memory (this applies for CMS and regular projects, not Pass-through), or if no texts could be extracted (Text extraction rules not configured properly), there should not be any translation required. In this situation, Beebox would create the target language file and would place it instantly into the OUT folder.

  • Check if all workflow steps were completed in Wordbee Translator.

  • You or another authorized user might be logged into the Beebox UI. All operations will be on-hold till the user logs out OR till the user clicks Start Auto-run.

  • Check the file/job status in Beebox. If you are using the feature that splits documents into a specific number of segments, it could be that Beebox is still waiting for other parts of the file to be completed before delivering.

Issue 3: An error message warns you that the source file is invalid.

  • The file might be corrupted, or you have added instructions file with an erroneous language locale or date. Please make sure your language locales are matching the Beebox project language codes!

Issue 4: Beebox is busy.

  • The behaviour is normal when you have requested a translation request in the last seconds or minutes, or if you are processing a high number of files. In this case, it is best to wait until the operation has been completed.

  • The login page will display the Project and file(s) which is preventing you from accessing the Beebox UI. If the operation takes longer than usual, try to move the Beebox configuration folders to a different place. This will enable you to access the Beebox UI. If it turns out that the file is neither corrupted nor invalid, you can move back the folders to the initial location.

Learn more

 

 

Copyright Wordbee - Buzzin' Outside the Box since 2008