Home›Support›English Support›[Resolved] Translated posts (blog) page of custom taxonomy displays other posts that shouldn't be there
[Resolved] Translated posts (blog) page of custom taxonomy displays other posts that shouldn't be there
This thread is resolved. Here is a description of the problem and solution.
Problem: The client is experiencing an issue where the Dutch archive for their 'destinations' taxonomy incorrectly loads posts from other terms after the initial correct batch. This problem occurs during AJAX pagination and affects archives like /nl/bestemmingen/azie/japan/. Solution: We identified that the theme's AJAX filter might not be compatible with WPML. Our 2nd Tier Support suggests either keeping the 'destination' taxonomy untranslated or deactivating the AJAX pagination plugin as potential solutions. Unfortunately, due to the theme's limited use and lack of compatibility with WPML, further investigation by our support team will not proceed. If deactivating AJAX pagination is a temporary workaround, we recommend contacting the theme developers for a permanent fix, providing them with details of the issue.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Background of the issue:
I am trying to make the Dutch archive for our 'destinations' taxonomy (for example /nl/bestemmingen/azie/japan/) continue to load only the Dutch 'Japan' posts, and never pull in posts from other terms after the first load. The issue can be seen at hidden link. This also happens on /nl/bestemmingen/azie/thailand/.
Symptoms:
After loading the first 10 posts correctly, the next batch is a random mix of posts from other 'destinations' (Bali, Mexico, Australia, etc.).
Questions:
Why are posts from other 'destinations' appearing after the first load?
How can I ensure only Dutch posts from that archive are loaded in the archive?
Sorry for the late reply, I never got an email saying this ticket was created. I have just now installed the theme and its essential plugins on the demo website.
I've setup a minimal version of the website, and the same issue can be found here:
hidden link
or
hidden link
I sometimes see English posts in between Dutch posts (something I don't experience on our site), even though posts are set to non-translatable. When trying to reproduce the issue, I noticed that without using the string translator to translate the custom taxonomy, the issue didn't appear. Only after I translated "Destination", "Destinations" and the slug (to Bestemming, "Bestemmingen" and bestemming) the infinite load issue happens. Thought I'd let you know!
Also, I've used the demo content and created dummy/empty posts to test as setting everything up already took way longer than anticipated. Hope you are able to figure out the issue!
Thanks for your patience. I can see the issue after translating the "Destinations" taxonomy. Please allow me to escalate this to our 2nd Tier Support for further investigation. I will come back to you once I've feedback.
Our 2nd Tier Support couldn't find a workaround here. Also, since the theme is not listed as compatible, they recommend either keeping "destination" untranslated or deactivating the AJAX pagination plugin.
That's disappointing... Not translating "destinations" is obviously not an option, but we'll see if we can disable the AJAX pagination as a (hopefully temporary) workaround. I'll also reach out to the creators of the theme to see if they can fix it. Before I do this, could you tell me what you/2nd tier support are seeing/experiencing and what exactly the issue is? Like what do you think is wrongly implemented in the theme and should be fixed. Then I can provide the makers of the theme with as much technical information as possible, in order for them to fix this. Would be greatly appreciated!
Thank you for your understanding, and I agree that leaving “destinations” untranslated is not a viable option.
Unfortunately, our 2nd Tier Support has opted not to investigate the matter further due to the very limited number of users for this theme, and no technical insights were provided regarding the root cause.
That said, the issue does seem to be linked to how the theme implements AJAX pagination.
