[Samarpan P.]

Hi Geoff,

that’s basically good news 🙂
Seems like we messed something up somewhere.
It does work now, though it’s not easy to pinpoint where the problem was exactly.

I changed the WPML translation mode to manual.
Just out of curiosity – do you advise against using WPML’s translation editor for general reasons or only because of issues with The Events Calendar?
Creating a new Venue and Event using manual mode did not fix the issue, at least not right away.

Next I deactivated all plugins except Events Calendar and WPML related Plugins, to no avail. (The site is still in development so no problem doing so :))

That’s when we decided to not use two slugs, but just one that kinda works in both languages – “location”.
So at first I unchecked “Use different slugs in different languages for Venues.” in the Multilingual Content Setup, which made the venue pages work in one language, but produced 404s in the other.
Then I clicked the “Translate Link Targets” button at the bottom, which still didn’t make it work.
Then I re-saved the Permalinks, nothing.

Then I installed this extension:
https://theeventscalendar.com/extensions/change-labels-events-venues-organizers/
as suggested here:
https://theeventscalendar.com/support/forums/topic/change-venue-translated-slug/
and set the Labels for the venues to “location”.
Then I clicked the “Translate Link Targets” button again and re-saved the permalinks again.
Then I tried using the WPML String translation again and around this time is where it started working.

Now I realised, that the aforementioned Extension had nothing to do with the slugs (or does it?), so I changed the labels back to “Veranstaltungsort”. (still keeping the info in here as it might point to what the problem was in the first place.).

Since it seemed to work now, I tried the “normal” way via Translation Management > Multilingual setup > “Use different slugs in different languages for Venues.” once more, and now it works well with different slugs.

Sorry if that all seems a bit muddled, but that’s all I can recreate at this point 🙂

I still wonder what the problem was in the first place, but as it sems to work now as it is supposed to, we’re happy.

Thank you very much for your help Geoff!

Best wishes,

Samarpan

[Samarpan P.]

This reply is private.

[Samarpan P.]

Hi Geoff,

thanks for reaching out!
As far as I can tell, we did set up everything according to the knowledgebase.

Here’s what we did now:

• Clicked on all the buttons at the WPML-Troubleshooting page
• Re-Saved the Permalinks
• Checked the option to use a cookie for AJAX operations at WPML->Languages
• Clicked the “Translate Link Targets” button at Multilingual setup, which does indeed take some time.
• Removed the Selection for “Use different slugs in different languages for Venues.” in the Multilingual Content Setup
  -> Events appear on the venue site in the original language (German), trying to switch over to secondary language results in a 404.
  Guess that could be handled by the “Translate Link Targets” button, but that’s not what I’m here for 🙂
• Checked it again, made sure that the slugs were entered correctly
  -> No results found at venue pages.
• Set up a new venue and a new event using that new venue individually
• Clicked the “Translate Link Targets” button again

Unfortunately, nothing removed the issue so far.
The option how to translate strings in themes and plugins is set to the first option: only use WPML String translation (don’t load .mo files).

Best wishes,

Samarpan

[Samarpan P.]

Hi Geoff,
thanks, your suggestion works out well.

Best wishes to you
Samarpan

[Samarpan P.]

Hi,

that doesn’t do the trick. The widget template uses a function to display date and time:

<?php echo tribe_events_event_schedule_details(); ?>

It is not possible to change anything on the template level (at least I don’t know how). Any chance by modifying the function via the theme’s functions.php? I’d rather avoid any modifications of the plugin core.

Thank you!

[Author]

Posts