[Barry]

This reply is private.

[Barry]

My apologies, firstly, for the further delay: many of us were unavailable last week but things should progress more smoothly from here onwards.

This is a puzzling problem and I’m still unsure what is causing it and am unable to replicate the same issues on my side. In my last reply, I proposed a different way of testing this:

I wonder if it would be possible for you to create a test site and work there instead.

A test site can be as simple as a fresh WordPress installation in a subdirectory (ie, example.com/test-wp). You could then start by adding just The Events Calendar and Events Calendar PRO (and nothing else!) and see if you can replicate the same issue there. Remember, there is no need to add your license key if you do this ?

Is that something we can do?

That would give us a clean environment in which to test and could be a useful contrast from the live site. If you do this and find you can create a recurring event that boasts the same problems as you have already described, please pause and link me to the test site so I can take a look.

Thanks!

[Barry]

Thanks, Anne. While gathering votes on the matching feature request isn’t quite a prerequisite it can certainly help us to gauge demand 🙂

If we can assist you with anything else, please do create a new topic and one of the team will be only too happy to assist.

[Barry]

Hi Thomas,

Apologies for the further delay: many of us were unavailable last week due to our annual team trip.

Thanks for the visual. Can you clarify though if this is an ongoing problem that is too big to resolve manually, or that is proving impossible to resolve manually?

Thanks!

[Barry]

Hi Murray,

Apologies for the delay in getting back to you: this does seem to be a bug and I’ve logged it for further attention. In the meantime, you should be able to workaround this by using the following code:

https://gist.github.com/barryhughes/f17acb877500e4b777ac8c701baff16f

This could be included via a custom plugin or by adding the code to your theme or child theme’s function.php file if that’s an approach you are happy with.

We’ll aim to update this topic as soon as a substantive fix is released (at which point you can remove the above workaround).

I hope that helps!

[Barry]

Thanks for the update.

Did you have any success when running through our standard troubleshooting steps? If you were unable to perform those steps on your live site, I wonder if it would be possible for you to create a test site and work there instead.

A test site can be as simple as a fresh WordPress installation in a subdirectory (ie, example.com/test-wp). You could then start by adding just The Events Calendar and Events Calendar PRO (and nothing else!) and see if you can replicate the same issue there. Remember, there is no need to add your license key if you do this 🙂

Beyond that, I’d love some more clarity on a few points:

• Is the problem that when you try to edit an existing recurring event the editor never loads?
• Or is it that after editing the event and hitting Update the process doesn’t seem to complete?
• Can you provide an example of the sort of recurrence pattern you are using? Is this a problem with a very simple pattern, such as an event that recurs weekly for perhaps only 1 or 2 weeks?

Thanks!

[Barry]

Awesome 🙂

This is linked to the bug report (on our internal issue tracker) so, as soon as there’s been some movement on the problem, we’ll update this and all other attached forum topics to let everyone know.

Thanks again!

[Barry]

OK, thanks for the update.

your release notes mentioned https://

This is true, though the changes were in relation to static links embedded in the plugin (we link to the wordpress.org forums and other places from the help pages, for example, and updated those to use the HTTPS protocol) — we didn’t implement anything in this release that would impact URLs stored in the database such as post content or custom nav links and we didn’t modify anything relating to the dynamic generation of event URLs.

Again, it is possible we inadvertently introduced something but I just don’t see it at this time. To be safe, let’s keep this topic open for the time being in case we, you or another community member hits on something useful that might help.

Thanks!

[Barry]

Hi Tom – thanks for taking the time to share those super links 🙂

Armed with all of that knowledge, is it possible for you to create a custom link as outlined in my OP in an https/ssl environment and test the issue?

Absolutely and – my fault for not being clearer – I already did so but was unable to reproduce. What I was hoping to discover was if you had done something else or if there was an angle I had missed but, based on the feedback in your last reply it sounds like I hit all of the key components already.

Since we’re unable to replicate and are not currently seeing comparable reports from other users, I wonder if this is the result of a conflict or otherwise is specific to your own site?

Here’s what I’m going to do:

• I’ll move this topic from the Event Tickets Plus forum to the Community Events forum – apart from being a better home for Community Events related issues like this one, it may also help others who are experiencing the same thing to find it and chime in (don’t worry, though, the actual topic URL will remain the same so you shouldn’t have problems locating it after it is moved)
• We’ll keep an eye out for any similar reports coming in and see if we can gather the information we need to replicate on our side from there

On your side, how much of a problem are you left with here — is this going to require a large clean-up effort? I’d love to have a better idea of the scale of the problem so we can prioritize accordingly.

Last but not least, I apologize for any further delay: team commitments mean we’ll be operating at a reduced level of service in the week ahead.

[Barry]

This reply is private.

[Barry]

I’m sorry for the further delay on this one, Teri.

Unfortunately we were unable to squeeze the fix in this time round. Bear with us a little longer and we’ll do our best to roll out a fix 🙂

[Barry]

Hi Brian,

I realize that I apologize for the delay. This issue is still pending: unfortunately, we were unable to squeeze the fix in this time round.

A solution such as Say What may offer you a temporary solution to this issue until we can deliver the fix in an upcoming maintenance release.

[Barry]

Thank you, Anne – we appreciate it 🙂

[Barry]

Happy to help 🙂

[Barry]

Thanks for your patience so far, Adam.

You are right – there’s a hole in our logic here and the fact that the ticket/attendee record in question no longer exists should be flagged up when an attempt is made to check them in via QR code.

I will log this and we’ll do our best to get a fix in place in an upcoming maintenance release — our apologies for any inconvenience in the meantime.

[Author]

Posts