In this guide: Fields excluded for safety to avoid breaking design or functionality.
Contents
- Why some fields are excluded
- Fields that are normally not translated
- Clear example
- What to do if you need to translate something special
Why some fields are excluded
Not everything inside Oxygen should be translated. Some data is technical, and changing it may break styles, icons, internal links, forms, or integrations.
The plugin is designed to focus on translatable content and avoid fields that could cause problems.
Fields that are normally not translated
- CSS classes.
- Internal IDs or technical anchors.
- SVG code.
- Internal icon names.
- Technical image metadata.
- Image sizes and variants.
- Tokens, keys, webhooks, or integration data.
- Design settings.
- Internal form values when they are not visible to the user.
- WooCommerce product-specific data.
Clear example
A button text such as “Contact” should be translated. A CSS class used to style the button should not be translated.
A visible accordion title should be translated. An internal identifier used by Oxygen should not be touched.
What to do if you need to translate something special
If there is a specific field that should be translated in your case, contact support. It is better to review it first than to force translations on technical fields and risk the stability of the layout.