Enable translation for a post type
Enable a post type when its individual objects contain visitor-facing language that should change with the selected locale. Typical examples include portfolios, events, products, or another custom type supplied by a theme or plugin.
Before you begin
The post type must provide a WordPress editing interface to appear under Content types. Decide which of its values are actual prose. Technical identifiers, prices, booleans, relationship IDs, and machine-readable configuration should not become translation rows.
Enable and populate the surface
- Open Settings → POM Translate → Content types.
- Find the post type under Post types available for translation. Its displayed name includes the post-type slug in parentheses.
- Select Enable translations for this post type.
- Select the required Title, Content, Excerpt, and Meta parts.
- Save the settings.
- Open one representative object of that type.
- Ensure it is published or private, then save it.
- Open Translations → Translate contents and filter to that object.
The setting changes what later saves parse; it does not launch a bulk scan of existing objects. Existing published items must be saved individually or processed by an appropriate maintenance workflow.
Choose the parts deliberately
- Enable Title when the object name is shown to visitors.
- Enable Content for the main editor or structured builder content supported by POM Translate.
- Enable Excerpt only when the post type uses its excerpt publicly.
- Enable Meta only when the theme or plugin has registered text-valued metadata keys.
Selecting Meta does not expose all database metadata. It opens the gate only for approved keys.
Expected result
After saving the source object, the selected non-empty values appear as editable rows for each additional language. POM Translate also initializes the object's language slugs from the source slug when localized slugs do not yet exist.
If nothing appears, confirm that:
- at least one additional language is configured;
- the object is not a revision or autosave;
- its status is eligible;
- the post type remains checked after reloading the settings page;
- the relevant part is enabled;
- metadata uses a registered key and has a non-empty scalar value.
Continue with Choose post title, content, excerpt, and meta or Translate custom post types.