jjbte

If you can’t reproduce the issue, it seems like it would have to be my theme or some other plugin. The two sites are running the same theme. When I first noticed the “//” the sites had one other plugin (AIOSEO) in common. I don’t recall if I had that plugin installed on the test site back when you first fixed the double language parameter issue (when I’m pretty sure the “//” issue did NOT exist).

Anyway, please don’t fret over it. It’s probably not affecting anyone else, and it doesn’t affect the actual functionality of my site. The search feature is working as expected in all languages. The “//” is just a slightly annoying cosmetic issue that will likely go unnoticed by the majority of users.

Thanks for looking into the issue and for all your time, effort, and help.

The “Known Issue” approach is a really good idea. In my opinion, if someone is posting “important” photos, they should be carefully filling in all the fields anyway. It’s usually considered good practice to include Alt text for photos/images.

Thus far, I have not been able to pinpoint any code changes that might help with WordPress standard gallery translations. The “_e” trick produced unexpected and unsightly results for the caption, and I have not yet gone through all the wp-includes/media.php code to see just where the Caption and Title values are initially retrieved. If I get to that point and get any ideas on what plugin changes might help, I’ll try them on my test site and try the pull request thing if they work.

The “//” thing is happening on both my test site and the real one I’m building. I’m pretty sure it was NOT happening back when you fixed the double language parameter issue, but I have no idea when it may have started. If I initiate a search, the results page URL has a double slash (example.com//?s=search1). If I use the language switcher on the search results page, the language changes and the URL’s double slash goes away (example.com/de/?s=search1). If I initiate another search, the double slash comes back (example.com/de//?s=search2). I normally have the “Hide URL language information for default language” box checked under qTranslate-X’s Advanced Settings. I tried unchecking that box to see if that might be contributing to the issue, but it made no difference.

I hope that information helps you. The double-slash thing is quite harmless since any browser I’ve ever worked with is forgiving of double slashes. Plus I doubt the average user will even notice. If I come up with any other ideas about what code could be causing the problem, I’ll let you know.

You’re my hero!!! Caption and alt tags are being translated properly for standard WordPress galleries. If all image properties–Title, Caption, Alt, Description–have values, WP gallery uses Alt and Caption accordingly. It does not appear to use Title and Description at all.

However, if Alt is empty for a given image, the wp_get_attachment_image function in wp-includes/media.php looks first to the Caption field and then to the Title field as a substitute for Alt. In either of these cases, the Alt value is NOT translated properly. So the Caption is translated properly for use as a caption, but not when it is used as a substitute for Alt. This is a very minor issue IMO. I usually fill in all fields for important photos, and not many users actually see the Alt text.

For Jetpack galleries, all fields are now translated properly except for Alt. I did post about this and other minor translation issues in the Jetpack forum yesterday and they’ve asked me to post a pull request on their GitHub page, which I will try to do later today.

I also looked at various other areas since you asked me to test. On my test site, I toggled the Hide Content setting to see the results. Either way, behavior is still as expected. When content is hidden, non-active language content, including menu items, do not appear. When not hidden, links to other-language content appear and work properly.

I did notice one minor issue that may have existed before and I just didn’t notice. I recall you recently fixed an issue with double language parameters appearing in the URL when using the Search feature. Search is still working fine in all languages, but I noticed a double slash (//) appears before the query string in the URL when searching.

Otherwise, I basically navigated around both my test site and the live site I’m building. I switched among my active languages and everything is working as expected, both in the web pages themselves and in their source code.

The Admin area still seems fine as well. In fact, it looks like you even fixed the theme preview pane issue I recently read about in another thread.

If there is something specific you’d like me to test, let me know and I’ll try. Thanks again for working so hard, and for being so attentive and responsive.

Because I have suspected JetPack as the cause of this and other translation issues, I have been working with a WordPress installation with just qTranslate-X installed. I finally I had a chance to insert a photo gallery this evening and there are issues even with WordPress’s own gallery functionality. I can’t say whether there are issues with the image title attribute because WordPress galleries don’t appear to include that attribute, but the image caption is definitely not translated properly. The multilanguage captions all appear together with no spaces between. In the source code, they appear with the <!– tags between them. On the other hand, the image alt tag is translated properly.

On the Edit Media page, The ID of the Caption input (textarea) is “attachment_caption.” I tried adding this to the ID field under Custom Fields on the qTranslate-X settings page, but it didn’t help.

I am using the latest version from GitHub (2.9.8.1). Can you confirm that photo galleries are translated properly with a theme like Twenty Fifteen? I want to get to the bottom of this issue. If gallery translation works in other themes, then I’ll know the issue is related to my theme and I’ll ask its developer for help. Thanks so much.