[Cliff]

Hi, Mark.

Thanks for your business and detailed report.

I believe you’re reporting a known issue when the WordPress Address (URL) and Site Address (URL) are not both HTTP or both HTTPS.

This is a bug that will be fixed soon.

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.

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

[Cliff]

Hi, Ben.

It sounds like you’re interested in Event Tickets and Event Tickets Plus.

Event Tickets Plus works with WooCommerce (or a few other eCommerce plugins) so you might look into a CASHNet payment gateway for WooCommerce.

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

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]

Hi, Bryan.

That plugin is not ours (third-party, not guaranteed or supported by us).

I also didn’t find the discussion on our forums recommending this plugin.

We do have a KB article basically stating we don’t test all the WooCommerce add-ons out there.

Therefore, I cannot provide assistance for that plugin.

[Cliff]

Hi, Mel.

Thanks for your detailed question.

The “next” link only gets hidden if there aren’t any future events, since we wouldn’t want a visitor to click infinitely to the next month to never find any events.

I see your site has targeted .tribe-events-nav-previous, .tribe-events-nav-next to add a colored border. I think you should target .tribe-events-nav-previous a, .tribe-events-nav-next a instead.

I think this would be more along the lines of what you’re wanting to have appear.

Please let me know how this goes for you.

[Cliff]

Hi, Charles.

This definitely sounds like a JavaScript conflict.

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

If that doesn’t help, I’d suggest following these recommended troubleshooting steps for your own site, since this isn’t currently a known issue:

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.

Let us know what you find out.

Thanks.

[Cliff]

Hi, Sara.

This is a bug we discovered recently.

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]

Hi, Blake. Sorry to hear this.

I see you have a “100 imports per day” license for Event Aggregator.

If you’re hitting your limit, you could upgrade to a higher-level plan.

Other than that, could you please explain other errors in further detail, including any links, screenshots, or video screencasts that you think may assist me in helping you.

Thank you.

[Cliff]

Hi, Kenny.

Thanks for your question.

The “/event/MM-DD-YYYY/event-name/” format would probably be problematic if you later activate our PRO add-on because of how it changes the link for recurring events. Here are some examples from our demo site:

• http://wpshindig.com/event/codeforcuritiba-hack-night/all/
• http://wpshindig.com/event/codeforcuritiba-hack-night/2016-12-07/

I think a better way to accomplish your end goal might be to programatically change the full slug, to something like this: “/event/event-name-YYYY-MM-DD/” (or another format)

It likely wouldn’t be super difficult to hook into save_post_tribe_events (see the Codex) and update the slug with that event’s date.

However, if your event changes its date, then people who bookmark the URL may hit a 404.

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

[Cliff]

Hi, Randy.

Sorry you’ve been having to deal with this. I haven’t personally heard of this theme.

We do not provide theme-specific help, per our Scope of Support / Terms, unless it’s a WordPress default theme like TwentyFourteen, TwentyFifteen, TwentySixteen, etc.

If you need some coding help, you may want to ask your developer or reference our documentation and list of known customizers. Of course, you could contact your theme support or you could just use a different theme.

Thank you very much for your understanding.

[Cliff]

Hi, Jeff.

That is an odd thing. It’s likely from your theme or a conflicting plugin.

However, here’s some CSS to fix it:

#tribe-community-events form #event_custom br {
display: none;
}

You can add custom CSS code via your child theme’s style.css file or via a third-party plugin (not guaranteed or supported by us), like:

• SiteOrigin CSS (helps you visually build CSS selectors via its Inspector and Visual Editor, if that’ll help you)
• Simple Custom CSS
• Jetpack (supports regular CSS and the LESS and Sass pre-processors)

If you’re not a CSS expert, Jetpack’s Custom Design reference may prove helpful.

Please let me know how it goes for you.

[Cliff]

Raphael, I’m sorry to hear about your multiple frustrations using our products. Of course, that’s never our intention.

We’d be glad to assist with each of the issues you’ve been dealing with (please create a separate forum thread per issue). Maybe they’re bugs we haven’t discovered yet, or maybe there’s a known workaround we can assist you with.

Please let me know if you think there’s another way we can help, too.

Thanks.

[Cliff]

Sure thing. Have a great week!

[Cliff]

I obtained a copy of the latest Avada (v5.0.5) and found avada_get_page_title_bar_contents() in /wp-content/themes/avada/includes/custom_functions.php

You might try digging deeper there or contacting Avada support to ask further.

I hope this helps.

[Cliff]

I’m glad to hear. Have a great week!

[Cliff]

I attempted an import yesterday that didn’t work but this morning it did work. Could you please try it again? If it still doesn’t work, please provide the URLs that aren’t working for you.

Thank you and sorry about the troubles here.

[Author]

Posts