| EventCode | Context | EventMessage | Description / Solution |
|---|
| Plug-In Okapi | Okapi Plug-In: Bconf not given or not found: {bconfFile} | Either there was no bconf given, or the default bconf could not be found.
Default for import should be: ./application/modules/editor/Plugins/Okapi/data/okapi_default_import.bconf
Default for export should be: ./application/modules/editor/Plugins/Okapi/data/okapi_default_export.bconf |
| Plug-In Okapi | Okapi Plug-In: tikal fallback can not be used, workfile does not contain the XLF suffix: {workfile} | In seldom scenarios tikal is used for export, if tikal receives an non XLIFF file this error is thrown. |
| Plug-In Okapi | Okapi Plug-In: Data dir not writeable: {okapiDataDir} | Solution: change filesystem rights so that the apache user can write into
./application/modules/editor/Plugins/Okapi/data |
| Plug-In Okapi | Okapi Plug-In: Error in converting file {file}. See log details for more information. | An error described in message happend on converting the file.
Check the message, since the error could be independent from the given file, for example if some Okapi configuration was wrong, or the Okapi server is not available.
A full log of the happened exception is available in the log (level debug). |
| Plug-In Okapi | Okapi Plug-In: Configuration error - no Okapi server URL is configured! | Set a correct Okapi server URL in the configuration: |
| Plug-In Okapi | Okapi Plug-In: The exported XLIFF contains empty targets, the Okapi process will probably fail then. | If the Okapi export failed investigate the XLIFF to find out the empty segments and why they are empty. |