[Andras]

Hello Callum,

Thanks for reaching out with this issue and I’m sorry it is causing you trouble.

I have tested this now extensively and though some code is in place to add a page break after every event and ticket, somehow it doesn’t kick in. I’ll mark this issue for fixing.

If you need this fix faster then this is what you can do:

1. Copy this file:

wp-content\plugins\event-tickets\src\views\tickets\email.php

to this folder:

wp-content/[your-theme]/tribe-events/tickets/email.php

2. Open it for editing. Line 236 should look like this:

$break = 'page-break-before: always !important;';

Remove the space after the colon like this:

$break = 'page-break-before:always !important;';

3. Save and done.

Please check if this solves it for you and let me know.

Thanks and cheers,
Andras

[Andras]

Hello Elza,

Thank you for getting in touch! I am really sorry you are experiencing this issue with the translations. I have checked that other thread and the related bugticket and that bug was fixed in April 2016 with version 4.3.1. Currently we are at 4.5.3.

In order to determine whether this bug has returned I would kindly like to ask you to share your system information with me.

Also, can you tell me what exactly is your process to make it work? Do I understand correctly that:

1. You update the plugins => this breaks the recurring event urls
2. Open the translation files and update the string to “all” from “alle” => this makes them work again?

Thanks for sharing this and I’m looking forward to helping you solve this!

 

I am Editing Po files for months now and it becomes a burden.

If you save the .po/.mo files under wp-content/translations/plugins then they should not be changed with a plugin update. With the plugin updates only the files in wp-content/plugins/the-events-calendar {or any of our other plugins}/lang are updated.

Cheers,
Andras

 

 

[Andras]

Hello Wade,

Thanks for using our plugins and for getting in touch with us with your question.

I’m sorry for the long wait for an answer to your question. Our forums have gotten a bit more busy lately. We are trying to give every issue the fair amount of attention which can result in a bit longer response time in a busy period. Please also note that we don’t work over the weekends and based on our Support Policy we try to give an answer to every post within 48 hours in the working week. Thanks for your understanding.

I have checked your sitemap and to test this I have also created a sitemap on my local install with the free version of the All in One SEO plugin, which you seem to be using as well.

I used the default settings for generating the sitemap and I didn’t get any duplicates.

What are your settings for generating a sitemap? Can you share that with me?

Also, I would much appreciate it if you could share with me your system information. Thanks!

Looking forward to helping you solve this.

Cheers,
Andras

[Andras]

Great questions, I was sorta afraid you’re going to ask that. 😀

To tell you the truth, I have no clue. But yes, it should work. As an addition, probably I would also delete the child events (meaning the recurrences) from the wp_posts table, just to be sure and to minimize junk in wp_posts.

When you create a recurring event, then 1 entry is created for the “main” event, and also separate entries are created for the recurrences which have the ID of the main event in the parent column of wp_posts.

When you will recreate the new recurrence rules, then a new set of child entries will be added to the table, and I’m not sure the old ones would be removed.

I guess you could test this with 1 recurring event and get confirmation that it works.

Cheers,
Andras

[Andras]

Hi Pamela,

No worries. 🙂

I’m happy to hear the issue is gone.

I am going to close this ticket, but if you need anything else related to this topic or another please post a new one in the forum and we will be happy to help you out.

Cheers,
Andras

PS: If you like our plugins, and you didn’t yet do so 🙂 we would be happy to receive a review in the wordpress.org repository. Thanks!
https://wordpress.org/support/plugin/the-events-calendar/reviews/

PS2: We’d be also grateful if you would give us feedback on your satisfaction with support. Just click on one of the classy looking emojis below. 🙂 If you can spare a few words, that’s even better. Doublethanks!

 

[Andras]

Just putting the reply here as well, maybe then you’ll be able to reply here too.

There is already a developer assigned to do this fix, however no release date has been set yet. I’m sorry that the wait is so long, please hang in there. This is on high priority at the moment and we are working on it.

Thanks for your continued patience!

Cheers,
Andras

[Andras]

Hey Mister,

Sorry about that. Try why wesleyanhq suggested it should work.

Nonetheless, there is already a developer assigned to do this fix, however no release date has been set yet. I’m sorry that the wait is so long, please hang in there. This is on high priority at the moment and we are working on it.

Thanks for your continued patience!

Cheers,
Andras

[Andras]

Hi wesleyanhq and thanks for chiming in.

I retested the issue and I could reproduce it. I also checked the bugticket for this and a developer is already assigned to developing a fix with high priority, though there is no set release data.

