Not able to translate "location"'s address

I used to be able to translate the address of the location from English to French but now those fields have disappeared.

sorry but can I know when is this started to happen? eg. after plugins update, theme or wordpress

thanks

Hi Angelo, I did a bunch of upgrades yesterday including theme and plugins and that’s when I noticed it (Can’t say about wp as mine updates automatically). But I’m not sure if it is this update or earlier one as I did not used Events Manager for a while and so did not notice the problem until I used it yesterday.

I have tried it with all plugins except the ones from WPML(CMS, String Translations) and WPML Compatibility deactivated and I have the same problem.

I also tried it with 20/15 theme and the problem remains. Hope this helps.

I see, let me try to replicate this and inform the devs if there is something wrong or bug.

Hi Angelo, I was hoping the problem would have been solved in the last upgrade to 5.6.2, but after the upgrade, the problem of not being able to translate the Location’s address still remains. The “Edit location” page in French does not have the “Where” panel (it does not appear uner Screen options either so I cannot tranlate things like “street”, etc.

Please see this:https://imgur.com/XVz4BOW

I’ve tried with all plugins except WPML translations plugins deactivated and the problem remains.

Thanks

If you deactivate the Events Manager and WPML Compatibility plugin does the location panel reappear on the Add / Edit Event page?

Yes the panel reapears in the Edit/Add Location page. I tried to translate it but I’m unable to save the translation. The panel disappears again if I reactivate the Event Manager and WPML Compatibility plugin.

I get this too. I’ve let the Dev team know.

sorry for the delayed reply. this is actually normal behaviour, because if you want to translate a location, you need to go to the actual location and translate, as you would any CPT with WPML.

I can see where the confusion arose though, in earlier versions there was a bug where the location wasn’t being linked to the one assigned to the original event translation, so you had to assign a location to the translations when that shouldn’t be the case.

I’ve noted down the idea as a feature to at least give an informational box showing the location assigned to this event, with a link to edit/translate the location, that’d clear up any confusion I hope!

Hi Marcus, thanks for answering. I don’t think it’s confusion because of the bug. I’m doing what you say and that does not work, unless I’m not understanding you properly. Because I Do go into the translation of the location and I cannot see anyway to translate it. Please refer again to https://imgur.com/XVz4BOW for images. I did not have the bug you mention, I used to be able to translate my locations fine until some upgrades…

Just to make sure I’m doing the right thing : My steps:

I have a location in English. I input the location address in the “WHERE” panel below the WP edit box. It says Address, City/Town etc. and those info need to be translated.

I want to translate that location in French using WPML to change for example “street” to “rue” – so I click into the WPML translation button which brings me to the French linked translated page. I’m still into Location not Event. But now, the “WHERE” panel, who used to be there is gone. It has disapeared. So I cannot input transated location adresses in another language. So my problem is not being able to do the translation as you write above. And it’s this “WHERE” panel that reapears when you deactivate the Events Manager and WPML Compatibility plugin

So when I go to my Event in English I select the location – everything is fine. When I go to the translated French Event page the location is in English instead of French since I could not do the translation in French anywhere, unless I haven’t found how to do it properly?

Could you please do look into it, it’s a real big problem for me?

Hi, yes, that’s what I mean. The ‘Where’ panel will not show anymore on your translations, because you’re translating an event, not a location. The bug was before when it did show, because it created two separate locations, not one location with different translations.

Both events and locations are custom post types, the Where tab creates a new location CPT first time round (unless you choose an existing location) and then you can only edit it by editing the location CPT directly. You can then translate the location via WPML.

Now, there is something I missed here. You mention changing ‘Street’ to ‘Rue’, this isn’t possible. The concept/approach we took is when translating an event or location you should be able to translate what needs to be translated (e.g. booking settings no, but ticket names yes), so normally you wouldn’t translate an address in a country, but you can change the name/description and the country name is automatically translated. If you have a use case where a country can have two addresses we could consider it as a future feature.

Hope that clarifies.

Hi Marcus, sorry for bothering you again. I have the eerie sensation that I’m just not understanding you properly, so please bear with me ??

I want to translate a “location” not an “event” to have a location and it’s address in more than one language. (So that further on, the “event” will have the address of the location in the proper language). I cannot to this right now – when I am in the “location” edit page and then I go throught WPML to translate the location, I have no place to input the changes in the address. The “Where” panel I’m taking about is not in the “event edit page” but in the “location edit page” (if that’s what you meant above – saying it was not possible to do, sorry for the repetition).

I live in Quebec Canada, where everything has to be in French for Quebec’s residents and everything has to be in English for the rest of the country. Obviously I need to be able to translate addresses, if only in regards to accents or generic names like street.

But even if it was not for Quebec’s particular situation, what happens when you have, say, an address in Japanese on a Japanese website, with a translation in English, and that you don’t want to have an English address in the Japanese page in regards to your Japanese clients but need also to have an English translation because you’ll also have English speaking people?

For example in my case, an address location would be in English: 1234, Decarie street, Montreal, Quebec
in French: 1234, rue Décarie, Montréal, Québec

As you see, they are different an as such, if I leave an English address in a French document, I get blasted for not having translated it properly.

Seems your bug was serving a purpose ??
In the meantime, is there a way or a patch that I could use to translate the address of a location?

I tried to deactivate the Events Manager and WPML Compatibility plugin, do the location’s address translation from English to French then reactivate the plugin… but the address stays in English when you view the event in French ??

No problem, this is an interesting nuance ??

I was guessing Canada was going to be your argument, but then I wonder (more out of curiosity here), if in Quebec, an address is

1234, rue Décarie, Montréal, Québec

the official address remains the same, no? Given it’s latin alphabet it’s readable by English speakers. I guess that was an assumption I made which may be wrong. For example, in Europe, you don’t write a French address in English.

Taking your Japanese example is better actually, because Westerners like myself would not be able to write an address in Japanese, or there’d be a high probability of writing it wrong, and a little research shows that you can in fact use English equivalents when sending post to Japan or China, so being able to translate the address does have merit. I’m not sure whether one can translate an English address to Chinese though, but I’ll stop researching there and just agree to make this a feature….

However, now comes the question/problem of when this will be done, it will take some time… we’ve made some good progress working towards being 100% compatible with WPML recently, but there’s still a lot more things to address that take priority.

There is a workaround though, for the meantime. Use location attributes, those can be translated. So, you could use #_LATT{City/Town} instead of #_LOCATIONTOWN, etc. Not perfect but it will work for display purposes, the only downside aside from the extra work is you couldn’t use search forms to search in another language equivalent.

The original bug was a bug regardless and wouldn’t have been helpful, because you’d be managing different locations for each translation. So, for example, whilst viewing a location page which contains upcoming events you switch languages, it won’t contain the translated event because it belongs to a different location. The fact that they’re the same address in different languages is irrelevant programatically because the link is the location ID of the original translation. Now we link a location and translations to the original event, and then show the relevant translation when necessary. We purposefully hide the Where meta box in event/location translation admin pages due to the assumption above.

I understand it’s a tricky concept to grasp, I hope the above explains it.

Hi Marcus, thanks for your understanding, your patience, and your explanations! I agree that Canada and Quebec are a little peculiar regarding translations, as some of it comes from our history – for example some towns have bilingual statutes in a unilingual province and a lot of English names that existed at the turn of the century have been replaced by French denominations, but retain the generic English terms when translated back in English, like street, etc. I have actually seen names of streets that have literal translations – for example “Lakeshore Road” having been translated as “Chemin Du Bord-du-Lac” (which is now it’s official name) and having both French and English at the same time in its official address, because it’s a bilingual town…

Thank you also for accepting to make this translation a feature of your plugin and also for providing a workaround, it’s really appreciated. I’ll implement it right away, so waiting for this feature will not be a problem ??

Again, many thanks!

Hello – just popping in to say I used to take advantage of the bug too! In one of my sites it seems I can still translate the address, but in one that I am currently developing I can’t unfortunately. In this case working in Welsh and English and I suspect we have the same ‘political’ problems as you have in Quebec with regard to using the correct address format.
The only thing I would say though is that I think it used to work better than you might think? The site that’s still working doesn’t have future events just now, but an old event can be seen here as an example