Localized view & venue problems

[apkoponen]

Hi,

I have the following problems:
1. The month view won’t work from the chooser. It works from /tilaisuudet/month/, but it apparently tries to use the localized form /tilaisuus/kuukausi/, which cannot be found and then redirects to an event called “kuukausikokous” found in /tilaisuus/kuukausikokous/.

2. List view won’t work, when trying to switch to it from another view. It works from /tilaisuudet/upcoming, but the view chooser directs to the localized /tilaisuudet/tuleva/.

With these two the problems seems to be that the view link from the chooser is localized, but the view slug is not. Photo, week and day view slugs are localized and they work. and map slug is not localized and it works.

Also, I have a venue called “Toivon lähde”, which can be found through search, but when the link is clicked, it gives a 404 error.

[Barry]

Hi apkoponen,

I can’t see the problem as the URL you provided seems to relate to a site that is not yet online. Can you confirm if the problem you are experiencing persists when you disable all other plugins (except for The Events Calendar/Events Calendar PRO) and at the same time switch to a default, unmodified theme (such as Twenty Twelve)?

Thanks!

[apkoponen]

Hi, for some reason it disappeared with disabling and re-enabling all plugins. Interesting.

Thanks for you time!

[apkoponen]

BTW, there is still a problem with the icons on filter bar view chooser, they are the same (“Month”-icon”), this did not get fixed with disabling all and changing the theme.

[Barry]

If your site is translated into a different language then that is, unfortunately, a bug in our code. Again we’re aware of this and have a fix in the works.

The basic problem though is that the actual CSS classes are being translated (so list might become lista, as one example) and that means our style rules that target those items and set up the special-to-view icons are failing. It’s possible as another user did to workaround this by adding custom CSS rules, if you are comfortable with CSS of course.

Again, we are aware of this issue and hope to get a fix out there shortly.

Since the original issue is resolved I will go ahead and close this thread. Thanks again!

[Author]

Posts