Problem with translated slugs in URLs

Home Forums Calendar Products Events Calendar PRO Problem with translated slugs in URLs

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #26948
    Wojciech
    Participant

    Hi,
    I have small problem with Events Calendar PRO – most url generated by plugin is not working (error 404).
    On my site default language is polish.
    So when I create new venue or category the permalink have slugs in polish (category -> kategoria, venue -> miejsce), but links in event template, on calendar page have slugs in English – and I get 404 error.
    And the same is with events/past and /events/upcoming.
    So? What can I do to make it work?
    Of course when I turn off permalinks everything works perfectly 🙂

    #26982
    Barry
    Member

    Hi Wojciech,

    It may be that the relevant strings have not been translated in tribe-events-calendar-pl_PL.mo (and .po).

    #: ../lib/the-events-calendar.class.php:295
    msgid “upcoming”
    msgstr “”

    A corresponding entry to the above would have to be created … if you are able to do this and send the revised translation to us that would be excellent (you can email it to [email protected]).

    Unfortunately there is not a lot more I can say, none of us are particularly expert in making translations – but there is certainly a good summary of what to do on the WordPress codex.

    Thanks for contacting us!

    #27017
    Wojciech
    Participant

    Hi Barry,
    problem is that this slugs are translated in .po file.
    For example: widget with link to upcoming event is like that “http://mywebsite.com/events/upcoming/” – and I get 404 error. But when I manually change URL to polish translation “http://mywebsite.com/events/nadchodzace/” it is working.
    And most URLs from widgets and templates of events are working like that – they have slugs in english, so I get 404 error. It seems to me, that links are not prepare to be translated, and the rest of plugin is…

    #27026
    Barry
    Member

    Hi Wojciech,

    So if the slug has been translated in the .po file and the URLs are still using the English slug is it possible that the change hasn’t been compiled into the corresponding .mo file?

    I just want to ensure all the bases have been covered here 🙂

    #27169
    Wojciech
    Participant

    Hi Barry,
    I did not make this translations. I’ve got fully translated .po file.
    Editing .po file in POedit and saving it, didn’t make any changes.

    #27172
    Barry
    Member

    Right – I guess that’s my point: the .po file needs to be compiled into a .mo file otherwise WordPress cannot use your translation.

    So probably, even though you have changed the .po file, WordPress is loading the existing .mo file and for that reason you will not see your changes.

    There’s a good overview of this stuff on the Codex – I have minimal experience of making translations so that will probably be a more useful guide than any advice I can provide 🙂

    #27234
    Wojciech
    Participant

    Barry, my POedit compile .mo files always with saving .po files.
    Still, default .po file was fully translated, so I didn’t had to change anything. I don’t suppose that you would give your plugin with uncompiled .mo files.
    Now – I removed translations for slugs, rebuild the permalinks and it is working. With permalinks in English.

    #27260
    Barry
    Member

    Hi Wojciech:

    My fault for not fully appreciating the problem you reported to begin with, however it seems this is actually a known bug (our reference #16547) whereby certain segments of a URL, such as “venue”, may appear to be translated in certain areas such as the editor but are not actually routed properly.

    Something Jonah had previously suggested is removing certain strings from the .po/.mo files: http://pastebin.com/wBdpTZEW of course this means that your site would revert to using certain English keywords in your URLs, however it would at least provide better consistency.

    I’m currently following up to see what is being done in respect of this bug and will report back as soon as I can.

    Thanks again for your patience and my apologies for the inconvenience.

    #27644
    Barry
    Member

    Wojciech,

    Sorry for the time it took to get back to you with an update. However, though we definitely want to fix this it is highly unlikely it will be addressed until after our 3.0 release.

    With that in mind, all I can suggest are the steps recommended by Jonah (see my previous post).

    Thanks for your continued support and patience,

    Barry

Viewing 9 posts - 1 through 9 (of 9 total)
  • The topic ‘Problem with translated slugs in URLs’ is closed to new replies.