[MatrixFourParticipant]

Or is translating that prefix not possible as Rad said?

From Rad….
Hi there,

The format should be like this

http://vicwest.staging.wpengine.com/fr/our-portfolio-category/agricole-portefeuille/

WPML translation is only applicable for category slug (eg. /agricole-portefeuille/ ), and not to prefix slug ( eg. /our-portfolio-category/)

You can view your category URLs in Admin > Portfolio > Categories.

Thanks!

—-

I want to know please before I start posting support requests on WPML. You guys are compatible with each other so not sure why you can’t give any advise on this.

Please let me know. If we did want to translate the prefix and not the category slug, would that need to be customized?

Looking forward to your reply.
Mike

[RadModerator]

Hi there,

It’s not, and according to you

The single portfolio page seems to work fine with the translations, but the category pages do not link to the proper pages when you switch the language. But the pages exist and work properly, it just seems like there are some linking conflicts.

It works on the single post that’s because the important part of the POST as its identity is its own post name as the slug ( regardless of slug prefix ). Even if you just type “hello” on the slug, it will redirect you to the post where slug matches “hello” and it will work.

While taxonomies (eg. portfolio category) depends on two part of a slug, the category name and the prefix that identify them as the category ( eg. /portfolio-category/category-name/ ).

This is the format of taxonomy and term

/taxonomy-name-that-indicates-to-where-the-term-belongs/this-is-the-term-and-its-translatable/

And these are the samples

/tags/awesome/
/categories/movies/
/portfolio-categories/art/

Now imagine changing the taxonomy (tags) name, that means the term (awesome) now belongs to different taxonomy and it will return 404.

I’m not saying it’s impossible, but you may contact a developer to implement this. Working with permalinks is a bit tricky. You have to tell the system that both different SLUG name is just the same taxonomy name for it to work.

Thanks.

[MatrixFourParticipant]

Hi Rad,

I assumed that WPML would be able to control taxonomy translations which I think it WPML does.

I have started a support request on WPML about the issue.
https://wpml.org/forums/topic/x-themes-from-themeco-portfolio-language-switch-issue/

So moving forward to do you suggest not to translated the prefix slug and leave it the same for english and my second language?

[RadModerator]

Hi there,

In your preferred setup, I think you should translate them but that’s something we can’t really help. And yes, contacting WPML is a good idea.

I read your provided URL, and this is his update

Update.
I could catch now our third tier supporter and ask him about it; he says that it is not possible to translate the category name itself or its slug because of limitation from WordPress.
Please see this reply from George our their tied on this issue in another ticket.
https://wpml.org/forums/topic/is-is-possible-to-translate-custom-taxonomy-slug/#post-1036552

It’s true that taxonomy term is translatable, but it’s not the term you’re translating. But the slug prefix that identify the term.

Thanks!

[MatrixFourParticipant]

Hi Rad,

Thank you for the update. I guess I will have to leave the Prefix untranslated at this stage.

Have a good day

[RahulModerator]

Let us know if we can help with anything else. 🙂

[MatrixFourParticipant]

Thanks Rahul. Ill let you know.

[ChristopherModerator]

You’re welcome.

[Author]

Posts