Skip Navigation

[Resolved] Revisiting WPML and intermediary posts issue

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Our next available supporter will start replying to tickets in about 0.21 hours from now. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Hong_Kong (GMT+08:00)

This topic contains 2 replies, has 2 voices.

Last updated by matthewC-9 1 year, 9 months ago.

Assisted by: Luo Yang.

Author
Posts
#2547457

Hi! We have a tricky problem with WPML and a view based on an intermediary content type. Basically, items disappear from the view when we translate the intermediary posts. More detail:
- The site is in English with a Spanish translation.
- There are two content types - online resource, and online resource list - connected by an intermediary content type.
- The intermediary content type includes a list-specific resource description, which we're translating.
- We want to be able to order the resources differently on different lists, so we're using a view based on the intermediary type, ordered by a custom order field set on that intermediary type. (Using a view based on the online resource type instead avoids the disappearing issue but doesn't allow us to set a unique order per list, as far as I can figure.)
- In English, everything is working fine (see for example hidden link)
- In Spanish, things work fine up until we add the translation of the intermediary post. At that point, the translated resource totally disappears from the list (see for example hidden link). If we delete the intermediary post translation, the resource shows back up again.

I had put in a ticket about this when we were first developing the site - even more detail in the back-and-forth there: https://toolset.com/forums/topic/issue-with-wpml-and-intermediary-posts/. The supporter was able to duplicate the problem, had escalated the issue, said it would not be an easy fix, and provided a workaround. At the time, we ended up just setting aside the ordering requirement and using a view based on the content type instead of the intermediary instead. But now we've reworked the content and ideally need the ordering to work, so I'm back to the original view.

I tried setting up the workaround described in the last post of that thread, but it's not working for me. If I set the filter based on the relationship as seen in that screenshot, I get no results for the nested view. If I set it to "in any relationship" instead, the post shows up, but the same disappearing issue happens as without the nested view.

I'm not attached to this way of doing things and would be happy with any solution that allows us to have a unique resource order and description for each list and to translate those descriptions into Spanish. Hopefully this all made sense - let me know if anything needs clarification or if more info would be helpful.

Thanks!

#2548677

Hello,

The key problem of your previous thread is:
In the translation version of intermediary post, can not display related post information with shortcode attribute item="".

The workaround I provided is:
Display the related post information with a post view(using relationship filter)

It works fine in below test site:
Login URL:
hidden link

See the translated intermediate post here:
hidden link

only post view can output correct result, you can find the post view settings here:
hidden link

Please let me know if you still need assistance for it, you can also try to reproduce the same problem in above test site:
If I set the filter based on the relationship as seen in that screenshot, I get no results for the nested view.

#2548967

Aha! I tried reproducing the setup in your test site and was able to figure out what the difference was - our view had item="@discover-it-online-list-online-resource.parent" set in the loop editor. I got rid of that, and now the workaround does work as expected. Thanks for your help!