Content-selection reference

Use Settings → POM Translate → Content types to define the WordPress content that POM Translate parses after a source save. Administrators and editors can access this settings area.

Post types shown

The Post types available for translation section includes post types that expose a WordPress editing interface. Posts and Pages appear first; the remaining eligible types are sorted by their displayed name. Menu items are intentionally absent because POM Translate handles them through its menu integration.

Post type Initial state Can the whole type be disabled here?
Posts (post) Enabled Yes
Pages (page) Always enabled No
Other visible types Disabled Yes

For every listed type, the interface provides four subordinate controls. Title, Content, Excerpt, and Meta are initially enabled when no stored choice exists. A developer integration may alter the defaults or make additional types mandatory.

Taxonomies shown

The Taxonomies available for translation section lists taxonomies with a WordPress editing interface, except for the two permanent defaults:

  • Categories (category) are always parsed.
  • Tags (post_tag) are always parsed.
  • Every other listed taxonomy has Enable translations for this taxonomy and starts disabled.

The taxonomy switch is all-or-nothing for source text: an enabled term contributes its name and its description when the description is not empty. There are no separate name and description checkboxes.

When collection occurs

POM Translate reacts when an eligible object is saved. For posts, pages, and custom post types, normal published and private source objects qualify by default. Revisions and autosaves are skipped. Moving an object to an ineligible status removes that object's translation strings; simply disabling its post type is different and does not perform that cleanup.

For terms, saving an enabled taxonomy parses the current term. The plugin also initializes the term slug for each configured language, but slug editing remains a URL workflow.

What this screen does not select

These surfaces have independent controls:

  • translated post and term slugs: Translations → Translate URLs;
  • menu labels and custom menu links: menu and URL workflows;
  • theme, plugin, and WordPress gettext strings: Translations → Software translations;
  • values registered through the public string API: their registration contract;
  • individual object exclusions: Translations → Translation exclusions.

After any selection change, save one representative source object and confirm its expected rows in Translations → Translate contents before applying the policy broadly.