[Cliff]

You’re welcome. I’m glad you got a quick resolution.

Have a great week.

[Cliff]

Ah, yes, in that case, the file would be at /wp-content/plugins/event-tickets/common/src/Tribe/Utils/Post_Root_Pool.php

The “common” directory is code that is loaded whether you have The Events Calendar, Event Tickets, or both — to try to keep things DRY.

Of course, it’s not recommended to modify core plugin files so the location of this file is likely moot if following best practices.

I did log an internal feature request to allow customizing it to something like “RUNNER” with the idea that if “RUNNER” already exists, it’d instead generate something like “RUNNER1” instead.

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

[Cliff]

Andrey,

Our Themer’s Guide, which I wrote in bold, is really the only resource you need. The file for the Single Event view is /wp-content/plugins/the-events-calendar/src/views/single-event.php

Another idea is that you might try playing with this setting: wp-admin > Events > Settings > Display tab > “Events template” option — to see if changing it makes things work better for you. If this doesn’t work, you might also try asking your theme author how-to for the tribe_events custom post type.

However, if things aren’t working for you, you can post to our free forum to report a bug or seek assistance from the community, or you could buy Events Calendar PRO and get its features and our premium customer support.

Or, if you really just need someone to help code some customizations for you, you can reference our documentation and list of known customizers.

Thanks!

[Cliff]

Rhonda, I just now came across this existing feature request: https://tribe.uservoice.com/forums/195723-feature-ideas/suggestions/5954812-make-a-default-template-for-dark-sites

Please do add your vote there.

This allows us to gauge interest in this particular feature request, which helps us prioritize our development efforts.

[Cliff]

The “Z” at the end of “DTSTART:20170501T210000Z” means UTC.

21:00:00 UTC is 9PM UTC.

[Cliff]

Hi, Scott.

This sounds like a decent-sized customization.

You could request this as a new feature (or maybe search to see if the idea was already posted by someone else) at our plugins’ UserVoice page.

This allows others who are interested in that feature to easily voice their support. We frequently review suggestions there to find out which ones are popular, then we implement as many of them as we can.

If you post it / find it, feel free to link to it from here in case anyone comes across this forum thread in the future.

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

[Cliff]

Hi, Charmaine.

I haven’t heard of people using Dokan with our products before, but we have Community Tickets, which you can do split payments through if you get approved via PayPal.

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.

I hope this info helps. Let me know if you have any follow-up questions.

[Cliff]

Hi, Roger. Sorry you’re experiencing this.

This is scheduled to be fixed soon (hopefully 1-3 weeks).

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.

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

[Cliff]

Hi, Diane. Sorry you’re experiencing this.

I detected that this link ultimately redirects to https://hcplfl.evanced.info/signupadmin/eventsxml.aspx?dm=ical&nd=14

I put that in an iCal file validator and it did not validate due to using the “TITLE:” for each event. After removing all of those, it still did not validate. Please discuss this with the author/creator of this calendar for long-term viability.

Regarding the timing issue, my testing of Event Aggregator worked like this:

• As a sample, the “Medicare – WH” event is set to
  DTSTART:20170501T210000Z
  DTEND:20170501T220000Z
• My site’s timezone is set to Central Time
• The Event Aggregator preview looks like this: https://cl.ly/2i0s2K0D2I26
• Since this event starts at 21:00 UTC (which is 9PM UTC), it imported for me as 9PM UTC.
• Oddly, it didn’t import for me in Central Daylight Time (CDT), but it did still import accurately, as seen here: https://cl.ly/2u0i2w221e2E

It might help to add one or more of these timezone parameters to the iCal’s header:

• TZID
• X-WR-TIMEZONE
• X-LIC-LOCATION

http://mcb.berkeley.edu/seminars/mcb_seminars.ics is an iCal feed that has all three of these and they’re all set to “America/Los_Angeles”.

An example from that iCal feed.

