Brook

Hello khrisme,

The untranslated upcoming string will appear in your file once you update from teh source .pot file. Unfortunately your translation is not completely up-to-date as of 3.10. If you would like to help us translate the remaining bits, we will give you a license to your choice of our plugins. Checkout this guide: The Events Calendar: Guide to translating a plugin

Cheers!
– Brook

Howdy again,

That’s actually another feature that’s about to enter beta. Just shoot us an email if you’d like to participate in that as well. 🙂

– Brook

Howdy Martin,

That’s a good question. Events categories are just regular old taxonomies. In this case the tax is called ‘tribe_events_cat’. So following any generic tutorial should do. I wanted to see if I could find one for you, and this looked like a promising Google result: http://wordpress.stackexchange.com/questions/7168/how-to-add-a-default-item-to-a-custom-taxonomy

Cheers!
– Brook

Howdy Goran,

Have a look at this guide. The Events Calendar: Guide to translating a plugin

If you’re keen to translate both The Events Calendar and Events Calendar Pro, we’d love to give you a free license to Events Calendar PRO. 🙂

Cheers!
– Brook

Howdy Indosta,

Let us know if you need further help after following Anur’s excellent advice.

Cheers!
– Brook

A heads up would have been very much appreciated though, I took the time to study your release notes and didn’t read anything about translations / strings being deprecated – then again I might easily have missed it, not sure…

leanderbraunschweig, that is a fair question. We, like many WordPress plugins, do not mention transltion changes in the changelog. Virtually every single release will have a number of them, so it is one of those things that basically happens without saying.

Anyhow, these strings are not at all “new” but were existent in the previous version (at least 80-90% I’d guess). My client doesn’t understand why something that worked before (and was translated fully) now is rendered incomplete.

The strings actually are new. It’s how WordPress and computer localizations in general work. So if “upcoming events” existed in the old plugin, but in the new one it was split up into “upcoming” and “events” then you have two new translations, and deleted the old. In this case though, “Events” was already translated in the old one so that carries over, and we only have one new translation. I know it’s no intuitive, but computers never are. It’s just how they have to work.

To everyone in this topic, basically the issue is that your translation needs to be update. Checkout this guide for contributing to the new translation The Events Calendar: Guide to translating a plugin. As outlined, there might even already be an update.po file from someone else who udpate the tranlastion since 3.10. You can download the latest from translations.theeventscalendar.com.

Cheers!
– Brook

Howdy DanielKomrska,

That line of code would break WordPress’ Ajax api, which for whatever reason resides in the /wp-admin/ folder. Since our plugin uses this feature of WordPress, ajax page loads would break.

You might try one of the WordPress HTTPS plugins instead, which use WordPress APIs to try and load everything via HTTPS. You should still be able to harden WordPress without breaking it using methods like that.

Cheers!
– Brook

Howdy Nick,

You should try changing this constant. That will likely fix your issue.

Cheers!
– Brook