[George]

Hey Stu,

Thanks for reaching out.

Our ticketing plugins are not quite optimized for online events like webinars; they’re built for physical events, specifically.

While they probably could be tweaked and modified to better support online events, something like Restrict Content Pro may work better for that sort of thing, as it is specifically meant for allowing access to online content, events, links, etc…

Please let me know if this helps and if there are any other issues or questions I can try to help with! 😀

— George

[George]

Sorry to hear this, @Anne Marie!

Have you installed the plugin on your site?

If you’re not sure, please follow the process described in this guide for getting started: https://theeventscalendar.com/knowledgebase/new-user-primer-the-events-calendar-and-events-calendar-pro/

Please let me know if there are any specific follow-up questions in response to that guide that I can try to help with!

— George

[George]

This reply is private.

[George]

This reply is private.

[George]

Thanks for confirming this @brenda—this indicates that your custom theme is the source of the problem, and has code within it that is breaking out plugin.

We do not make that theme and so we don’t know the code within it, nor can we fix that broken code, but that is the source of the problem here. Please contact the support team for that theme and report this issue—they should be able to help fix their theme’s plugin-breaking code promptly!

— George

[George]

Hi Stanley,

Thanks for your update here. I wanted to let you know I have reported this thread to a developer on our team who will be helping me take a closer look at your file and these issues.

As we head into the weekend, I apologize for the pace of this investigation. As noted above, this is an odd set of issues that we can’t recreate with other files and so it’s taking some time to investigate.

Please respond to each of the three questions that follow:

---

Question #1

Indeed the “STATUS: CONFIRMED” field exists in the ICS files—this is what is being reported as an “error”.

You mentioned above that there is no “status” column in your original CSV file. And so the pesky “STATUS: CONFIRMED” field in your ICS file doesn’t come from your CSV files.

• Where is it coming from, then? Do you happen to know? I cannot generate CSV files from my local site or anything with a “STATUS: CONFIRMED”-type field. I apologize for harping on this “STATUS: CONFIRMED” field, but it’s the only thing standing out as problematic here.

---

Question #2

In regards to your questions about what I mean by duplicates, I am talking about events with the same title and same date—”same date” meaning same time, day, and year. So if there are multiple instances of “Event A” on May 1, 2017, then that would be an example of duplicates. But if there’s an instance of “Event A” on May 1, 2017, then another instance of it on May 1, 2018, this would not be a duplicate.

• Are there any such duplicates in your file? Yes, I am checking manually myself, by given the size of the file that is taking some time and so I am just curious if you have any knowledge of this yourself.

---

Question #3

• Can you please share the original CSV file with us? Upload it to Dropbox, Google Drive, CloudUp, etc., and we’ll download it from there.

---

Thank you for your continued patience and persistence,
George

[George]

Thanks for posting this, @Mathew!

@ronald and @sean, @Mathew’s code may be helpful—definitely try it out!

— George

[George]

Here’s the paradox, folks:

• On one hand, speedy fixes are desired.

• On the other hand, fixes that are sloppy end up begetting more problems, which is NOT desired.

And so if we work quickly and too fast, we are more apt to publish something sloppy that creates more problems. Which understandably induces customer dissatisfaction.

And yet if we work more diligently and do more stringent processes of testing, it adds time to the release process, which also understandably induces customer dissatisfaction.

---

I emphasize the word “understandably” in both sentences above because I genuinely understand your frustrations. Nobody is happy about these bugs—yes, including us!

We are working hard on fixing this bug and a number of others; I am happy to report that this particular bug is now in the process of QA and testing.

Thus, this fix will hopefully arrive next week.

Your patience means a lot and I am genuinely sorry for the trouble here. The fix is coming soon.

Please let me know if there are any other issues or questions I can try to help with in the meantime.

Sincerely,
George

[George]

I am genuinely sorry for the existence of these bugs, Corinne. I am sorry if things come across with a “too bad” attitude, because in my opinion we try to do the exact of that:

• We admit there is a bug.
• We set threads like this to “Pending Fix”
• We actively communicate when the fix is available.

☝️ This is far from “casual”, in my opinion—we are working hard on a bug fix will alert you when it’s available! 😀

It would of course be ideal if the bug did not exist to begin with. Nobody can argue that. 😉 But in terms of fixing the bug and communicating when it’s available, we take both things seriously and are actively working on fixing the bug you reported here.

Please stay tuned to this thread for updates about that bug fix, and please let me know if there are any other issues or questions I can try to help with in the meantime.

Sincerely,
George

[George]

I appreciate the feedback, Kristen, and do agree that it should be easier to specify a number!

Best of luck with your project,
George

[George]

This reply is private.

[George]

Hello!

I was able to produce a snippet that makes the featured image required for submitting a Community Event. That snippet is this:


add_filter( 'tribe_events_community_required_fields', 'tribe_community_require_image_to_submit', 10, 1 );

function tribe_community_require_image_to_submit( $fields ) {

if ( ! is_array( $fields ) ) {
return $fields;
}

$fields[] = 'EventImage';

return $fields;
}


☝️ Try adding this to your theme’s functions.php file and it should make featured images required.

You will have to take the reins on further refinement of this and/or other customizations, but I hope this helps! 😀

— George

[George]

Hello!

I was able to produce a snippet that makes the featured image required for submitting a Community Event. That snippet is this:


add_filter( 'tribe_events_community_required_fields', 'tribe_community_require_image_to_submit', 10, 1 );

function tribe_community_require_image_to_submit( $fields ) {

if ( ! is_array( $fields ) ) {
return $fields;
}

$fields[] = 'EventImage';

return $fields;
}


☝️ Try adding this to your theme’s functions.php file and it should make featured images required.

You will have to take the reins on further refinement of this and/or other customizations, but I hope this helps! 😀

— George

[George]

Hey Daniel,

I’m sorry to bear this news, but this customization was much harder to pull off than expected and we have not been successful in creating it. 🙁

I won’t be able to come up with a solution here like we tried.

I am sorry to disappoint! Please let me know if there are any other issues or questions I can try to help with.

Sincerely,
George

[George]

Hey @adage, very sorry for the delayed reply. I have tried to replicate these issues but what I have consistently found is that in all calendar views our plugins actually do list child event categories and even grandchild event categories without issue!

[Author]

Posts