[Barry]

One other thought: your system information notes that you have a “must-use plugin” (that is, one which cannot be deactivated) called System Plugin.

I suspect this is a plugin your host added, which isn’t unusual. I’m curious though, does this provide you with any caching capabilities or, more simply put, do you see a button anywhere in the admin environment that lets you clear the cache? If so and you use this, does the information you see in the attendee screens resolve to what you would expect?

[Barry]

I don’t think I need admin access right away (and generally we don’t login to customer websites unless absolutely critical) but I did just make submissions on both of those pages – which seemed to be successful.

Even for the second of those, I did receive a ticket email and stock on the single event page appeared to reduce as expected. Do you still not see any records in the attendee screens?

[Barry]

Hi @sfbirthcenter,

I think there may have been a slight mix-up with your previous support exchange and the bug we thought you were experiencing may in fact have been separate from what you are actually hitting up against.

Your situation is not something I can replicate on a clean testing site, so I have a few ideas for us to try:

• Looking at your system information, nothing jumps out as being particularly worrisome except perhaps “WP Meta and Date Remover” … can you temporarily deactivate that plugin, create a new test event and some RSVP tickets and see if you still hit the same problem?
• Once you’ve created the test event/tickets, can you provide a URL (by private reply if you prefer) so we can try using it ourselves, in case that yields any useful debugging information?
• If all else fails it may be worth creating a clean testing/staging site … in a typical hosting package (such as those provided by GoDaddy, which you are using) it is generally very easy – a matter of a few clicks – to install a new WordPress site in a subdirectory (ie example.com/test-site) and I’m sure their team would assist you if needed … we could then troubleshoot in there and/or verify if the same problem can be replicated using only our plugins and a default theme – and go from there

Are you happy to get started with these steps? I realize the problem must be very frustrating and we’re keen to help, but it may take a little work to get to a solution.

[Barry]

This reply is private.

[Barry]

Checking in on this … we did just make some changes which ought to have improved this problem (the changes were made on our server, so to benefit from this you don’t even need to update things locally).

To that end, can you confirm if you are still experiencing the problem or if it is now resolved?

[Barry]

Hi there!

Though I can see the most recent snippet Jeremy shared with you (“.tribe-mini-calendar td.mobile-trigger”) I don’t actually see the initial snippet that he shared … before we go any further, can you pop open Appearance ‣ Customize ‣ Additional CSS one more time and ensure it wasn’t accidentally deleted?

Thanks!

[Barry]

Unusual!

We do have a current bug report for a very similar problem, but it doesn’t actually impact RSVP-type tickets. I’m wondering a couple of things here:

• If you clear your cache (or disable caching completely) is the problem resolved?
• Can you update all of your Modern Tribe plugins to the latest versions and see if that helps?

Thanks!

[Barry]

Great – thanks for your patience while we worked on this.

If anything else crops up, please do create a fresh conversation and one of the team will be only too happy to assist further 🙂

[Barry]

This reply is private.

[Barry]

Great 🙂

[Barry]

Hi Kevin and Brent.

Unfortunately this is a known bug however it’s one we’re actively working on. As soon as we have news of a fix, we’ll drop an update in here 🙂

[Barry]

Hi Brent,

This was not resolved in our most recent release, we’re still working on it. As before, we’ll drop an update in here (and in other related topics) once we have news of a fix.

There is no reason, though, to add the same question repeatedly to multiple topics 🙂

[Barry]

Hi Brent,

We’re working on resolving this but haven’t done so yet. As before, we’ll share an update here once the fix is ready.

Thanks for your patience!

[Barry]

Hi Gray,

Unfortunately, this is a known bug … we hope to resolve it soon.

I’ll go ahead and attach this conversation to our bug report: that way, the developers can review the specific error message you shared and we will also be able to update you once the fix is ready.

Thank you for your patience in the meantime.

[Barry]

Hi Drew,

Thank you for the details of the error.

I believe you are correct, it’s the same issue Samuel reported and it matches a currently open bug report on our issue tracker.

As soon as we have an update to share, we’ll drop a note in here 🙂

[Author]

Posts