Geolocation not working

[Jörg]

Hello,

I have trouble regarding the geolocation function of Events Calendar PRO. It won’t update the Venue Data, instead I receive the following errors, see attachment.

I set up my Google Maps API, it works just fine.

I also got an error which said set_time_limit isn’t supported. Well, it’s blocked by the hosting company, so I tried a workaround by removing said function call in the source code. I did not change anything else.

When I tried to troubleshoot the problem I moved the project to my PC (because in this stage of the project switching the theme would give me even more sleepless nights) using XAMPP. With all activated (and not modified) Plugins and Themes it works like a charm there.

I guess i need to change my hosting company? What are the PHP requirements?

Thanks in advance and please excuse my bad English.

[Jörg]

Oh I forgot this:

Looks like it displays both an error message and a success message at the same time?

[Brook]

Howdy Jörg ,

I would love to help you with this.

The first error message you show references gzinflate. Specifically it is part of the WP CURL functionality. Basically our plugin will require everything WordPress requires for the WP HTTP API to work. If anything that it needs it missing or misconfigured for WordPress, it will generate errors. I wish I could be more help here. All the error message says is data_error, and I would need to be running a debugger on your server to glean more info than that.

Thanks for letting us know your host does not support set_time_limit(). removing the functions calls, or putting @ immediately before them was a good idea. I’ll note that for our developers to put an @ before each of those in the future to suppress the error your host generated. WordPress itself uses this function a number of times, but it suppresses errors if the host does not support it so we should too. 🙂

Does that info help any? Does that answer your questions?

Cheers!

– Brook

[Jörg]

Hi Brook,

thank you for your help, your lead got me on the right track. I resolved the data_error issue by disabling gzip compression in the geolocation method, thus I’m forcing WordPress to figure out the correct method to handle the data itself, I think.

The venue data still won’t be updated, I tried everything I could. I even set up a clean WordPress installation on the same server, same result. I’d like to accept your offer regarding you running a debugger on the server. How can I securely pass you the server login credentials? Also, do you want me to enable all PHP error messages?

[Brook]

Howdy Jörg,

That’s awesome, we got past the PHP error!

I’d like to accept your offer regarding you running a debugger on the server. How can I securely pass you the server login credentials?

I wish I could do that! The debugger I am referring to though requires a special type of server and configuration, it’s what we use when developing plugins. It’s not really something we can run on others servers.

Also, do you want me to enable all PHP error messages?

Not just yet. I wish to double check on something. It appears we are currently not using the API key for the venue location info, and I want to talk to the developers to find out why.

• Brook

 

[Jörg]

Hi Brook,

thank you for the update. I’ll just await the corresponding update then.

I’m sorry to bug you further, but I noticed another issue: The generated link for a venue location website is not displayed properly, as you can see in the attached screenshot.

Anyway, I wish you a nice weekend.

[Brook]

Oh sorry I missed your response here Jörg.

I’m sorry to bug you further, but I noticed another issue: The generated link for a venue location website is not displayed properly, as you can see in the attached screenshot.

It’s not trouble at all. That is a bit quirky. I would think this would be a result of your theme. Perhaps it is HTML escaping the entire link thinking the link wouldn’t contain an < a > element? Could you try briefly changing themes to see if this problem persists in a default theme like Twenty Sixteen? Feel free to switch back.

If it does not persist in Twenty Sixteen checkout your custom theme’s folder. Does it have a tribe-events folder within it? If so it is probable that there is a file called /modules/meta/organizer.php inside of it. Renaming or deleting this file will likely cause this issue to go away, but might make things look different on your site. The problem is likely somewhere in that file, so if you share it here I might be able to find it and correct it.

Did that help narrow down the cause?

• Brook

[Jörg]

Hi Brook,

thank your very much for your assistance. You guessed right, the theme I’m using indeed has an Events Calendar integration. It hasn’t been updated since late 2015, so some modfications made in that theme became obsolete. I corrected that in the child theme, excluding the geolocation everything works fine now.

Again, thank you very much, I wish you a nice day.

– Jörg

[Brook]

Excellent news! It was truly my pleasure to help. Thank you for getting back and letting me know how it was fixed.

Cheers!

– Brook

[Brook]

Circling back around to our earlier discussion:

The venue data still won’t be updated, I tried everything I could. I even set up a clean WordPress installation on the same server, same result.

What is happening is that the Maps API key is not used for venue data “geocoding”. Because it is not used you share the same limit as everyone else on your server, which is 20k lookups per day. Someone else on your server is likely doing thousands of lookups every day and ruining things for the rest of you.

On our end we would like to adjust our plugin so the API key is used for “geocoding”, then you can avoid this error. But until that new version is released you can keep trying to rebuild the venue data, and eventually you might get your request in before the server goes over the daily limit. Or, you can manually specify the latitude and longitude for each event that has not been geocoded.

– Brook

[Jörg]

Hi Brook,

What is happening is that the Maps API key is not used for venue data “geocoding”. Because it is not used you share the same limit as everyone else on your server, which is 20k lookups per day. Someone else on your server is likely doing thousands of lookups every day and ruining things for the rest of you.

That indeed seems to be the reason. At this stage of the project the website is hosted in a simple hosting package, which means that serveral other dozen or even hundreds of websites are hosted on the same server. It will be moved to a dedicated server soon, the issue should be resolved then.

Thank you very much for the heads-up, have a nice day.

– Jörg

[Brook]

That is good to hear! Thank you for getting back Jörg.

Cheers!

– Brook

[Courtney]

Hey there Jorg

We’ve just released an update that should fix this bug. You can read more about it at http://m.tri.be/19tp. Please update your plugins and let us know if you are still experiencing this or if we can close out this ticket.

Note: We suggest testing updates on a staging server (https://theeventscalendar.com/knowledgebase/creating-using-wordpress-staging-site/).

Thanks
Courtney 🙂

[Support Droid]

Hey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.

Thanks so much!
The Events Calendar Support Team

[Author]

Posts