[Cliff]

Hi. Thanks for the screenshot and explanation.

Thanks to your help, I have discovered (and hopefully fixed) these 2 bugs. I apologize for the inconvenience.

The “Attendee Information:” translation issue will be fixed in a future update due to this code change. In the meantime, you could hard-code your own language into the file at /wp-content/plugins/event-tickets-plus/src/admin-views/meta.php or follow our Change the wording of any bit of text or string article.

In that same file, the 2nd string you reference doesn’t even have a text domain so it wasn’t even translatable. Same story as the above paragraph except a different code change.

Let us know if you have any other questions or concerns! 🙂

Thank you!

[Cliff]

This reply is private.

[Cliff]

This reply is private.

[Cliff]

Todd, I understand the frustration when a part of your site isn’t working. However, a 403 (Forbidden) error when submitting a Community Events event isn’t a known bug and I cannot replicate the issue.

Therefore, I’d start by investigating your .htaccess file yourself or with your web host or with your developer.

If nothing relevant is found, I’d suggest following our Testing for Conflicts Guide.

I understand this may be inconvenience, but discovering the root cause of the issue is the best way to provide a long-term fix. It might turn out to be one line of your .htaccess file, or it could be a theme or plugin conflict, or it could be something else.

We need to go through the troubleshooting steps to thoroughly assist you. I hope you understand and can provide some actionable information to me as a result of your troubleshooting.

Thank you!

[Cliff]

I don’t have any such information at this time, but please keep an eye on things on your end.

[Cliff]

Hi Boris. Thanks for the 2 links.

I can confirm your site appears in mobile view on a wide desktop browser window.

Did you try the ‘tribe_events_kill_responsive’ code snippet in that KB article?

 

Please follow our Testing for Conflicts Guide and see if that helps narrow down the cause of this (e.g. a theme or plugin conflict)

Let us know what you find out.

Thanks.

[Cliff]

Hi Emily.

While I don’t see you have a current PRO license that includes Support, I believe the file you’re looking to override is this one:

/wp-content/plugins/events-calendar-pro/src/views/pro/widgets/modules/single-event.php

Please let me know if that got you headed in the right direction. If you have any follow-up questions and the site you’re working on is publicly-accessible, please include a link.

Thanks!

[Cliff]

Hi Todd. Sorry you’re experiencing this.

I noticed a console error at your site when I tried to submit the event: http://cl.ly/06293M2F3f03

Your .htaccess file may be causing this. You’d need to request help from your web host or developer to address such an issue.

If you find .htaccess isn’t the cause, please follow our Testing for Conflicts Guide and see if that helps narrow down the cause of this.

Let us know what you find out.

Thanks.

[Cliff]

Hi Tim. Thanks for including the iCal link.

Using the HTTP (instead of WEBCAL) version of that link, I entered it into an iCal Validator and this was the result: http://cl.ly/111Z2K2T2L1y

As long as your iCal feed validates, our iCal Importer should be able to properly import from it.

Please let me know what you find out.

[Cliff]

Susan, I understand the concern about messed up oEmbeds that are still left over.

It’s probable that the stored oEmbeds will eventually refresh/update themselves some time in the future.

However, if you want to force all oEmbeds to refresh themselves, you might try this code snippet:

https://gist.github.com/cliffordp/e331b28d0d4d3b042fc7daf714256796

1. add this code to your theme’s functions.php file
2. load a page on the front-end of your site (e.g. the home page)
3. comment out or delete this code from your theme’s functions.php file
4. check to see if previously incorrect oEmbeds are now fixed (i.e. visit a page that had one and see if the oEmbed is now displaying correctly)

Warning: If you do NOT follow step #3, your site will be significantly less efficient than it should be!

Please let me know how things worked out for you.

Thanks!

[Cliff]

Hi Juan. Thanks for your patience as I researched this with our developers.

The new Google Maps API key setting does NOT currently get used when PRO is geocoding your address to obtain the latitude/longitude coordinates.

Therefore, I am wondering if Google is tracking your IP Address for Geolocation API calls to determine that you’re Over Limit.

Please see if implementing this code snippet helps:

https://gist.github.com/cliffordp/9d6c25feb389f98e8ae09a41273a3488

1. use the code as described (enter your own API key)
2. try to update/add a new Venue (so the Google Maps Geolocation API gets called)
3. see if you get the error message again

Let me know how things go.

[Cliff]

Hi Robert.

I see your Time Format is set to G:i (24 hour without leading zero)

If you set it to H:i (24 hour with leading zero), it should work for you.

With H:i, the AM/PM correctly does not appear, and the 1970-01-01 issue goes away.

Thanks for helping us discover this bug.

I logged this bug with our developers and will 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]

Jonathan, I’m very glad to hear things improved on your site.

However, I checked in with one of our developers because the bug report your thread is attached to doesn’t show “Completed” (in our internal bug tracker). His response was that we took 2 steps forward and 1 back here. Validation errors can still cause various problems for those multiple-post (organizer) fields.

As such, please still be on the lookout for such issues.

I’ll leave this thread as Pending Fix for now.

Thanks!

[Cliff]

Thanks for letting us know, Jonathan.

[Cliff]

You are correct that the built-in Reset Filters button is designed to clear/reset all Filter Bar fields.

Your custom button’s JS/jQuery code would need to target the specific Filter Bar fields you want to target.

You may choose to use the Reset Filters code as a starting point or just write some code from scratch. It’s your choice. If you need some coding help, you may want to ask your developer or reference our list of known customizers.

[Author]

Posts