[Cliff]

Ah, yes. Well this makes more sense why the page source is so different from my testing.

Maybe the errors/suggestions I provided before was actually from our old code base (before my time) and not from conflicts or customizations.

You’ll need to update to the latest version and stay current on the latest release for us to be able to provide support for the issue.

In summary, I’m guessing the theme isn’t the problem, but I can’t say for sure. You REALLY need to use the latest version of all Modern Tribe plugins for functionality, security, and support reasons.

If it’s simply a style decision why you’re still on version 2, the current version allows minimalistic styling that you can then customize as desired — Tribe, Full, or Skeleton (i.e. get the same/similar look as version 2 while actually using version 3 code base).

I wish you the best with the plugin update(s). You can get the latest versions from your downloads page.

[Cliff]

Terry,

Our support forum works best when users create a separate topic for each issue they’re experiencing.

Here are my quick replies to each of your new questions:

1. The tribe search bar at http://buzzpro.com/events/ worked fine for me. I tested searching “career” and “professional” and both displayed the expected search results. Maybe your browser cache or settings need to be cleared. http://www.refreshyourcache.com/ may be of help for this.
2. You are currently subscribed to The Events Calendar PRO – Business, which allows up to 3 sites. You can view additional details at https://theeventscalendar.com/license-keys/
3. Support for the free “core” The Events Calendar is handled at https://wordpress.org/support/plugin/the-events-calendar. If you need priority support for it, you could start a ticket in the PRO support forum on this site.

I hope this helps. If you need follow-up support for any of these additional/separate questions, please post as a new thread by visiting https://theeventscalendar.com/support/post/

Thanks! 🙂

[Cliff]

Jameson, I’d lean toward no.

In my testing, I had a single event with tickets, changed it to recurring, and it essentially duplicated the new event (slug of ‘my-event-2’ instead of ‘my-event’) and the tickets weren’t attached to it.

So I think — not certain — when you edit reoccurrence settings (like if you wanted to change the reoccurrence pattern for an even that’s already recurring), I think it essentially deletes all the existing events and recreates them anew. Assuming this is correct (again, just a hunch, not something I tested/verified), I don’t know if it’d keep the tickets assigned to that.

Overall, your idea, while creative, isn’t the native way of editing recurring events.

For these reasons, I’d say you can try it but it wouldn’t be a supported way to go since the product does state that tickets for recurring events isn’t supported. If we edit how recurring events get modified, you could lose all those tickets being assigned to those events.

One way to go about it might be to ‘duplicate’ an event over and over and then edit each individual duplicate event.

One of these plugins may (or may not — untested/unsupported) come in handy if you choose to go that route:

• https://wordpress.org/plugins/post-duplicator/
• https://wordpress.org/plugins/duplicate-post/
• https://wordpress.org/plugins/duplicate-tec-event/

Good luck!

[Cliff]

Got it. Thanks!

I’ve submitted it to our developers to review. We’ll update this ticket after they have a chance to look into it.

Thanks for your patience and understanding.

[Cliff]

I see your site is using v2.4.3 of http://www.elegantthemes.com/gallery/harmony/, which is the current version of that theme (so not sure about your version 2 vs version 3 statement).

Anyway, I don’t know what customizations you may have, but the page’s source isn’t outputting things the same way my local testing site does so that’s why I think there must be custom code, but maybe there’s a plugin or theme conflict instead.

Another thing you could try is enabling WP_DEBUG and resolving any PHP errors you see while navigating your site’s home page, events page, single-event pages, and any other of your site’s pages relevant to this ticket.

To really determine if there’s an issue with our plugin, we’d need the site to have all non-Modern Tribe plugins deactivated and the theme would need to be one of the WordPress defaults, like Twenty Fifteen.

I know most people don’t want to do this on their live site. Maybe there’s a development/testing copy of your site you could play with.

Please let me know how you think I can best help / what else I can do for you at this time.

 

[Cliff]

Hey Kevin. I confirmed with our developers that https://theeventscalendar.com/knowledgebase/required-fields-for-events-submission-form/ has all the information you’ll need to reference.

Hints:

• Find the note about “square bracketed” fields on that page. If it helps you understand better, “square bracketed” fields are arrays — in other words, more than one choice is allowed.
• Because tax_input (i.e. categories) allows more than one choice, it is a square bracketed field and therefore this also applies: “…the above approach will not cause a (Required) label to be automatically printed out next to the relevant field – however you could achieve this by means of a template override.”

