Reply to: tickets(262713)

Yes, it seems that the map is not loading fully at first. Please send in the wp-admin access so that we can be able to troubleshoot the issue fully.

Reply to: tickets(262900)

Hi Joe,

I think that would be the best option for now.

You can also create a new ticket with your initial feature suggestion and select Feature Request as category so others can vote on your idea and get it moved into development faster.

Reply to: tickets(262958)

Hi Evan,

Please use the CSS code below instead

.ajde_evcal_calendar.boxy.boxstyle1 .evo_boxtop, .ajde_evcal_calendar.boxy.boxstyle2 .evo_boxtop{border-radius: 0px;}

Reply to: tickets(260574)

Hi Ashan,

Thank you for taking a look at this. I appreciate you are very busy.

This is becoming a major issue for us, refunding one of four tickets on an order causes it to mark all four tickets as refunded. (separate issue, but seems linked to this..). Whilst identifying which ticket belongs to what order is possible with it’s ID, it does not help identify which line item on that order it corresponds to.

URL: https://www.elgintownhall.co.uk/wp-login.php (wp-login.php is required rather than wp-admin to avoid our MS 365 Single sign on system)

Username: eventOnSupport

Password: 7VVHFvtvLW!goPbrgh@nBx(l

This is our live site details for you. Please let me know if you’d prefer a staging site to do some testing with.

Thanks again,

Angus.

Reply to: tickets(259391)

Andreas, dynamic tags for RSVP subject line was never supported. As you can see it is not mention anywhere in the settings. However you do bring a great feature and we will add support for these in the future updates and will make a note in the settings as to which tags are supported. 

Reply to: tickets(262611)

Ok found add to calendar twice in the event card designer, removing one of them. have done the trick 🙂

Reply to: tickets(258758)

So you can use a query like SELECT * WHERE meta_kay LIKE ‘%checked’ I am not sure exactly what you are trying to do?

Reply to: tickets(258758)

Ok here you go.

So the “status” value was legacy method. My sincere apologies. We are storing the status as an array with corresponding ID and status in meta key “ticket_ids”

Reply to: tickets(258758)

My apologies mate, we’ve been running heavy past few weeks with cyber week stuff. Ok let me get you straightened out here. 🙂 Doing some debugging now.