Hi, I've built a website with Toolset and WPML. I've 3 languages: ES, EN, DE.
I've the CPT Perros (Dogs) and the CPT Custionario (Questionnaire) with a relationship 1-to-many.
Users can fill a Toolset form that creates a Custionario post connected to a Perro. The Form has the relationship field so the user can select the Perro. It works great on the default language ES, but I get this error message if I open the form on EN or DE pages:
Relationships can only be managed in the default language.
Is it a bug? Is there a solution?
Perros are only translated to ES, is that the problem?
I found that if I set by a hidden custom field the value of @perro-cuestionario.parent with Perro ES post ID, I can correctly connect the Custionario EN or DE post to a Perro ES post. I could build a select with a view to list all the Perro ES so the user can select the correct dog to connect. Does it make sense? Do you see any inconvenience?
thanks
cheers
Hello, right now, post relationships can only be managed in the primary language of the site. It's not a bug, it's a limitation of how the relationships feature was originally created in Toolset and the way WPML's "transalatable - fall back to primary language" option was implemented. As of right now, there is no easy workaround for this problem except to force your secondary-language Users to submit content and establish post relationships in the primary language. If content does not exist in the primary language, it is not currently possible to manage Types post relationships for that content.
However, our developers are currently wrapping up a major update to both Toolset and WPML that will facilitate translation of related content with or without related content in the primary language. In other words, you'll be able to create content in a secondary language and manage post relationships for that content in the secondary language without having original content in the primary language.
This has been a major limitation for multilingual content, especially that content which is created by front-end users, and we've been working on the required changes now for some time. The good news is we hope to have those updates very soon. As of last week, we are expecting a release in the next week or two, so it's not something in the far distant future. It's expected to be in the next major round of updates, so very soon.
I'll be glad to keep you posted here as I receive more information, or we can close this ticket and open a new ticket for questions when the software is actually released.
I found that if I set by a hidden custom field the value of @perro-cuestionario.parent with Perro ES post ID, I can correctly connect the Custionario EN or DE post to a Perro ES post. I could build a select with a view to list all the Perro ES so the user can select the correct dog to connect. Does it make sense? Do you see any inconvenience?
We used custom fields to manage post relationships for a long time, and it can work but it has limitations. It doesn't work well with many-to-many relationships, for example. Obviously it won't integrate with our post relationships APIs or post relationships filters, and in a few weeks you may find you want to redo this feature anyway since secondary language post relationships will be implemented and supported in Toolset and WPML.
