[Victor]

Hi Julian!

Thanks for reaching out to us! 🙂

Sure you can do that. We have a snippet you should paste in your theme’s functions.php file >

https://gist.github.com/cliffordp/4f06f95dbff364242cf54a3b5271b182

Let me know how that works and if any other questions.

Best!
Victor

[Victor]

Hey Marcus!

Thanks so much for the kind words, on behalf of all of us at Modern Tribe. I’m super happy you could solve the issues! 🙂

If the “[day]” issue is solved for you that means the warning message should not show up anymore. But, with the WP_DEBUG_DISPLAY constant set to false, you won’t have any type of PHP warnings or errors showing up, even if they are still occurring. This setting is recommended to be ON in test / dev sites for debugging purposes, so having it OFF (meaning that it’s set to false) makes sense in your case because your site is live.

To make a final test, Would you mind setting the WP_DEBUG_DISPLAY to true again and see if the warning error shows up? If it doesn’t then it means we’re al set and we have no issues left so far. After this, you can change the debug display to false again. Let me know about it.

Regarding the “Location Search option” I see Courtney already responded back explaining the issue further. You should verify the “Disable the Event Search Bar” state in your events settings to make sure it’s unchecked. Please let her know about the state of this.

One final thing, I’ve checked your site and see you have the community submission form open for anyone to post an event. I’m not sure this is something you really intended this way, but just in case you didn’t notice, there is an option to only allow logged in users to be able to post new events. You can see this option by going to Events > Settings > Community tab and make the Allow anonymous submissions option unchecked.

As always, don’t hesitate to ask any other questions.

Cheers!
Victor

[Victor]

Right on! I’m so glad to hear everything is working smoothly and I appreciate you following up to let us know. Definitely keep us posted if any other questions come up and we’d be happy to help.

Cheers!
Victor

[Victor]

Hi Robert!

Thanks for getting in touch with us! 🙂

If you change the option selected for Default stylesheet used for events templates to Full Styles, then you should be able to see both top and bottom navigation links. You can change this setting by going to Events > Settings > Display tab. See here > https://cloudup.com/cZwFUaEN3Vn

Let me know if this works for you.

Best!
Victor

[Victor]

Hi Szymon!

Thanks for reaching out to us and for using our plugins! 🙂

Let me help you with that.

It seems that the css snippet you are using won’t work because you’re using a theme that may be changing the html code for the attendee information. Instead, you should try the following >

tribe-event-tickets-plus-meta {
display: table-row !important;
}

Let me know how that works.

Best!
Victor

[Victor]

Hey Joseph!

Thanks for letting us know about that! We’ll keep you posted for any update on the issue.

Cheers!
Victor

[Victor]

Hi Ewan!

Thanks for reaching out to us and for using our plugins! 🙂

You can accomplish that by installing the following extension from our Extensions Library > https://theeventscalendar.com/extensions/display-custom-html-specific-calendar-views/

You should install it like any other plugin and once activated you’ll be able to check / uncheck where to show the before and after html.

I hope that helps. Let me know if any other questions and I’ll be happy to help.

Cheers!
Victor

[Victor]

Hi Simon!

I’m sorry you are having this issue as well 🙁

It seems to be a conflict that appeared since the WooCommerce 3.0 update.

This bug has just been reported and it’s in the hands of the developers. So, I will change this thread’s status to “Pending fix” so the team will let you know as soon as the bug fix is released.

In the meantime, you could change the ticket product’s visibility to hidden by going to wp-admin > Products then edit the product created for the tickets and change the visibility setting. See here https://cloudup.com/cg4Od6sS4CR

I hope you can understand and we’ll appreciate your patience.

Let me know if you have any questions.

Best!
Victor

[Victor]

Hi Viki!

Thanks for reaching out to us and for using our plugins! 🙂

I’m sorry you are having this issue. I’ve just tested it myself and it seems to be a new bug that appeared since WooCommerce version 3.0.

I will create a bug report for this and link to this thread. The team will address this issue in one of our future maintenance releases and will let you know as soon as the bug fix is released. I can’t say an exact date for this as it’s in development team’s hands now. But, rest assured it will be taken care of.

As a workaround, you could change the ticket product’s visibility to hidden by going to wp-admin > Products then edit the product created for the tickets and change the visibility setting. See here https://cloudup.com/cg4Od6sS4CR

Let me know if you have any questions.

Best!
Victor

[Victor]

This reply is private.

[Victor]

Hey Dominic!

That’s great! Thanks for letting us know about it and for sharing the solution so other users can get a reference on this.

I’ll go ahead and close this thread but don’t hesitate to open a new one if anything comes up. We are always happy to help.

Good luck with your project!

Victor

[Victor]

Hey Iain!

I’m sorry that didn’t work. After some tests I realised it actually doesn’t work because the source / name variable is not the event name nor the event source name, and is instead a database generic name for the source record.

Like I said before, I do encourage you to post it as a new idea in our user voice. That is a great resource for us to see what the users needs are for new features to come.

My apologies for the misunderstanding.

Let me know if you have any other questions.

Best regards,
Victor

[Victor]

This reply is private.

[Victor]

You’re welcome Jason!

You do that and let me know how it works.

Good luck!
Victor

[Victor]

Hi Erick!

Thanks for getting back and sending all your system info.

Unfortunately, I’ve been able to reproduce your issue in my local installation and it seems to also be a conflict with the latest WooCommerce version 3.0. With all major releases like that one, these errors are very common as you can also see with the case of Smart Coupons.

We always recommend setting up a testing / dev site to test all the plugin updates and make sure it works before going to production.

I have created a bug report and linked to this thread, so the team will address it in a future update for the extension. I will change this thread status to “Pending fix” we will let you know as soon as it is released.

The error message you are getting is just a php warning, which does not necessarily mean something is not working. I can actually see the event info in the order screenshot. So, the workaround I would like you to try is deactivating these error messages by copy and pasting the following code in your wp-config.php file >

define( 'WP_DEBUG_DISPLAY', false );

you should paste it below this line of code >

$table_prefix = 'wp_';

Let me know how that works for you.

I apologise for this inconvenience and I really appreciate your patience.

Best!
Victor

[Author]

Posts