[Josh]

Hey Karl,

Thanks for reaching out to us!

To clarify here, it sounds like when you create the event you’re able to set the end date to the correct date and it displays properly on the front-end of your site. However, when you view the event on the backend it displays the wrong end date in the event settings?

As an initial step here, can you try following the Testing for Conflicts procedures to ensure there isn’t a conflict occurring within the dashboard (particularly something that could be impacting the datepicker display on the backend).

Let me know if that reveals anything new.

Thanks!

[Josh]

Hey Mike,

Thanks for reaching out to us!

Coming from version 4.0 to 4.1.2 shouldn’t break your site. The only reason it may would be if there were any modifications to the core files or customizations that could get overwritten in the process.

If there is any concern, it would be best to take a backup of the site prior to updating to the latest version.

Thanks!

[Josh]

Hey Dan,

Thanks for reaching out to us!

Your assumption there is 100% accurate. The deleted events are saved as a deleted_event post type. Here is a great response that will help you to delete these as well as prevent that behavior from persisting on the site.

Let me know if this helps.

Thanks!

[Josh]

Hey Barbara,

Thanks for reaching out to us!

You should be able to accomplish this by using the same snippet from above but by changing the 2 WooCommerce references to “Tribe__Tickets_Plus__Commerce__EDD__Main”.

Let me know if this helps.

Thanks!

[Josh]

Hey Francis,

Thanks for reaching out to us!

You can try adding suppress_filters => true to your query args to see if that helps. This will remove any customizations that we are adding for event queries.

Additionally, the main issue here is with the “eventDisplay” argument which defaults to “upcoming” to only show upcoming events. You can manually set that to “custom” within your query args as well.

Let me know if this helps.

Thanks!

[Josh]

Hey Curtis,

No problem. Yes, I’m able to see it on my local install on the single event view for both single and recurring events.

Thanks!

[Josh]

Hey Robin,

Thanks for providing that link!

It looks like your theme has a customized version of our plugin here (looks great too!). Take a look within your theme files and see if you have a “tribe-events” folder there. If so, take a look for a “single-event.php” file there or a “modules” folder there that has additional files that would make up the different sections on your single event template.

You should find a call to the event details there that you can modify the same way you were able to within the rest of the site.

Let me know if this helps.

Thanks!

[Josh]

Hey Tac,

I’m terribly sorry for the delay here. I missed this one in my queue last week.

Thanks for providing the additional information here. It looks like you do have the latest versions of all the plugins and you have previously mentioned that you did try deactivating the other plugins without success here.

Was hoping to see a little more detail from the PayPal debugging here however I will follow up with one of our developers to see if they have some more information to add here.

In the meantime, can you give me a little more detail about where in the checkout process the plugin fails for you? Also, are there any errors/warnings given when a transaction fails?

Also, do you have PayPal set up for general transactions within WooCommerce. This can occasionally add two PayPal buttons to a checkout. If so, it’s possible that the checkout is using the general PayPal checkout via WooCommerce.

Thanks!

[Josh]

Hey Sue,

Thanks for reaching out to us!

Check in your theme’s functions.php file and see if there is a function there that defines the default titles for the different views such as the archive.

If so, you can find the conditional that is outputting the “Archives:” and add an additional check there to not show on event pages. The conditional that you can use there is “tribe_is_event_query()”.

Let me know if this helps.

Thanks!

[Josh]

Hey William,

Thanks for reaching out to us!

The simplest approach for removing the Venue name from the front-end single event display would be to follow our Themer’s Guide and copy the views > modules > meta > venue.php file into your theme and deleting the venue name from displaying there.

Let me know if this helps.

Thanks!

[Josh]

Hey Ameet,

Sure thing!

I’ll go ahead and close this thread for now.You’ll still be notified here as we look into addressing this one.  If you have any further questions/concerns about this process, please don’t hesitate to open a new thread.

Thanks!

[Josh]

Hey Curtis,

Thanks for reaching out to us!

I just reviewed this on my local install and was able to see the “Edit Event” link in the admin bar with the latest version (4.1.2).

Is this still happening after updating to 4.1.2? If so, you can try following the Testing for Conflicts procedures which may help to locate any modified code that could be causing the issue here.

Let me know if this helps.

Thanks!

[Josh]

Hey Robin,

Thanks for reaching out to us!

Our single event templates don’t include a sidebar by default. Would you mind providing a link to an event so I can get a better idea of what may need to be modified here?

Thanks!

[Josh]

Hey Stefano,

Thanks for reaching out to us!

1. For the header search, it would be possible to do something with a map type search in the header, however it would take a bit of customization beyond what we’re able to provide here in support. Alternatives would be to add a basic search field that either searches just the “tribe_events” post type or have a field that submits to the events map view and passes the value to the location field.
2. Take a look at this starting point provided by another member of our team, Nico. It’s not a complete solution here but can help to get you pointed in the right direction.
3. This is something that is available within our Filter Bar plugin

Let me know if this helps.

Thanks!

[Josh]

Hey Emanuele,

Looking at the template which drives the event meta within the dashboard, it does appear that there would be a straightforward way to move those elements without overwriting the plugin file. There are hooks in there to add additional fields anywhere you would like though.

An alternative may be to look at the Community Events plugin and have the client enter events via the front-end form there. Those front-end templates can be easily overwritten within your theme following our Themer’s Guide to be any order that you would like.

Thanks!

[Author]

Posts