Archives: Replies

Unfortunately, autoupdate is still in development and we can’t tell the exact date when it will be available.

We are glad your issue is resolved, if you have any further questions or concerns please create a new ticket.

If you have a moment, we would greatly appreciate if you could kindly leave us a review at codecanyon! from your account > downloads. Cheers!

Please check https://hopelives365.com/events/eating-you-alive-public-screening/

https://tppr.me/nS9NM

Test RSVP https://hopelives365.com/wp-admin/post.php?post=207447&action=edit

Hello,

Please check this link http://languedoc.squareowl.co.uk/evofeed.

Ashan,

The same on dev2: http://dev2.myeventon.com/15000-2/

Go to March https://tppr.me/MrNJp

http://dev2.myeventon.com/wp-admin/post.php?post=14979&action=edit Full

http://dev2.myeventon.com/wp-admin/post.php?post=14980&action=edit

Please send us FTP access to your site as a private message.

Thank you for your messages, I am going to assign this ticket to Ashan and he will be able to take it from here and find you a solution. Please allow some time for him to get back to you, we greatly appreciate your patience and thank you for being a eventon customer! Also please disable any IP blocking on your site if there are any.

kv1.matineegroup.com/events-calendar-tickets/ leads to 404 Not Found. Could you please check?

Hi, I am afraid since we are just a small club I cannot offer more. Hence I will close the ticket and submit a features request. Maybe one day it’ll be developed.

Thank you and best regards,

Konstantin

The one error is gone, but another error at the bottom of the page remains:

 

Warning: count(): Parameter must be an array or an object that implements Countable in /www/htdocs/w009e30a/training.akaishidaiko.de/wp-content/plugins/eventON/includes/class-frontend.php on line 682

did you make any modifications while testing? this is imperative to know since i have to make the same plugin updates to the live site and want to make sure this doesn’t happen on the live site for obvious reasons.

i need to make sure as this wasnt a one off fluke as it was replicated across different browsers and different machines(on site testers) during testing.