[Josh]

Hey,

I followed up with our team and we were able to recreate the issue with chrome on iPhone. I’ve created a bug ticket for our developers to look into this issue. You’ll be notified here as we make progress on this one.

I apologize for any inconvenience this issue has caused.

Let me know if you have any further questions.

Thanks!

[Josh]

Hey Linda,

Thanks for following up with us!

For this particular issue, it may be best to reach out to the developer of the plugin and see if they can provide an update for this issue. They should be able to limit the impact of some of that code so it doesn’t get fired on the calendar pages where it shouldn’t be getting used.

Let me know if this helps.

Thanks!

[Josh]

Hey Christina,

The link above is for unpublished posts. Are the sermons and staff for your site unpublished items? If so, that would be a related issue and be tied to this bug.

Thanks!

[Josh]

Hey Yann,

Thanks for following up!

The issue here is the use of different parts of the Google Maps API. When looking at the map that shows based on the address within your single event view, it is an embedded map using the Google Maps Embed API.

The Longitude and Latitude settings for the venue should get set automatically when you create the venue. This is done using the Geocoding API. However this can sometimes be hindered by the fact that each IP address has a limited number of API calls that can be made within a 24 hour period. If you’re on a shared hosting plan, it is possible that the limits could have been hit when you created the second venue. Try creating the venue again and see if the proper latitude and longitude values get saved this time.

In regards to the limits, you can see (within the links above) that the Google Maps Embed API (used for the maps that are working on your site) don’t have a stated usage limit while the Geocoding API has a limit of 2,500 requests every 24 hours.

Let me know if this helps.

Thanks!

[Josh]

Hey Anna,

Thanks for following up!

Strange, it doesn’t appear to be giving us any additional information here. One thing you may try, since this happened during an update, is to re-download the files from your account here of the latest version of the plugin. You can then delete the existing files off of your computer and replace with the new ones.

It’s possible that there might not have bee a full download (or full migration from staging of changes) with the last round of updates and doing the above would address that issue.

Let me know if this helps.

Thanks!

[Josh]

Hey Brendan,

Unfortunately I don’t believe there is a straightforward way to move this information over.

What you could try doing, take a look at the src > views > filter-bar > filter-view-horizontal.php. You could potentially copy that file’s content into your sidebar.php file and have it only conditionally display on the main calendar pages. This is an untested theory, but would be a step in the right direction for what you’re trying to accomplish.

Let me know if this helps.

Thanks!

[Josh]

Hey Jon,

Thanks for reaching out to us!

I apologize for any inconvenience you’ve experienced with using our plugins. For this one, it sounds you may have some additional code on your site (most likely within your current theme or possibly within another plugin) that is relying on the code from the Community Events plugin. Since the plugin is now deactivated, this code would be using functions that no longer exist and would cause fatal errors in PHP, causing the site to break.

Check your theme’s functions.php file or see if there is a “tribe-events” folder within your theme and try removing anything that could have been added as a customization to the Community Events plugin.

Let me know if this helps.

Thanks!

[Josh]

Hey Brendan,

Thanks for reaching out to us!

I’m assuming you’re wanting to update these fields for the front-end community events submission form?

To do so, you’ll want to follow our Themer’s Guide to copy the “organizer-fields.php” file from the Community Events plugin folder into your theme. From there, you can remove the fields that you don’t want to display and replace them with the ones that you do want to use.

You will need to ensure that you do structure the new inputs though to match up with the custom fields that you would like them to sync up to. If you did use our “Additional Fields” option, you could take a look at the “custom.php” file found in the same folder within the plugin as the “organizer-fields.php” file and copy that code over to your new “organizer-fields.php” file to get your custom fields displaying there.

Let me know if this helps.

Thanks!

[Josh]

Hey Joe,

Thanks for reaching out to us!

Take a look at the following snippet and description and see if this works for you.

https://gist.github.com/BeardedGinger/a0909879cff5a302c4d4

Let me know if this helps.

Thanks!

[Josh]

Hey Brandon,

Thanks for reaching out to us and welcome to WordPress!

This definitely sounds like a strange issue for sure. I took a look at the site and saw that the events weren’t displaying on those views. The strange thing that I did notice was that for the list view it still showed the “Next” & “Previous” events links which means that the query is recognizing that there are events to display. If it were actually returning no events, those links would not display.

As a starting point, have you tried following the Testing for Conflicts procedures fully? This will help us to see if there is a conflict at play here with an existing plugin or theme.

Let me know if this turns anything up.

Thanks!

[Josh]

Hey Michael,

Thanks for reaching out to us!

That would definitely be one way of approaching this one. However, since our tickets aren’t technically a downloadable product we probably will be leaving that portion set to “no” so when you update you’ll lose that customization.

Woo does have another way for automatically setting all orders to “complete” automatically. You can check out this snippet to see how that is done.

Let me know if this helps.

Thanks!

[Josh]

Hey Josh,

Thanks for reaching out to us!

Unfortunately we’re unable to provide support here in our Pre-Sales Forum but I would like to help you get pointed in the right direction.

For this in particular, this tutorial should include everything that you need to accomplish the changing of the titles. Remember, these snippets should be added to your theme’s functions.php file and you don’t need to worry about following the Themer’s Guide or adding a “tribe-events” folder to your theme for this particular change.

I do apologize for any frustration you may have in customizing. However, almost anything you can imagine within the plugin can be customized via the use of hooks and filters rather than just templating options. This is the most common and preferred method for customizations for WordPress plugins.

Let me know if this helps.

Thanks!

[Josh]

Hey Eric,

Thanks for reaching out to us!

Would you mind providing the system information for your site which can be found under the Event Settings > Help tab as a private reply here? This will give us further information to test on this particular issue.

Thanks!

[Josh]

Hey,

Thanks for reaching out to us!

I apologize for the inconvenience of this issue. I’ll reach out to the team for some further testing on this one and will get back to you tomorrow.

Thanks!

 

[Josh]

Hey Anna,

Thanks for reaching out to us!

I apologize for any issues you’ve had in updating the plugins. To help in troubleshooting, would you mind temporarily turning on WP_DEBUG on the live site? This should show us the exact error that is happening and give us an idea of where to look.

Thanks!

[Author]

Posts