it seems like this is almost certainly a doing-it-wrong problem.
Although Meta Box is listed as compatible, there is no documentation on wpml.org or metabox.io about using WPML with post types registered with Meta Box.
What jumped out at me when I installed a copy of the site was that in the sidebar we have both a Tours and a Ture post type available.
Not the posts, but the post types.
So if you disable WPML and return to the same page you will see that each post type is registered 4 times, and one of the times that the Tours post type is registered it is registered with a slug of ture.
I am 99% certain that doing this is wrong (you certainly wouldn't do this with any other tool such as CPT UI).
Go to WPML > Settings > Post Types Translation and you will see that the Meta Box internal post type (used to store details about the post types being registered) mb-post-type is set as translatable, as we as the custom post types (such as Tours) being marked as translatable. (But not the "ture" post type.)
The mb-post-type post type should almost certainly be set as not translatable, which will eliminate the duplicate post type registrations, including that of the "ture" post type, which I would expect to resolve problems with post type slugs.
You second tier support mentioned "Ture" as additional post type which exist with the original post "Tours".
That post type is not what I have created. This is what you have created or your support team. Please, look at the my screenshot (I restored my backup meanwhile) - there is no post type "Ture". It's just "Tours". Somebody also changed some other elements, so that's why I was a bit angry, and realized I will have to bring back my backup (backup restore).
I mean, it won't be the problem if you (or anybody else) bring back the original situation, and not leave those changes active - because we can see now, those changes lead to wrong conclusion.
So, once again - there is no another post type "Ture". There is just "Tours" (check my screenshot). Please, ignore that post type - it doesn't exist on my Site anymore, it something you or your support colleges created and now that same thing is confusing you.
That is strange as I certainly did not add any custom post type like that.
For now, Is it possible to provide us with the version that does not have the Tue post type to avoid any confusion and give us the login so we can create a dump of the file?
- Logged in.
- Installed Duplicator
- Took a backup without uploads folder
- Downloaded the file
- Deleted the backup file of Duplicator
- Deleted the duplicator plugin
I'd appreciate it if you could deactivate the login you shared with us.
The second tier support is asking before downloading the zip file. Did you follow the step mentioned in the previous reply to make "mb-post-type" not translatable and you confirm that the issue is still there after that change?
The mb-post-type post type should almost certainly be set as not translatable, which will eliminate the duplicate post type registrations, including that of the "ture" post type, which I would expect to resolve problems with post type slugs.
Hello Christopher, I have the same issue MB AIO + Bricks + WPML.
mb-post-type is set to "Not translatable" and then my CPT "Knowledge Base" have different slugs set inside WPML > Settings > Post Type's Translation.
So when I view a KB entrie that is translated, when I switch to another language the slug contains the code language and then the translated slug of my CPT.
But what about the archive page? Where can I change the custom archive slug that I provided inside MB AIO?
As I mentioned earlier, somebody registered that additional post type - Ture - and I deleted it afterward. There is no more "Ture".
However, mb-post-type is still set as translatable, so this is not related to the additional post type "Ture".
I can switch mb-post-type to non-translatable, but the main question is - what will happen to my content after that? I have a bunch of posts in every post type I have created. All those posts are published in 4 languages, each with many categories (taxonomy).
So, what will happen with all of that if I set mb-post-type to non-translatable?
I won't certainly do that if I can't be sure everything will be fine. I believe - you, or second-tier support know exactly what will happen. PLease, send me the feedback.
I managed to find kind of solution for my problem with an additional plugin, so I am closing this ticket.
Best regards
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
