[Resolved] [split] - Slider images not showing on translated posts

I saw that trying to switch to the NL version of the Accenture project was giving a fatal error in the back end, and I could see that if I tried the same on my local copy of your site I found the same.

I spent time tracing through what happens with the code and found an unexpected value for the project_gallery field being passed on the translated project, and I checked in the database and verified that the value stored was not of the format that is expected.

So to fix that I simply updated the translation of the Accenture project from the EN original. I checked the database, and the project_gallery field had a value of the expected format, and—sure enough—I was then able to switch from the EN to the NL project in the back end without error.

I did that on my local copy of your site first. Rather than wait for you to do the same on the production server I have done the same there, with the same result.

It is possible to edit the project in Dutch in the back end, and when displaying the project on the front end the slider works in both languages. ("Works", but there is only one image saved in the project_gallery, so the gallery keeps rotating the same image, on both the EN and NL pages.)

So, the slider was not working correctly because the single project template translation needed updating, and the accenture project wasn't working correctly because the project translation needed updating.

Perhaps translation settings were changed after these translations were last updated and hence the change in the settings were not reflected in the translated template and post.

I expect if there are similar issues with other projects or templates they could also be resolved by updating the translations with the current settings.

Indeed, revisting the project you linked to at the top of this thread, it had the same problem as the Accenture project.

I updated the translation for the project, and now it works correctly: hidden link

So I think the sliders issue is "resolved" inasmuch as where the same problem occurs it can be resolved by updating the translation.

Regarding your other questions:

>1. We would like to know if we can create projects in different languages and then link them between translations easily.

You mean, you would like to publish some projects in EN and translate those to NL, and you would like to publish some projects in NL and translate those to EN. Yes?

You can do that. The only limitation would be that currently you could not use Automatic Translation from a secondary language to the default language, but that does not apply in your case because you are manually translating the content with WPML's Classic Translation Editor.

>2. If we want to upload images from scratch for the same project in other languages from the backend, what would be the best practices?

Your WPML media settings are to make new images available in all languages, so this should also be straightforward. If you are publishing a project first in NL and add images to that project, those images should automatically be added when you translate the project to English.

You mention some errors but I don't know what you are referring to. Could you share some screenshots perhaps?

"translate the strong"

Sorry, could you give me an example of what you mean? A screenshot, or share some code?

OK, that's fairly straightforward.

Whenever you add texts in PHP files like that you need to prepare them for internationalization (known as "i18n" for short) using gettext calls. (This isn't specific to WPML.)

We describe that in our documentation here: https://wpml.org/documentation/support/translating-the-theme-you-created/#using-gettext-functions-in-php

So the line in your child theme from the screenshot that outputs the Learn more text would be wrapped in a __() function call, like so:

<a href="<?php the_permalink(); ?>"> <?php __( 'Learn More', 'mmek-theme'); ?> </a>

I used "mmek-theme" as the text-domain, as I don't think you are using a particular text-domain already.

Then you can go to WPML > Theme & Plugins localization and scan your child theme so that WPML can find such texts and make them available for translation.

You should then be able to go to WPML > String Translation and find the texts and translate them (you can filter by the text domain you used, e.g. "mmek-theme" if you use the same as my example above).

I'm not sure I can see the problem you describe in 1, but in any case it is almost certainly because you need to activate the setting for language cookies in support of ajax requests (screenshot). I have set that for you, so hopefully you should now get the expected behaviour on the Dutch page.

Regarding the second issue, I'm not sure what I am supposed to be looking for. Both the English and Dutch versions of the project category archive for the concepting term look the same to me (apart from the language of the text), and in the back end the English and Dutch versions look largely the same.

Can you clarify what the problem is?