Reply to: tickets(256868)

Yes, this works perfectly. Thanks!

BTW I add the Eventon shortcode using the divi module “Code” not Text. is this correct?

Reply to: tickets(256864)

Hi,

thanks for helping me.

I changed the part to ux_val=”3″ but unfortunately it does not work.

Reply to: tickets(255107)

Sorry pasted wrong!

If i only want 1 week seen at same time in frontpage, how do i do then?

lasse

Reply to: tickets(255107)

Hi!

Finally I got the event on list to work again, but after the update it is green and with white text and 2 weeks of activities show at once how I change this.

 

Best regards

Lasse

Reply to: tickets(255904)

Hi,
but the new design of the canceled events on my site is very ugly, it’s all gray. Can’t keep the previous setting?
Thank you

Reply to: tickets(256707)

I don’t think you’re understanding me properly – I have added a recurring event starting on the 25th October (yesterday) and set it to recur twice a week for 5 weeks. The new event is showing in the calendar, but is still showing the date as October 25th – I want the date to show whenever the it next recurs.

I have also ticked the option which allows me to see the future dates in the card, but I want these dates to show on the main calendar.

 

See:

https://www.themonastery.co.uk/events/
https://www.themonastery.co.uk/events/test/

Reply to: tickets(256900)

Hello,

Thank you for your great suggestion, at the moment it is not supported. However please create a new ticket and select Feature Request as category so others can vote on your idea and get it moved into development faster.

Reply to: tickets(256707)

event_past_future=”future” makes sure that only Future Events are visible. You can make sure by adding a new test Oct 25 repeat and see if it hidden.

Reply to: tickets(256704)

[25-Oct-2021 16:58:15 UTC] PHP Fatal error:  Out of memory (allocated 606076928) (tried to allocate 48250880 bytes) in /home/domovina/dev1.domovina.je/wp-content/plugins/query-monitor/output/html/hooks.php on line 106

The line says that the issue is with Query Monitor. Could you try disabling it but leave Litespeed.