[Cliff]

Tracey, we’ve published the update to https://theeventscalendar.com/extensions/list-venues-and-organizers-shortcodes/

Thanks for helping make our products better.

Please try it out and let me know how it works for you.

[Cliff]

Could you please send me the zip of your plugin or a gist link of your widget class?

[Cliff]

This reply is private.

[Cliff]

Gotcha. I thought you did like some people and tried to load your own Google Maps script from a theme or another plugin and didn’t load ours.

Since you’re just using our stuff “out of the box” and it’s not working, please refer back to the instructions in my initial response.

Although not fun sometimes, it’s important to follow those very closely.

[Cliff]

Glad to hear and thanks for letting us know.

[Cliff]

Hi, Mathew. I’ve seen several tiny bugs logged regarding widgets, such as this one, so I have pinged the planning/development team to see if we can get some traction because, as a group, they maybe warrant some sooner-than-later attention.

That being said… I marked this thread as Pending Fix, which means it 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. Sorry you experienced this.

The way recurring events happen is that each event within the series is a child post of the parent/series post.

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.

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.)

Whenever troubleshooting, it’s best to enable WP_DEBUG and WP_DEBUG_LOG (which will create a file on your server at /wp-content/debug.log if there are any WP_DEBUG messages) and share any debug messages you see while trying to replicate this issue.

If there’s nothing obvious (such as a console error or WP_DEBUG message) pointing you to what might be the problem, 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.

Note that https://wordpress.org/plugins/plugin-detective/ may prove helpful as well. (third-party, not guaranteed or supported by us)

Of course, we always recommend restorable database and file backups as well as performing modifications first on a staging site before modifying anything on your live/production site.

If you still need assistance with this, please share your System Information (while in Testing for Conflicts Mode) in a Private Reply.

That will give me a lot of extra information to help troubleshoot this.

Let us know what you find out.

Thanks.

[Cliff]

Hi. Sorry this is happening. We recently changed the way assets are loaded: https://theeventscalendar.com/maintenance-release-for-the-week-29-july-2018/

This may affect some themes that integrate with our plugin. Please contact Beaver Builder regarding this.

Note that we do not integrate with themes, per our Scope of Support / Terms, but we are aware of Beaver Builder integrating with our plugin, which is great: https://theeventscalendar.com/design-an-event-calendar-beaver-themer/

[Cliff]

Hi, Mini.

I see you’re referring to https://theeventscalendar.com/knowledgebase/stylesheets-and-page-templates/

The “Default Page Template” would depend on your theme. Basically, your events would appear just like the rest of your Pages — sidebar and such — but its appearance would change per theme.

The Events Template option loads our own template, as you determined.

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

[Cliff]

Hi. The way to do this is via tribe_asset(), which is in /wp-content/plugins/the-events-calendar/common/src/functions/template-tags/general.php

You can see some examples of its usage within /wp-content/plugins/the-events-calendar/src/Tribe/Assets.php

And here’s something that might be a helpful starter snippet for you:

tribe_asset(
tribe( 'tec.main' ),
'my-widgets-style',
'full-path-to-the-file',
array(),
'wp_enqueue_scripts',
array(
'groups' => array( 'events-styles' ), // Passing the group will ensure it will load with the widget
'priority' => 15,
'conditionals' => array(
array( $this, 'should_enqueue_frontend' ),
),
)
);

Please let me know how this goes for you.

[Cliff]

Hi. You should be able to call tribe_get_ical_link() wherever you want it.

https://github.com/moderntribe/the-events-calendar/blob/4.6.22/src/functions/template-tags/ical.php#L24-L47

Please let me know how this goes for you.

[Cliff]

Hi. Please see these settings: https://theeventscalendar.com/knowledgebase/woocommerce-specific-ticket-settings/

If you still can’t figure it out, please share your System Information in a Private Reply.

That will give me a lot of extra information to help troubleshoot this.

[Cliff]

Oh, but adding target=”_blank” wouldn’t solve the issue of filtering the link (such as to use that other extension you linked t0)

Basically, here’s the issue: the Venue and Organizer names and links should use our own functions:

• tribe_get_venue()
• tribe_get_venue_link()
• tribe_get_organizer()
• tribe_get_organizer_link()

… instead of get_the_permalink() and get_the_title() so our filters get applied, which would allow that other extension and that gist snippet to take effect on them.

[Cliff]

Hi, Tracey.

The reason that gist doesn’t work there is because get_the_permalink() is used to get the link: https://github.com/mt-support/tribe-ext-list-venues-organizers-shortcodes/blob/2.1.0/tribe-ext-list-venues-organizers-shortcodes.php#L151

…which isn’t quite the best way.

I’ll log this bug internally so this thread should get a reply once an update for this issue is released. For now, I’d recommend just modifying the extension’s code to add target=”_blank” as you want it.

Thanks for the heads up.

[Cliff]

We cannot troubleshoot your customizations, but if you share your code — particularly the part about “replaced all of the APIs” — then I might be able to offer some suggestions.

[Author]

Posts