Reply to: tickets(381688)

Dave,

No need to be sorry mate, I appreciate everything you are doing.

FTP: 43.250.142.152

Username: eventon@bluediamondtransfers.com.au
Password: OclOYoGJfR*m

Thats direct access to the wordpress directory with everything you should need.

I’m taking a backup as I type this just in case!

Reply to: tickets(382253)

this is set in your time settings- if you provide wp-admin access we can do it for you

your going to want to add the letter

l


to your settings>>>>general from the wordpress dashboard (that letter adds the week to the event card)

if thats confusing – give us admin access and we can do it in a few seconds

Reply to: tickets(381688)

update:

I am sorry for the delay- I am contacting Ashan the creator of eventon about this issue to see if there is a better fix for your site, so you don’t run into this issue in the future after any updates

it is possible he will need ftp details to go in and edit code in eventon that isn’t available from the wordpress dashboard

sorry about this I have been diagnosing with the help of your theme creator we have pin pointed where the issue is coming from and I believe ashan will be able to fix with FTP access

Reply to: tickets(382044)

After updating EventON to version 4.9, I started experiencing issues with the Quform plugin on the same website. Specifically, Quform’s conditional logic stopped working — form fields no longer responded dynamically when changing selections.

After lots of testing, I tracked the problem down to the eventon_event_details.php file.

In version 4.9, the file uses html_entity_decode() combined with a check for unclosed HTML tags (hasUnclosedTags()). If the function finds something unusual, it outputs a warning message or alters the HTML output.

By removing that check and simplifying it to:

$_full_event_details = stripslashes($object->fulltext);
echo apply_filters('evo_eventcard_details', EVO()->frontend->filter_evo_content($_full_event_details));

everything started working perfectly again with Quform.

I completely understand the intention behind validating the HTML, but it seems to interfere with other plugins that rely on stable DOM structures and frontend JS conditions.

Is there already an option in the EventON settings to disable this validation or alter that behavior?
Or should I wait for a future update where this might be handled differently?

Right now I’m running a modified version of this file, but I’m worried that a future update will overwrite it and break the integration again.

If needed, I can share the modified file that works for me.

Thanks for all your work — and I hope this feedback helps!

Reply to: tickets(374195)

Hello,

This is because WPML isn’t enabled in shortcodes according to this guide:

https://docs.myeventon.com/documentations/wpml-eventon-front-end/

Please add the compatibility and then check events from the compatible shortcode to see the correct translation.