Plugin Author
Chouby
(@chouby)
Hi!
You should have a checkbox in Polylang settings to disable the translation management for your post type. If not, it may be because your plugin/theme creating portfolio chose to make this post type translatable by default (for example in a wpml-config.xml file).
However, you will have a problem. If you already created some content before unchecking this option, the language information will be kept and thus, your content will still be visible in only one language. Only newly created content will have no language associated.
Thread Starter
pebeh
(@pebeh)
Hi Chouby,
thanks for your fast reply. You were right, the needed option wasn’t visible because my theme was setting it in the wpml-config file. However, I now removed the part of the xml file which was causing this and can now see the needed options. They are not ticked anymore and in the portfolio list I don’t see any translations anymore.
Yet the new item I created afterwards doesn’t seem to be language independent. If I open it it is missing the language paramenter in the URL – but I still get redirected to the homepage if I select another language with the language switcher.
Is this the intended behaviour?
Thanks again
Plugin Author
Chouby
(@chouby)
Yes and no…
Yes… since the post is not translatable, there is no translation. The default behavior is then to link to the home page. There is an option not to to display the language switcher when there is no translation.
No… Because we could expect to load the same content with the theme loaded in a different language. There are however drawbacks:
1. This cannot work for user setting the language from the content.
2. Search engines may not like the duplicate content.
If you want to implement this for you, there is the filter ‘pll_translation_url’