[Leah]

Hi framegirona,

Yes, I believe that The Events Calendar (our core plugin) is not compatible.

Best,

Leah

[Leah]

Hi Ahmed,

As I mentioned over email, our plugin is not currently compatible with WPML. We can continue discussing the situation via email.

Best,

Leah

[Leah]

Hi Guido,

Thanks for your interest in our plugins. If you are already using WooCommerce then your best option for selling tickets is WooCommerce Tickets. It uses WooCommerce for the transactions, so you wouldn’t need to add or learn another commerce engine.

There are Brazilian Portuguese translations for The Events Calendar, Events Calendar PRO, and WooCommerce Tickets. However, they are outdated. I would love to have you help update them- you could even get free licenses in exchange. If you are interested, check out the Getting Started post in our Translations forum where you’ll find the instructions and files you need.

Best,

Leah

[Leah]

Hi framegirona,

As you’ve read, we are not yet compatible with WPML. The same issues make us incompatible with other multilingual plugins such as Polylang and qTranslate. Unfortunately, I do not know any multilingual plugin that is currently compatible. You may be able to use them, but it would likely take a lot of complex customization. I’m sorry we can’t provide further assistance.

Best,

Leah

[Leah]

Hi passportsd,

Thanks for your post, and including all that information. That helps me identify the issue right away.

The problem here is that your are running outdated versions of your premium plugins but you are running the current version of The Events Calendar. The mis-matched versions are causing your settings page to fail.

I see that you own valid licenses, but since they weren’t inputted into your settings you haven’t been getting the automatic updates, which is why your premium plugins are out of date.

Happily, you can fix this by doing a manual update for your premium plugins. To do that, deactivate and delete the two premium plugins from your Plugins page. You should not lose data, but we recommend that you backup your database first just in case. Then install the new version of the plugins (downloaded from tri.be/my-account/downloads/) and activate them. It will work best if you deactivate and delete both Events plugins and then install them all again, instead of one at a time.

Once they are running the most up-to-date versions (Community Events 3.5 and PRO 3.5.2) you should be able to see your license key page again. You can then snag your keys from tri.be/my-account/license-keys/ and enter those under settings. You’ll be able to do future updates from your Plugins page with just a single click.

Thank you for your support!

Best,

Leah

[Leah]

Hi fxidesigns,

Thanks for getting in touch. There isn’t a built in way to duplicate an event. The easiest way to duplicate one of your existing events is to use a post duplicating plugin. We have a UserVoice thread where users can vote for us to add a duplicate event feature. Additionally, several users there have commented with post duplicating plugins that worked nicely for them.

We are also working on adding more complex recurring event options, so in the future you may be able to make yours a recurring event instead of two separate but duplicated events.

Best,

Leah

[Leah]

Hi Sandras,

To change the translation for your current, you can just put the The Events Calendar files in the regular /lang folder for The Events Calendar. You don’t need to do it under the child theme. Once you’ve put the files in there, open wp-config.php and change your language code to et_ET to match. That should do it 🙂

That coupon code should be correct- please try again and make sure you are using the whole code from the above post, including the period.

Best,

Leah

[Leah]

Hi there,

I just wanted to update you here. We were not able to fix this issue in time for our upcoming release (3.6). However, it is still very much a priority and we plan to work on it for a future maintenance release. We will keep you posted on our progress. Thank you for your patience and support!

Best,
Leah

[Leah]

Hi there,

I just wanted to update you here. We were not able to fix this issue in time for our upcoming release (3.6). However, it is still very much a priority and we plan to work on it for a future maintenance release. We will keep you posted on our progress. Thank you for your patience and support!

Best,
Leah

[Leah]

Hi there,

I just wanted to update you here. We were not able to fix this issue in time for our upcoming release (3.6). However, it is still very much a priority and we plan to work on it for a future maintenance release. We will keep you posted on our progress. Thank you for your patience and support!

Best,
Leah

[Leah]

Hi there,

I just wanted to update you here. We were not able to fix this issue in time for our upcoming release (3.6). However, it is still very much a priority and we plan to work on it for a future maintenance release. We will keep you posted on our progress. Thank you for your patience and support!

Best,
Leah

[Leah]

Hi there,

I just wanted to update you here. We were not able to fix this issue in time for our upcoming release (3.6). However, it is still very much a priority and we plan to work on it for a future maintenance release. We will keep you posted on our progress. Thank you for your patience and support!

Best,
Leah

[Leah]

Hi there,

I just wanted to update you here. We were not able to fix this issue in time for our upcoming release (3.6). However, it is still very much a priority and we plan to work on it for a future maintenance release. We will keep you posted on our progress. Thank you for your patience and support!

Best,
Leah

[Leah]

Hi there,

I just wanted to update you here. We were not able to fix this issue in time for our upcoming release (3.6). However, it is still very much a priority and we plan to work on it for a future maintenance release. We will keep you posted on our progress. Thank you for your patience and support!

Best,
Leah

[Leah]

Hi there,

I just wanted to update you here. We were not able to fix this issue in time for our upcoming release (3.6). However, it is still very much a priority and we plan to work on it for a future maintenance release. We will keep you posted on our progress. Thank you for your patience and support!

Best,
Leah

[Author]

Posts