I hope this gets you the information you need to complete your customizations for the category field! 🙂

[Cliff]

Hey! So it turns out I forgot this is a stated limitation of Woo Tickets add-on.

Please note that right now, recurring events are not supported with tickets, and attempting to set up tickets on a recurrence pattern will not work. We’re working on this for the next major release, since we realize it’s in high demand, and will update this page at that point.
<cite>https://theeventscalendar.com/product/wordpress-wootickets/</cite>

You can see this feature request at https://tribe.uservoice.com/forums/195723-feature-ideas/suggestions/3685663-recurring-event-support-for-woocommerce-tickets

Please reply back to confirm you understand the situation.

Sorry about this. I know we’d all love if this functionality already existed.

Thanks!

[Cliff]

Hey! So it turns out I forgot this is a stated limitation of Woo Tickets add-on.

Please note that right now, recurring events are not supported with tickets, and attempting to set up tickets on a recurrence pattern will not work. We’re working on this for the next major release, since we realize it’s in high demand, and will update this page at that point.
<cite>https://theeventscalendar.com/product/wordpress-wootickets/</cite>

You can see this feature request at https://tribe.uservoice.com/forums/195723-feature-ideas/suggestions/3685663-recurring-event-support-for-woocommerce-tickets

Please reply back to confirm you understand the situation.

Thanks!

[Cliff]

Thanks for the details.

I see you’re using version 3.12 of the PRO plugin. Please update to the latest version (currently 3.12.5) from https://theeventscalendar.com/my-account/downloads/ and let me know if the issue gets resolved after updating.

Thank you.

[Cliff]

Thanks for the details. I’m double-checking with one of our developers and should get back to you within the next business day. Thanks for your patience.

[Cliff]

Kevin, I’m double-checking with one of our developers and should get back to you within the next business day. Thanks for your patience.

[Cliff]

Thanks for the link and the additional details to clear things up.

I can see there’s quite a bit of customization on your site so that’s sort of the first indicator something custom may be affecting things.

However, the biggest concern I have is noticing that a single event, such as http://www.birchmere.com/events/delbert-mcclinton-with-damon-fowler/, does NOT have the ‘ld+json’ data in the page source.

I believe the ‘ld+json’ data is how Google should be reading events (reference: https://developers.google.com/structured-data/rich-snippets/events) so I’m curious — have your customizations disabled printing the ‘ld+json’ data to the page?

Moving on, I see there is rich snippet information like this in your page source:

A couple of notes about this screenshot in regards to ISO 8601 date and time formats:

1. The hyphen between the date and time should be the capital letter “T”, not a hyphen. It’s apparent that Google is smart enough to read it despite this imperfection.
2. If Google reads the ‘startDate’ meta as 07:30:00, they’d be correct to read it as 7:30 am. 19:30:00 would be 7:30 pm since ISO 8601 requires the 24-hour time format.
3. It’s optional to add a timezone offset (e.g. “−05:00” for Eastern Standard Time) to the end of 19:30:00, but I believe, if omitted, Google assumes it’s the local timezone of wherever the event location is.

All those put together means the content=”…” from that screenshot should instead be 2015-11-05T19:30:00

Because there seems to be quite a lot of customizations on this site, I thought it best to provide you the general information you may need to resolve the “Google AM/PM” issue you initially brought up as the topic of this thread.

Please let me know if you think there’s anything else I can help with.

[Cliff]

Thanks for trying multiple things. Have you tried using the [tribe_mini_calendar] shortcode or just the widget?

If you haven’t tried that shortcode, please do and let me know how it works for you.

[Cliff]

You could add it to Dropbox, CloudApp, or any other such cloud file storage service. Then send us a private reply with the link. Once we confirm we’ve downloaded it, you could delete it from the cloud.

[Cliff]

Hi Antoinette.

Sorry your tribe_mini_calendar shortcode is formatting weird like it is.

I detected you’re using version 2.5.3 of the Divi theme.

The current version is 2.5.5. I tested that shortcode with the current version of Divi theme and it displayed just fine. Here’s a screenshot:

Please update to the latest version of Divi theme and let me know if that fixes the display issue(s) you’re having.

P.S. Don’t forget to clear your site’s cache and your browser’s cache after updating your theme.

[Author]

Posts