Ditto Dito

@malikh : Have you tried multi-lingual in the meantime ? WPML and Polylang should work, but I haven’t tried so far. And mightydigital is a bit evasive on that point. Thanks if you have something to report!

Quite a bit disappointing to suggest to write a function to output html-code.

The plugin induces quite a bit of overhead with a Twig and Symfony-loader, plus own code. And all this is wrapped away because you consider these “internal”.

Why don’t you simply let me hand you a Twig template as the worst solution. Or just let me write an ordinary php template.

For the moment, your suggestion “please consider writing a five star review!” is on hold. The plugin has great potential, but is still a bit off what users need. You may want to check this support forum – and don’t bother thinking that because a thread is marked “resolved” that it is resolved.

Sorry guys.

@annalisa16 : I wanted to do the same thing, and the filter is the reply. Not sure how you feel, but this is a disappointing fix.

Thanks !

I am not sure how this filter resolves my question. I will have a go and see how far it gets me.

In the meantime, I am re-setting the topic to “not resolved” – don’t be too quick ??

Thanks Jordy !

I am not sure what is wrong, but I can definitely say that this is not a bug in your software. I suspect a glitch in the NextGen plugin plus some “unexpected creativity” (read stupidness) in front of the screen.

I’ll dump NextGen for the moment, and will give pure NextCellence a try. If it does what I need, I’ll have a look at a wplr-nextcellence plugin.

Thanks again, enjoy your holidays and be in touch soon for my purchase of the LR plugin.

Avec un bonjour de Toulouse !

This is killing me. I start to believe that I have dreamt this yesterday.

Nextgen is showing Alttext as a caption, and in the LR WP/LR plugin, I am copying the photos metadata Title into the Alttext field.

Could this be a restriction from the trial version of the WP/LR plugin ?

I had a look into the database. It seems that wp_lrsync_meta.tag_name is not copied into wp_ngg_pictures.alttext anymore.

If it has ever been, that is. But from observation, this is what I believe is happening.

Chouby, a couple of ideas to get closer to something that is requested oftentimes:

1/ Write a routine that duplicates all your media across all languages (that are not yet translated).

2/ Write a hook that automagically creates all languages when you upload a new image.

That is far from perfect, but at least all images should be available for ordinary image-in-post cases.

We keep image-in-custom-field-in-post for later. ??

If I have large experience with Polylang? No. But for me, software is just like with good-looking girls: I immediately recognise them when I see them.

Regarding speed, the database part is not the biggest issue. Databases are fast. The big problem is the number of calls to a database, and this is where WPML fails. Their problem, in my limited experience, is that they need to be please everybody, any theme, any plugin, any anything. Polylang is not there.

If I were you (which I am not, so please take the following as what it is: an opinion of someone who has no idea what you do), so if I were you I’d go the multi-language route at the cost of WP SEO Yoast. Search engines will love your double daily dose anyway, why bother with meta-tags? Put it another way, SEO is to get people onto your site. Another language does that as well.

Getting media in a translation is potentially easy. At least if you don’t need different images per language. There is a small hack to copy the original post into a translated post. It’s a 1:1 copy, and if you just change the text, the media stays attached. You just need to translate the media’s meta information (caption, description, alt) in a second step.

Does that all make sense? I hope so.

Maybe this gets you further. It would be nice if you could tell us back.
https://pastebin.com/bsEM0P2R

I actually have some problem understanding what doesn’t work, and why your theme won’t allow you to link pages.

Is there a workaround to set the english home page to “https://mydomain/home” and not to “https://mydomain/en” ?

I don’t think so. Unless you want to dig into your .htaccess file.

Explanation: The /en/ part tells WordPress / Polylang which language to use, English in that example. Without the /en/ it will think that you want your default language, German in your case. There is no way that I know of to tell Polylang that /home is the English version of /startseite.

I happens if you try the code you gave?

For your second question, I guess you can find the answer in the sticky posts.

For the first one, my guess would be that the answer is yes, polylang can handle that. But maybe it’s just unclear to me what particularities a “web magazine publishing a lot” has. What is different to an ordinary blog, and that may refine the answers you get.

Isn’t the “problem” outside of any category discussion?

When I set the english category as default, the posts wouldn’t show up on the german site.

My reaction is: Of course not, without any additional programming, languages are never mixed. First selection is always by language, then possibly further filtered by category.

Glad that you found a hack! ??