It works like a charm, thanks Mike!
So, basically you’ve extended the size of the “text part”, so that it takes the whole space, and leaves the thumbnail alone in a row, correct?

Let me just ask for a last adjustment: what if I’d like to have the thumbnail CENTERED in the row?

Thanks again!
Bye,
A.-

If anybody is finding the same issue in the future, and interested in how I’ve solved it, here is the full thread in WPML forum.

https://wpml.org/forums/topic/captions-of-the-images-in-the-galleries-are-not-visibile-in-the-advanced-editor/

You can close this one, thanks!

Thanks Guenni for your checks: I know I can translate them individually in the Media Translator, but I am interested in finding the images in the WMPL Advanced Editor (because it is more comfortable: you’d find all you need to translate for one page in a single page, I don’t want to translate the page in the advanced editor and then go and find every single image in the Media Translator, one by one).

In my case, I can find images in the Advanced Editor only if the Gallery is NEW (= created after WPML installation) or if I add new images to an OLD gallery (=created before WPML installation)…

Well, but this is not a local installation, and it is not mine: it is an external installation (https://woocommerce-278662-3175935.cloudwaysapps.com/) that the WPML support team granted me access to. In my mind, it is like installing enfold on a SECOND website, and this is why I am not sure I can do it.

THX
Ciao,
A.-

Guys, I am leaving it here in case any other user in the future encounter the same issue.
I had to deactivate the BLOCK EDITOR and use the CLASSIC EDITOR.

Now, with the CLASSIC EDITOR, I save a Portfolio, I launch the WPML Advanced Editor, I translate everything, I save it, and the portfolio page is correctly translated.

You can close the ticket, guys, unless you don’t want to ask me something to investigate why this is happening. I am so happy to have solved it.
Bye,
A.-

Thanks Mike, too bad you have to do it by hand… you can close the topic. Bye!

It happens with the user you’re using (that I’ve tried), and my user. As I told you, it is not related to the plugins: I made a mirror copy of the production environment to staging, and in staging I never had the issue.

But… Rikard, NOW it is not happening anymore on my side as well.

It is a mistery. I did not do anything: this morning I’ve tried and you see the result in the screeshot of my previous message. Tried again now, I don’t have the error anymore.

No idea what caused this. It was not working in Edge, in Chrome, in Firefox. No updates have been made in between. Just time passed by.
A real mistery.

Thanks for your support, though, even if we did not find the reason of the issue…
You can close the ticket…

Close it, thanks Rikard!
Bye,
A.-

Sure! Check this one out:

Simply resize the screen: you will see that the subheading “da Colle Garda a Colletto Taf via Monte Rena, Taille e Taf” will be split in 2 lines: until the moment when the font size is not decreased (screen width > 767 pixel), the space between the 2 lines remains acceptable.
When you reduce the screen size below 767, the font size decreases, and the space between the 2 lines is annoyingly large… it may be that the “line height” of that subheading remains the same IN PIXELS, while the font size is decreased. This is why you get that “distance” between the two lines. Just my 2 cents!

It’s working now, thanks Yigit!

Excellent as usual, Rikard! thanks so much. You can definitely close the ticket!
For everyone in the future wondering what he added to my CSS, here it is. I am not sure it is ok for everyone, but at least it is something you can experiment.
Bye!
A.-

@media only screen and (max-width: 1300px) {
  nav.main_menu {
    display: block !important;
  }
  #avia-menu .menu-item {
    display: none;
  }
  .av-burger-menu-main.menu-item-avia-special {
    display: block;
  }
}

@media only screen and (min-width: 768px) and (max-width: 990px) {
  span.logo img {
        padding-top: 25px;
}
}

IT IS WORKING!!!!

Thank you, thank you very much for having spent so much time trying to fix this one!

Isn’t the Horizontal Gallery working definitely better this way on mobile phones?? I still cannot understand how the “standard” behaviour is acceptable by other people! :) If I tap on an image on the horizontal gallery, it must open directly in the lightbox, period!

Well, who cares why other people like to have an intermediate tap? Today I am happy! :-)
Thanks, thanks so much.
Bye!
A.-

Thanks Ismael!

But on IOS (I cannot check on Android) it is still showing me the “<= =>” enlarge icon after the first tap, and then opening it in the lightbox only after the second tap.
You can check for example with this one:you’ll find an horizontal gallery just below the first descrption section.

Thnks for yout efforts, Ismael!
But what I don’t understand is: this behaviour should be annoying for everyone, isn’t it? If I see a picture on the screen, I want to enlarge it by tapping on it once. Why should I tap on it TWICE, just to make a useless “enlarge icon” appear on firts tap? :)
THX
Bye!
A.-

Hi @Rikard. I already explained in my first message that I already did what you are asking to test.
1) I removed the whole CSS
2) I set the Default Content Font Size to a large value
3) Cleared the cache, opened the website: the default text is still unchanged.

But I did it once again. In these screenshots you can see:
1) Set the default font size to 70px (all the 4 values, just to be sure it is not mistakenly skipping the first value): https://imgur.com/a/lZNGH0E
2) cleared the whole CSS area (you can see that it is also “saved” already: https://imgur.com/a/qJzNRMb
3) See the normal text when I access no matter what page (you can see that I am also in incognito mode): https://imgur.com/a/iSjGTmo

Therefore, as I said in my previous messages, the Default Content Font Size seems NOT to be working.
I also wrote already that the H1, H2, H3… values in Typography are working fine. The only one that seems not working is the Default Content Size.

Bye,
A.-