Bogo only supports Posts and Pages by default because applying to all CPTs can often cause troubles.
You can use the bogo_localizable_post_types filter to customize it.
add_filter( 'bogo_localizable_post_types', 'custom_bogo_localizable_post_types' );
function custom_bogo_localizable_post_types( $post_types ) {
$post_types[] = 'your_cpt_name';
return $post_types;
}
To detect the current locale, or LTR/RTL, on front end, you can use standard WordPress functions like get_locale() and is_rtl().
I’m writing documentation and will finish it next year.
Thank you very much for getting back to me Takayuki, much apreciated!
When you write the CPT can ofter cause problems – do you mean performance issues? or just because it is better practice to enable the translation per CPT?
Will look forward working with Bogo!
Have a great year,
Dan
Post types are not only used for general document data like Posts and Pages. For example, Contact Form 7 plugin uses the custom wpcf7_contact_form post type to represent its contact form data. WordPress itself uses nav_menu_item post type for menu items. In such cases, you wouldn’t want to apply m17n to the data. Otherwise, you’ll see a lot of unexpected behavior.
