Venue displaying as "Array" on all events

[Dylan]

Like others, I am having an issue with venues since updating to 4.0.7. The venue is displaying as “Array” on the calendar front-end. Specifically, it appears to be the country field causing the problem (see screenshot). I normally do not use the location fields, but I tried to select my country and it did not save the selection. For now I have hidden the field with CSS.

Screenshot: http://i.imgur.com/S8YB7Zk.png

Thanks for help!

[Geoff B.]

Good evening Heather and welcome back!

Thank you for reaching out to us.

We are sorry to hear about the word Array creeping up where it shouldn’t. It certainly was not our intention.
I would love to help you with this topic.

I went ahead and tried to reproduce the bug described and you are 100% right, whenever there is no venue defined for an event, the word array appears instead.  All our apologies for that.

This is a legitimate bug and I have opened a ticket for it. Unfortunately, I cannot commit to a release date at this point. But stay tuned!

In the meantime, the best workaround would be to either hide the venue field using CSS

.events-list .tribe-events-venue-details {display:none !important;}

Or hide the field on a per event basis (still using CSS)

.events-list #post-663 .tribe-events-venue-details, events-list #post-326 .tribe-events-venue-details {display:none !important;}

I wish I had a better answer for you, but for now it’s the best one I have.

Thank you for your understanding.

Best regards,

Geoff B.

[Leah]

Hello,

Thank you for reporting this issue. We weren’t able to get a fix for it into our upcoming release (4.1). However, please know that the problem is still on our radar and is ticketed within our system to be addressed in a future maintenance release. We’ll do our best to keep you posted when we are able to get a solution in place. Thank you for your patience while we improve and expand our plugins.

Best,
Leah

[Support Droid]

This topic has not been active for quite some time and will now be closed.

If you still need assistance please simply open a new topic (linking to this one if necessary)
and one of the team will be only too happy to help.

[Geoff]

Hey Heather,

Just wanted to follow up and let you know that we released version 4.1.1 last night and it included a fix for this issue. I hope Geoff B’s workaround helped in the meantime, but please go ahead and remove those and update to the latest version if you haven’t already. And, of course, do let us know if you continue to see any issues from there. 🙂

Cheers and thanks for your patience while we worked on this!

Geoff

[Author]

Posts