[Josh]

Hey Nicky,

Thanks for reaching out to us!

For the embed on the event page, are you using some custom code to modify the output there? If so, would you mind sharing a snippet of that particular code?

Additionally, take a search through your theme files and see if they have any default modifications within a “tribe-events” folder or any modifications to iframes added anywhere within the theme.

Let me know if you find anything there.

Thanks!

[Josh]

Hey Ameet,

Thanks for reaching out to us!

Definitely sounds like a strange issue here. I’ve created an internal bug ticket for this one and have added this thread to that ticket. You’ll be notified here as we make progress on addressing this one.

In that thread, I added your suggestion for disabling the ability to delete as well as the possibility of disabling future sales (since I imagine is the reason why organizers are deleting the ticket?) without deleting the core WooCommerce product associated with that ticket.

I apologize for the inconvenience here. If you have any questions/concerns about this process please don’t hesitate to reach out.

Thanks!

 

[Josh]

Hey Kevin,

Thanks for reaching out to us!

Would you mind sending a screenshot of your current field section that you would like to make required? Want to verify that I’m fully understanding the direction you’re wanting to go.

Also, looking at the knowledgebase item you reference, I see that we do have some notes for that one requiring some updates and potential code need changes. We’ll look into that in conjunction with this thread to ensure that it continues to be a solid starting point for customizations such as these.

Thanks!

[Josh]

Hey Lee,

Awesome! I’m glad we were able to get to the bottom of that one!

With the previous update there was an issue where the folder names were different for the plugins. With the latest update, those were fixed. However, when WordPress updated the plugins the folder changed and the path was no longer recognized so the plugin may have been automatically deactivated then since the “activated” version that WordPress recognized no longer existed. Should be good to go moving forward though.

I’ll go ahead and close this thread for now. If you have any further questions, please don’t hesitate to open a new one.

Thanks!

 

[Josh]

Hey Carl,

I apologize for the delay here. I was out on some unexpected medical leave.

I want to also apologize for the continued issues here with the plugin. Looking through the responses, I believe I see a couple of known issues that I can help you with.

• To start, once the events were imported and then deleted it caused the issue of the importer not recognizing events from the feed associated with the original import there. This is due to the events not being completed deleted by the system and saving that information as a “deleted-event”. Here is a great response from our team member Brook on how to address this particular issue.
• For the admin notices, would you mind trying deactivating the plugins and reactivating to see if that causes the admin notice for the update to go away?
• Finally, for the import issues would you mind doing a quick test with http://wpshindig.com/events/?ical=1 to see if your site is able to read the file there? If not, try following the Testing for Conflicts procedures to see if there is a conflict here which is causing the import to fail.

Let me know if this helps.

Thanks!

 

[Josh]

Hey Alan,

Thanks for reaching out to us!

This definitely sounds like a frustrating issue to be having here. Did the failure happen around the same time or did it occur at different time throughout the day? Would you mind trying again to see if there was a temporary connection issue when attempting the update.

If that doesn’t work, it may be best to delete the files from your server and download the latest version of the plugin from our site here and uploading directly.

Let me know if this helps.

Thanks!

[Josh]

Hey Lee,

Thanks for reaching out to us!

Looking at the latest version of the plugin, the option to set the latitude and longitude for the venue is still available on the venue edit screen. It is the last option on the page and the fields for the values will display after selecting the associated checkbox to use those fields.

Are you able to see those fields when looking at the venue edit screen with Pro activated?

Thanks!

[Josh]

Hey Alex,

Thanks for reaching out to us!

I’m sorry to hear that you’re having issues with the latest version of the plugin. With this particular issue, are the orders not showing at all within those reports or is it that some information about the orders is missing from the report?

Thanks!

[Josh]

Hey Hugo,

Thanks for reaching out to us!

Definitely seems like a strange issue. When I click on the link directly to “/events” on your site, I’m directed to the calendar view with a normal, functioning display.

When you experience the issue, are you clicking to the calendar from somewhere else on your site?

Thanks!

[Josh]

Hey,

Thanks for reaching out to us!

It may be a little tricky to utilize a redirect for a use case such as this. You could potentially have a good solution with a redirect here, however my initial assumption would be that you might get headers already sent errors when trying to run the redirect after handling the conditionals for the events.

An alternative may be to hook into the event publish and set the events assigned to the categories that you would like private as private status. This way, users that have access (you can filter that access as well to subscribers if needed as well) would be able to see those private events within the calendar views while everyone else would just see the public events.

I’m sorry I wasn’t able to give you a direct solution here however I hope it helps to get you pointed in the right direction.

Thanks!

[Josh]

Hey Paula,

Thanks for reaching out to us!

I’m sorry to hear you’re having trouble using the importer plugin. Would you mind sending us the link that you’re trying to import from so we can do some further testing here.

Thanks!

[Josh]

Hey Christopher,

Thanks for reaching out to us!

I tested this one out and was able to replicate the issue of the “tribe_events” post type being included in the query when tags were used.

I apologize for the inconvenience of this particular issue. I’ve created an internal bug ticket for this one and added this information to it. You’ll be notified here as we make progress on addressing this one.

If you have any questions or concerns about the above process, please don’t hesitate to reach out.

Thanks!

[Josh]

Hey Eran,

Thanks for reaching out to us!

To clarify, it sounds like you want to use the product attributes feature within WooCommerce to add additional information to a ticket. However, you don’t want this information to show up on the event details for that ticket. You only want it to show up when the WooCommerce product shortcode is used?

If so, this is unfortunately a customization of WooCommerce features that we’re unable to provide direct support for here in our forums. However, to help get you pointed in a good direction, check out this thread on stack overflow which seems to be exactly what you’re looking for.

Thanks!

[Josh]

Hey Robert,

Glad you were able to get back up and running again here! But definitely strange about that odd downtime.

I’ll go ahead and close this thread for now. If you have any further questions or if the issue comes back up, please don’t hesitate to open a new one.

Thanks!

[Josh]

Hey Keith,

Thanks for reaching out to us!

This is a great question! After a quick look through the files, I’m not seeing any hooks that we’ve added that fire after the import. However, I’ll check with one of our developers to see if they’re aware of anything that would be useful here. If not, we’ll get a feature request added for the ability to hook in after the import.

Thanks!

[Author]

Posts