[Cliff]

GP, our ET / ET+ product is not a true “bookings” solution (like having available time-of-day slots that have limited capacity), although quite a few users do seem to use it this way via PRO’s recurring events functionality (which ET does not yet support).

Other than that, I believe the information I shared should give you a pretty solid understanding of what ET / ET+ is capable of and to help you decide whether you can get away with using the free one or if you’ll need to upgrade to ET+.

Please let me know if you have any follow-up questions on this topic.

[Cliff]

The RSVP fields come from this code: https://github.com/moderntribe/event-tickets/blob/4.3.3/src/views/tickets/rsvp.php#L98

You might be able to customize it for your needs.

Please let me know how things go.

Thanks.

[Cliff]

Another alternative would be to not use Event Tickets Plus’ Attendee Meta at all and instead customize the RSVP form, which is rendered from this code: https://github.com/moderntribe/event-tickets/blob/4.3.3/src/views/tickets/rsvp.php#L98

However, with this approach, I’d guess adding a Phone Number field would require extra coding to then display that information somewhere in the wp-admin area.

[Cliff]

Gotcha. Thanks for sharing your use case.

How about making your phone# field not required and then trying this CSS:

body.single-tribe_events .tribe-events-tickets-rsvp .tribe-event-tickets-plus-meta-attendee:nth-child(n+2),
body.single-tribe_events .tribe-events-tickets-rsvp .tribe-event-tickets-plus-meta-attendee header {
display: none;
}

Here are the before and after screenshots from my testing site.

Please let me know your thoughts.

[Cliff]

10-12 seconds load time is never “good”.

However, to say whether or not it’s “expected” is different based on each site’s configuration, traffic, theme, other plugins running, etc. so I can’t really answer that.

We do have a Performance Considerations KB article that may point you in the right direction, but I doubt it’ll be your silver bullet.

I see some of your events have 70+ recurrences. This is correct if you created an event that recurs daily for 70 days straight.

Users who typically have the “runaway recurring events” issue typically have hundreds in a single series, unexpectedly.

So, in the end, there’s not much I can help with here other than recommending your server be powerful enough and optimized for your usage. If you can’t get help from your web host and want to hire someone to help, you may want to check with Donald Grover from our list of freelancers.

[Cliff]

Thanks for the feedback. Please do keep me updated.

[Cliff]

No worries, Jim.

Here’s some CSS to make Month View quite a bit more print-friendly, but it’s imperfect. I’d still consider it a significant improvement thought:

https://gist.github.com/cliffordp/edec7dff1e2d92333682759d0b8de7de

Screenshots:

• Portrait — before: https://cl.ly/2n283O373C13 and after: https://cl.ly/1W2U1t342u2x
• Landscape — before: https://cl.ly/3u1C3V2a3v2s and after: https://cl.ly/473z0S2k3J1V

You’d have to adapt it for your theme’s HTML, but please do let me know your thoughts.

And please see this KB article for your shortcode question.

[Cliff]

I will share this with the developer assigned to this bug.

Thank you.

[Cliff]

Christopher, the “recently-published” is just that… recently published (based on published date, not event dates)

The code, by default, gets up to 20 recently published events.

[Cliff]

Jo, thanks for that thorough report.

I was able to reproduce the issue with All Day Events on Day View.

I’ll mark this ticket as Pending Fix, which means this thread should receive a reply once the applicable fix has been released. I cannot guarantee when it will be fixed as it’s in the development team’s hands now. They need to assign it, code it, test it, and schedule it for release.

I apologize for this issue and appreciate your understanding and patience.

[Cliff]

You could also try using a database dump plugin, like https://wordpress.org/plugins/wp-db-backup/ (instructions provided at https://codex.wordpress.org/Backing_Up_Your_Database#Using_WordPress_Database_Backup_Plugin)

(third-party, not guaranteed or supported by us)

And, again, try dumping before editing an event you think will experience this issue, then dump again if it does happen as you expect (to give me a before and after).

Thanks.

[Cliff]

Excellent! Thanks for confirming. 🙂

[Cliff]

If that plugin works the way it says it should, I think that’d solve your problem.

However, yes, I think they should be deleted by default, since https://codex.wordpress.org/Transients_API states they should get deleted after they expire.

Since the deletion of expired transients is outside the scope of our plugin’s functionality and we haven’t heard of this issue from others, I’d suggest following these recommended troubleshooting steps for your own site:

Could you please make sure all your Modern Tribe plugins (and WordPress core) are at their latest versions?

• Downloads / Version Numbers
• License Keys
• TEC Automatic Updates
• or TEC Manual Updates
• WordPress core updates

Once you verify you’re on the latest versions, please test to see if the issue is still happening for you.

If it is, please follow our Testing for Conflicts Guide (basically switch to Twenty Sixteen theme and deactivate all plugins and custom code other than Modern Tribe plugins) and see if that helps narrow down the cause of this.

If it doesn’t, please enable WP_DEBUG and WP_DEBUG_LOG and share any debug messages you see while changing tickets quantity, navigating your site’s home page, events page, single-event pages, and any other of your site’s pages relevant to this ticket.

Then, please share your System Information (while in Testing for Conflicts Mode). That will give me a lot of extra information to help diagnose the problem.

You might also see if you can spot any console errors at your site. (If needed, you may reference our KB article Using Google Chrome Developer Tools.)

Let us know what you find out.

Thanks.

[Cliff]

The free RSVPs only collects name and email address so we know to whom the email confirmation should be sent.

The ET+ add-on is required to enable Attendee Meta functionality.

Last but not least, we have a pretty great Refund Policy so you can buy one or many of our add-ons and thoroughly test them.

Let me know if you have any follow-up questions.

[Cliff]

I’d say this is possible with custom coding (getting user’s most recently-created event and pre-filling that same Organizer/Venue into the New Event form — or possibly even adding data to their WordPress profile field and pulling from their — or get their most recently-created Organizer and most recently-created Venue and pre-fill that).

We cannot provide such in-depth customization help, per our Scope of Support / Terms.

If there’s a code snippet you’d like me to put some eyes on or something else I can help you with, please update this ticket or create a new ticket if it’s a separate issue.

Thank you very much for your understanding.

If you need some coding help, you may want to ask your developer or reference our documentation and list of known customizers.

[Author]

Posts