Filter post-type translation configuration

Available filters:

  • pom_translate_default_enabled_post_types( array $post_types );
  • pom_translate_always_enabled_post_types( array $post_types );
  • pom_translate_enabled_post_types( array $post_types );
  • pom_translate_post_type_translation_part_defaults( array $defaults, string $post_type );
  • pom_translate_is_post_type_translation_part_enabled( bool $enabled, string $post_type, string $part );
  • pom_translate_subject_search_post_types( array $post_types );
  • pom_translate_translation_storage_post_statuses( array $statuses, object $post ).

Defaults seed configuration; always-enabled values cannot be disabled through normal settings; the final filters affect runtime decisions.

pom_form is excluded from optional post-type translation even if a stored setting or enabled-post-types filter includes it. POM Forms owns its structured registered strings and shares one form across languages.

The subject-search filter controls which post types appear in the Translation Manager autocomplete. It does not enable extraction for those types.

Translation storage accepts publish and private posts by default. Extend that status list only when the integration has a deliberate editorial workflow for incomplete content; adding a status can create translation records while a post is still changing.

Return valid registered post-type slugs, sanitized status names, and booleans. Do not enable private or technical types without confirming their stored fields contain public translatable content.

Hide the current language
Previous
Respect the import and export boundary
Next