I checked for the issue and looks like a page named "Referencie" is having the slug which is being served as this custom post type's taxonomy base-slug at hidden link (see attached).
If you change the slug of this page to match the category's slug (kategoria-referencie), then it 'll load fine at hidden link. Same is the case with the translations of this taxonomy. Please follow these steps:
- Open the page "Referencie" for editing in default language.
- Edit the slug and use the taxonomy's base slug in default language (i.e. kategoria-referencie).
- Save.
- You can now either update translations and in translation editor search for that slug and correct as per the other language base slug for this taxonomy (i.e. category-references for English and kategorie-referenzen for German) and complete the translations.
- Or, can switch to other languages from top admin bar.
- Click "edit anyway".
- Correct the slug as mentioned above and save.
- Finally resave the permalinks.
Why would the Referencie page and it's slug be the problem, when my taxonomy is named differently than the page? I don't want to change the Referencie page slug.
Of course, that's not ideal, but my first suspect is that page is somehow acting as an archive. Although it is clearly a page (post type = page).
I understand your concern and 'll investigate more, but unfortunately this is a live site and I can't do much in there.
Can you provide a staging or test site by copying the live site? So I can then check by deactivating plugins, with only WPML plugins and default theme. This way we can see if issue is really coming from WPML or is any other part of the site is creating a conflict (i.e. a plugin or theme).
I've set your next reply as private to share the staging/test site access safely.
IMPORTANT: If you don't see the section for providing access information, do not write in the message box or the information may appear as public.
Thank you for the access but due to some security restrictions by GeoIP filter I'm unable to reach the WP Admin (although credentials worked fine) - please see attached.
I've also tried connecting via a VPN without any luck.
Please deactivate any security plugins and/or firewalls temporarily and let me know.
I need some time to investigate the issue, however, please note that I'll be off tomorrow for a local holiday and 'll be able to check back on Wednesday and 'll update you accordingly.
Looks like the "Category Ajax Filter Pro" is not compatible with WPML (https://wpml.org/plugin/). I tried to find any existing report in our forums without any luck. We're not sure how this plugin actually works.
Theme and plugin authors are welcome to join WPML’s Go Global program, which helps them make their code multilingual ready. Together with WPML’s compatibility team, they can test and confirm that their theme or plugin works with WPML. See https://wpml.org/documentation/support/go-global-program/ for details and you can refer your theme/plugin provider to this as well.
Hello, is the Category Ajax Filter Pro relevant when I just want to translate the custom post type taxonomy slug? Did you have luck translating it when the plugin was disabled?
Actually why I referred to that plugin because initially you mentioned that:
> The issue can be seen on this page: /en/references/
> I expected to see 'category-references' for the slug, but instead, I got 'kategoria-referencie'.
If I check that page, I don't see any 'kategoria-referencie' for the posts listed on this page, for example one of the post listed there is hidden link, which is referring to the post type's English slug(s).
I then noticed that the said page (/en/references/) is using a shortcode coming from a 3rd party plugin, to list the posts. The posts are still listed fine and using correct slugs in translations (as noted above).
While I tried to reproduce the error on your said page (/en/references/) which isn't possible without that Category Ajax Filter PRO plugin and its shortcode.
So I'll request as I did during our first chat, to record your screen showing the exact problem. And I'll try my best to further investigate it.
P.S.: I'll be off for the weekend and 'll be able to attend on Monday.
