Missing/incorrect Venue data from Google Calendar
I have a recurring import from Google calendar that is having issues getting the correct data from Google.
The full correct address is imported into the title field of the venue, but the street number is always incorrect and the postal code is always blank. The street name is usually fine but sometimes blank as well.
I have replicated this issue on a test site. Attached is an example of a venue.
Thanks for reaching out to us!
I’m really sorry about this issue.
We are aware of this bug, it is already ticketed and hopefully we will be able to provide a fix for this very soon. I added your voice to the ticket as well.
I am going to set the status of this ticket to “pending fix” and we will update it once the fix is released.
If you have any new questions or issues please create a new ticket and we’ll help you out.
Thanks for your patience!
At the moment we don’t have a public facing status page for bugreports, so the best place is here in the Help Desk. You can ping us any time in the thread here and we’ll be happy to give you an update.
We have identified different paths we can take with this and currently it’s waiting for the manager to make a decision and choose one.
I know this has been sitting there for a while now and understand that the issue is frustrating. The options need to be carefully weighed, so that we can provide a 1) long-term solution that 2) works well for our users.
I believe the most time consuming part (info collection) of this is done, but I still need to ask you to hang in there a little longer. Rest assured, the bugticket is on highest priority and we are working on a solution.
Thanks for your kind understanding.
I wish that the disappearance of Facebook imports would mean that all other import bugs are automagically fixed, but unfortunately we are not in Wonderland where this could happen.
Nonetheless our development team is continuously working on fixing bugs and bringing improvements to our plugins. Some take less time, and some take more.
The bug you are affected by is partially out of our reach and we cannot do much about that part. We have made some progress on this, but the issue is more complex. At the moment it looks like we might need to switch to a different map provider, which means more work.
Rest assured, the issue is not swept under the carpet waiting for it to expire.
Thanks for your patience so far!