15.1 - Field translations
Version 3.x lets you translate customer-facing field text directly from the field editor. This is the recommended way to translate labels and validation messages.
You can translate items such as:
- field label
- cart/summary label
- required error message
- other field-specific strings when the field type supports them
- Open the calculator.
- Go to Fields.
- Edit the field you want to translate.
- Use the translation controls next to the translatable inputs.
- Save the translations.
These translations are stored with the field and travel with the calculator when you export and import it.
15.2 - Admin interface translations
The modern admin interface ships with bundled language files and follows the active WordPress or user locale automatically.
In practice, this means:
- you do not need to edit PHP language files for the modern admin
- plugin updates keep the official translations managed by the plugin
- if a language is missing or incorrect, it is better to report it than to edit plugin files directly in production
15.3 - Legacy custom translation files
For backward compatibility, legacy file-based frontend translations are still supported through:
/wp-content/uploads/excel-worksheet-price-calculation/translations
Example:
<?php return array( 'height' => 'Height', 'width' => 'Width', );
Use this legacy file-based approach only if you specifically need an older frontend override workflow. For new projects, prefer the translation controls built into the field editor.