• DTSTART:20170501T230000Z
  DTEND:20170502T000000Z
• This is 11pm UTC, which is 6PM Central Time and 4PM Pacific Time during DST.
• Here’s an import Preview: https://cl.ly/3X301W293R19
• and actual import: https://cl.ly/062N2v1r0h0q (imported correctly as 4PM Pacific Time)

Therefore, please consult the author/creator regarding what’s most appropriate for your iCal feed.

[Cliff]

Sorry to hear that, William.

Please follow our Testing for Conflicts Guide (basically switch to Twenty Seventeen 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]

You bet. Have a great day!

[Cliff]

Right. If you downloaded fresh copies from your My Account > Downloads, they’d be the latest versions and therefore none of the auto-update notifications would appear at this time.

To get the auto-updates in the future, make sure you have the correct license keys entered at wp-admin > Events > Settings > Licenses tab

Since this didn’t solve the issue you’re experiencing and this isn’t currently a known issue, I’d suggest following these recommended troubleshooting steps for your own site:

Please follow our Testing for Conflicts Guide (basically switch to Twenty Seventeen 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]

Math, thanks for reporting your situation with the Show Print Tickets extension.

This sounds like an error with the PDF, which should be addressed to the DK PDF plugin’s support, if at all available.

To provide them with a useful amount of information to help you, you might first try setting your site language to English (if it’s not already) and follow our Testing for Conflicts Guide (basically switch to Twenty Seventeen theme and deactivate all plugins and custom code other than Modern Tribe plugins, and DK PDF in this case) and see if that helps narrow down the cause of this.

Of course, if you find out something helpful, please report it back to us.

Antonio, thanks for sharing what worked for you. We have logged the feature request to make this work for non-logged-in attendees/respondents.

[Cliff]

Hi, Nadja.

Are you completely moving away from our product suite? If yes, you’ve still got a couple days left in your 30 day refund period.

===

Deleting The Events Calendar or its add-on plugins will NOT delete any of your data if you delete it via the WordPress plugin manager because that’s how we’ve decided to code our plugin.

To delete the bulk of the data from our plugins (there are likely still some other things that I’m not thinking of), you could take the following steps:

• Of course, we always recommend restorable database and file backups before modifying anything on your site.
• While The Events Calendar and its add-ons are still installed and active on your site:
  • delete all Events, Organizers, and Venues posts and empty each trash can
  • go through your Widgets and delete any of our widgets
  • use the wp-admin search for keywords like “tribe_events” through your posts, pages, and other non-Modern Tribe content types to find any of our shortcodes
  • go through your Menus and find any Custom Links menu items that go to pages like /events or /event/…
• Deactivate the Modern Tribe plugin(s)
• In your database, search your wp_options table for any option names LIKE “tribe%” and delete them
• Search through all of your database tables for anything like “%tribe%” and see if there’s anything remaining. To clean up anything else that’s found, it might be advisable to perform the action (e.g. a delete command) via wp-admin instead of directly in your database.
• Delete the Modern Tribe plugin(s)

Please let me know how this goes for you.

[Cliff]

Hi, Alfonso.

I’ll answer these in backwards order:

2)

We just recently added a hook making it possible to override the initial ticket number so it doesn’t have to start at 1.

Please reference this code snippet:

https://gist.github.com/cliffordp/91223c67e30e648257e47e50349d81f4

It is required to be a positive integer.

The applicable code is viewable at /wp-content/plugins/event-tickets-plus/src/Tribe/Meta/Unique_ID.php

1)

The part of that code that gets (or generates if not yet set) the prefix is the get_event_root() method in that file. The actual generation (if does not yet exist) happens in /wp-content/plugins/the-events-calendar/common/src/Tribe/Utils/Post_Root_Pool.php

Long story short, it needs to be unique and therefore it’s generated accordingly instead of being something like “RUNNER”… because then your next event you could not use “RUNNER” again.

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

[Author]

Posts