Documentation

Security and limitations

Security

  • The license key can stay out of the database, in wp-config.php (see License, plans and updates).
  • The panel always shows the key masked.
  • Only administrators (manage_options) can access the panel and recording mode.
  • The dictionaries are PHP files inside uploads/. The plugin creates a protective index.php and .htaccess there, but on servers that run PHP inside uploads/ that is not enough (on Nginx the .htaccess has no effect). If your host allows it, block PHP execution in that folder.

Known limitations

  • URL slugs are not translated. Only the prefix changes — a deliberate choice, explained in Why the slug is not translated.
  • Emails not tied to an order may go out in the store’s language. An email to the customer that is not linked to an order has nowhere to inherit the language from. (Order emails go out in the language of the purchase — see WooCommerce.)
  • One sentence, one translation, across the whole site. The Where column helps give context to whoever reviews.
  • It does not translate inside <script>. That includes SEO plugins’ JSON-LD structured data.

Publish.
Read it in
every language.

30,000 characters, one site, no card. The key arrives by email after checkout.