I’m double checking just to make sure, but I’m suspecting that the Must not exceed 20 characters and may only contain lowercase alphanumeric characters, dashes, and underscores detail would be enforced even if we weren’t also aiding enforcing with javascript.
The rewrite spots sound like they have you MOSTLY covered and the public facing parts are as expected/needed, it’s just the post type key that is probably expected to be in latin.
Would be curious if things went differently with use of the “Get Code” tab for this post type, and temporarily manually registering a post type key using Arabic characters. You can find that tab at https://mlotfycarrental.com/wp-admin/admin.php?page=cptui_tools&action=get_code and it can be pasted into your theme’s functions.php file.
I pasted this in the functions.php and nothing happened
function cptui_register_my_cpts_عربيه() {
/**
* Post Type: عربيه.
*/
$labels = [
"name" => esc_html__( "عربيه", "woodmart" ),
"singular_name" => esc_html__( "عربيه", "woodmart" ),
];
$args = [
"label" => esc_html__( "عربيه", "woodmart" ),
"labels" => $labels,
"description" => "",
"public" => true,
"publicly_queryable" => true,
"show_ui" => true,
"show_in_rest" => true,
"rest_base" => "",
"rest_controller_class" => "WP_REST_Posts_Controller",
"rest_namespace" => "wp/v2",
"has_archive" => "عربيه",
"show_in_menu" => true,
"show_in_nav_menus" => true,
"delete_with_user" => false,
"exclude_from_search" => false,
"capability_type" => "post",
"map_meta_cap" => true,
"hierarchical" => false,
"can_export" => false,
"rewrite" => [ "slug" => "عربيه", "with_front" => true ],
"query_var" => true,
"menu_icon" => "dashicons-car",
"supports" => false,
"show_in_graphql" => false,
];
register_post_type( "عربيه", $args );
}
add_action( 'init', 'cptui_register_my_cpts_عربيه' );
If nothing happened, then i assume that first listed “Post Type Slug” is going to have to be in latin characters rather than Arabic.
Hello @tw2113 I wonder if I can create a CPT UI under a specific language? lets assume I have /ar by Polylang how can I create a CPT UI that’s ar based? because now CPT creates general tab and then from inside it you choose the article language which makes the CPT archive link loyalty to the main domain and not the subdirectory of that language. So, is there a possibility for the CPT to be under a specific language so the archival link of it really works? as when its under the main domain the archive link will always be empty because the posts or pages is already assigned to a language that needs a /AR after the .com but the archival link remains .com/archive because the CPT itself doesn’t understand that this archival is for a specific language. Also, that makes an issue in the sitemap as it displays the empty archival link and not the correct one that should have the /ar/ after the .com then the archival slug. For now I’m solving it temporarily by cloudflare 301 redirect. Is there a real solution for this?
I believe in general you can register the post type in whatever default language you want, it’s just that this field specifically needs to be in latin:
Labels can be in whatever language, and permalink slugs are meant to be translation ready.
We try to do our best for PolyLang/WPML/etc support, but I know we also store label data, etc, as part of saved options making them a little bit hard to get to for those other plugins.
In terms of content created in the post types and taxonomies registered, those should be fully accessible from the translation plugins.
Have you reached out to PolyLang support for some of these questions? We’re more than willing to help think through how to try and achieve what you’re needing, but I’m not 100% sure which plugin would be in charge of which parts.
Ultimately the primary purpose of CPTUI is to collect the arguments that get passed to register_post_type() and register_taxonomy().
Any news or changes here @weboosteg ?
if you are talking about the translation well, the solution is there in paid versions (confirmed) so the issue isn’t in your or their side its only on client side if he don’t want to pay.
also for the speed issue not sure if I mentioned here its not related to you or translation plugins it was a wrong caching setup.
so in short, both issues is on the client side whether a setup or getting pro sub
thanks for asking all good now
Thanks for the followup, and let us know if you need anything else.
