Archives: Replies

You can find our Refund Policy here:

https://docs.myeventon.com/documentations/terms-and-conditions-and-refund-policy/

Please add this CSS code to EventON > Styles (If you don’t see any change, EventON > Scripts & Styling > turn off Write dynamic styles to header > save settings > turn on Write dynamic styles to header). You can also add this code to wp-admin > Appearance > Customize > Additional CSS.

.ajde_evcal_calendar.boxy .evoShow_more_events { min-height: 150px; }

Please send us wp-admin access to your site from “Access Info” box on right side menu, to further assist your situation.

Also try EventON > Scripts & Styling > turn off Write dynamic styles to header > save settings > turn on Write dynamic styles to header.

What’s the temporary fix? Could you elaborate?

Hello,

Please add this CSS code to EventON > Styles (If you don’t see any change, EventON > Scripts & Styling > turn off Write dynamic styles to header > save settings > turn on Write dynamic styles to header). You can also add this code to wp-admin > Appearance > Customize > Additional CSS.

.ajde_evcal_calendar.color #evcal_list .eventon_list_event p a.desc_trig:focus { box-shadow: none !important; }

The code will remove it.

Perfect! Please keep us updated.

Usually any cache plugin allow you to remove URLs from cache.

Try removing /?evo-ajax=eventon_get_events

Hello,

Can we somehow help you with any issues before refunding it?

While we are working on this, please make sure to cancel your subscription:

https://docs.myeventon.com/documentations/how-to-cancel-addon-subscription-before-auto-renew/

Hello,

Please send us wp-admin access to your site from “Access Info” box on right side menu, to further assist your situation.

Try placing it into Text Element, but make sure to switch it to Text Mode.

Kindly update to the latest version of fullcal 2.2.3 — https://docs.myeventon.com/documentations/changelog-fullcal/

this will resolve the issue of not all the evnets showing on first calendar load. 

Just wanted to update you we have addressed this issue in version 4.9.11 — let me know if the issue still happen with new version .