I’ll add this thread to the bugticket to give it more push.

I’m sorry this is causing you trouble. Hang in there, a fix will come. Thanks for your patience!

Cheers,
Andras

 

[Andras]

Happy to be of service. 🙂

Since this is marked resolved I am going to close this ticket, but if you need anything else related to this topic or another please post a new one in the forum and we will be happy to help you out.

Cheers,
Andras

PS: If you like our plugins, and you didn’t yet do so 🙂 we would be happy to receive a review in the wordpress.org repository. Thanks!
https://wordpress.org/support/plugin/the-events-calendar/reviews/

PS2: We’d be also grateful if you would give us feedback on your satisfaction with support. Just click on one of the classy looking emojis below. 🙂 If you can spare a few words, that’s even better. Doublethanks!

 

[Andras]

Hello Troy,

Hope you had a great weekend!

Thanks for sharing all that information, much appreciated, and it helps a lot now that I know the details.

Unfortunately the issue is knows. It is coming from the recurring events. A couple versions back we have changed how recurring events are handled in the backend and some _EventRecurrence metadata gets broken after the update, and thus you can get a buggy backend (incl. freezing scripts) when editing recurring events that have been created before the plugin update. 🙁

As said, we are aware of this issue and one of our developers is assigned to the ticket. According to the current plans the fix should come in about a month or so.

Until then there are 2 workaournds, but one of them might be a bit tough due to the sheer number of events you have:

1. Re-create the recurring events.

2. Roll back to a previous version of the plugin. Looking at your data I’d say 4.2.5 or so.

While this might not be the answer you were looking for, I hope it clarifies things a bit. I ask for you patience until we develop the fix.

I am going to set the status of this ticket to “pending fix” and we will update it once the fix is released. You can still post here regarding the topic.

If you have any new questions or issues please create a new ticket and we’ll be happy to help.

Thanks and cheers,
Andras

[Andras]

Thanks for confirming that, Marcus.

I checked the status of the fix. It needs to go through 2 rounds of testing and if all goes according to plan it will ship within 2 weeks or so. Hang in there.

Cheers,
Andras

[Andras]

I was digging a bit in the database and this is what happens:

When you save the extra fields, then an entry is created in wp_postmeta, which is connedted to the ticket (meaning post_ID column contains the ID of the ticket, which is in wp_posts).

When you change a field name, then this entry in wp_postmeta is updated and the old name (and the slug) will be replaced by the new name (and slug).

Here’s a screenshot of before (on top) and after (on bottom): https://cloudup.com/c6ZRzPUeZK8

When a ticket is purchased and the extra field values are saved, then the slug of the field is saved in the purchase entry, but not the label itself. In your screenshot you can see the slug. (Basically the slug is the same as the title, only made url friendly.)

So to give a definite answer, no, the label is not saved in the database, but the slug is.

I’m not sure how this can be exported though. The fix likely will fix that issue.

Hope this clarifies.

Cheers,
Andras

 

[Andras]

Hello Martin,

Thanks for getting in touch and I’m really sorry about this issue.

To be able to better support you, could you please share your system information with me?
Here’s a handy guide how you can do that:
https://theeventscalendar.com/knowledgebase/sharing-sys-info/

Meanwhile I will try to check if the fix for this bug has been released already.

Cheers,
Andras

[Andras]

Hello Pamela,

Thank you for reaching out to us! I’m sorry about the issue you are experiencing.

I went to your website to check this out and I didn’t experience the issue you mention. Here is a video I made of it.

https://1drv.ms/v/s!Aqh6lbOjUW1TqHiW5FuxyjcTvd8A

This is on the http://christiesbaptist.org.au/events/month/ page. Is that right?

Andras

[Andras]

Grüss dich Stefan

Hey, thanks for going Pro and welcome to the forums!

I’m sorry about this issue.

I was curious and got lucky. I looked into the Easy Appointments plugin and totally by chance I discovered that it is using the same library as The Events Calendar. It is this one:

wp-content\plugins\easy-appointments\vendor\lucatume\

(lucatume is actually one of our devs. 🙂 ) Then I copied our version of that folder to the Easy Appointments plugin and voila, it works, both can be activated. (I didn’t test if they work properly, I will leave that to you. 🙂 )

I guess the Easy Appointments uses an older version of that library. You could share this info with the developer of the plugin, he might want to officially update that library.

Hope this helps, let me know.

Cheers,
Andras

[Author]

Posts