This thread is resolved. Here is a description of the problem and solution.
Problem:
The issue here is that the user wanted to get the language of a specific post as well as the Language of the current page on the frontend.
Solution:
This can be done by using the shortcodes below.
// Add Shortcode
function get_post_language( $atts ) {
// Attributes
$atts = shortcode_atts(
array(
'id' => '',
),
$atts
);
$language = apply_filters( 'wpml_post_language_details', NULL, $atts['id'] ) ;
return $language['language_code'];
}
add_shortcode( 'get_post_language', 'get_post_language' );
To get the current language being viewed you can use the shortcode below.
// Add Shortcode
function current_language() {
$my_current_lang = apply_filters( 'wpml_current_language', NULL );
return $my_current_lang;
}
add_shortcode( 'current_language', 'current_language' );
You can add them to the toolset custom code section in Toolset -> Settings -> Custom Code and activate the snippet.
The shortcodes that will be generated are
[get_post_language id='[wpv-post-id]']
And
[current_laguage]
Now for the get_post_language shortcode i'm passing in the id of a post to get the language of that post based on its ID.
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.69 hours from now. Thank you for your understanding.
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| - | 9:00 – 12:00 | 9:00 – 12:00 | 9:00 – 12:00 | 9:00 – 12:00 | 9:00 – 12:00 | - |
| - | 13:00 – 18:00 | 13:00 – 18:00 | 13:00 – 18:00 | 14:00 – 18:00 | 13:00 – 18:00 | - |
Supporter timezone: America/Jamaica (GMT-05:00)
This topic contains 6 replies, has 2 voices.
Last updated by 5 years, 2 months ago.
Assisted by: Shane.
Hi
I am using Toolset for a CPT on a site along with WPML with two languages and Toolset Views with a search function to show the CPT posts as results.
The CPT has custom fields and some of them are repeatable fields.
And this is where my problem is.
As I have two languages and the CPT posts are going to be written in language 1 first and published and then slowly translated one by one into language 2, I need the views/search to only show the CPT posts for language 1, when that language is selected on the language selector in the menu, and only show the CPT posts for language 2, when that one is selected.
For this I would select “Translatable - only show translated items” for the CPT in the WPML settings, and not “Translatable - use translation if available or fallback to default language”.
But this cannot be done when using repeatable fields?
I am told in the Toolset repeatable customs fields when editing one of the CPT posts, that I need to enable the “Translatable - use translation if available or fallback to default language” setting to access/edit the field.
I seem to have read somewhere on either of your sites something about this also.
It is very unfortunate if this cannot be done as it makes the website work counterintuitive for the users/editors who do not wish to publish/show language 1 posts on language 2 as the fallback setting will it do.
I just switched from Polylang because of conflicts with Toolset Views, and really like WPML, but Polylang had no problem with separating the two language posts on the views though.
What to do? And why is this so?
The funny thing is, that when I do use the setting “Translatable - only show translated items” is does work on the frontend - only the selected language posts are show on the views - but I am just not allowed to edit the CPT fields in the backend, where I get the error (se the attached image).
If I have to use the “Translatable - use translation if available or fallback to default language”, there must be someway to hide the second language on the views, to make the views only show one/the active language??
Both Toolset and WPML is from the same company, as I understand, so I hoped, that they would work perfectly together…
Best regards,
Andreas
