|
bigtomato
|
April 13, 2020 at 5:52 pm
Hello, I am trying to get a better look for the espresso calendar by switching to the basicDay mode when in mobile. But I cannot get the switch to work.
Here is the code on the page:
<div id=”content-desktop”>[ESPRESSO_CALENDAR]</div>
<hr />
<div id=”content-mobile” style=”height: 800px;”>[ESPRESSO_CALENDAR cal_view=”basicDay”]</div>
and here is the CSS:
@media only screen and (max-width: 480px) {
#content-desktop {display: block!important;}
#content-mobile {display: none!important;}
@media only screen and (max-width: 385px)
{
#content-desktop {display: none!important;}
#content-mobile {display: block!important;}
}
}
I have tried many different screen sizes but the view only shows the basicDay view no matter what the CSS max-width is. The problem is that my client wants to see the whole text descriptions in mobile, but they are too long to show in each day’s box.
I’m beginning to think EE3 cannot do this for some reason? I also tried the WonderPlugin Conditional Display mentioned in a ticket about this for EE4 but that didn’t work either. We cannot move to EE4 because we need recurring events.
Is there anyway around this?
Thank you.
|
|
bigtomato
|
April 13, 2020 at 5:53 pm
This reply has been marked as private.
|
|
Tony
|
April 14, 2020 at 6:57 am
Hi there,
Currently, you can’t render 2 instances of the calendar on a single page which is why this isn’t working (although your only displaying one, both are in the page and one is simply hidden).
A better alternative to the above is using the method here:
https://eventespresso.com/wiki/events-calendar-add-on/#how_to_calendar_list_on_small_screens
|
|
bigtomato
|
April 14, 2020 at 5:20 pm
Hi Tony, thanks. I’ve tried this, and get this error:
Uncaught TypeError: ye[e] is not a constructor
at y (fullcalendar.min.js?ver=1.6.2:6)
at f (fullcalendar.min.js?ver=1.6.2:6)
at r.u [as render] (fullcalendar.min.js?ver=1.6.2:6)
at HTMLDivElement.<anonymous> (fullcalendar.min.js?ver=1.6.2:7)
at Function.each (jquery.min.js?ver=5.3.2:2)
at m.fn.init.each (jquery.min.js?ver=5.3.2:2)
at m.fn.init.t.fn.fullCalendar (fullcalendar.min.js?ver=1.6.2:7)
at HTMLDocument.<anonymous> (espresso_calendar.js?ver=2.2.8.p:24)
at j (jquery.min.js?ver=5.3.2:2)
at Object.fireWith [as resolveWith] (jquery.min.js?ver=5.3.2:2)
Which is weird, because the [ESPRESSO_EVENTS] shortcode works fine elsewhere. So maybe there is a conflict with the wondercond plugin?
Are you all still working on adding recurring events to EE4 or has that gone by the wayside?
thank you.
|
|
Tony
|
April 15, 2020 at 4:03 am
Your site is loading a different version of jQuery than the version included within WordPress which causes issues like the above. I tested the above plugin on a test site using the latest version of EE3 (and calendar) before posting to confirm it worked so that’s likely the problem.
For details as to why, see here: https://pippinsplugins.com/why-loading-your-own-jquery-is-irresponsible/
Are you all still working on adding recurring events to EE4 or has that gone by the wayside?
Yes, we are still working on recurring events for EE4.
Although to put it correctly, we are working on changing the event editor which will then allow us to work on recurring events. Without going into great detail there are a lot of backend changes required for managing recurring events within EE4 and we’ve learnt from the current setup that the editor needed to change to allow for them. For example, a recurring issue with people creating multiple datetimes/tickets within a single event is hitting the servers max_input_vars setting and then even if you upped the limit to use the current editor once you had more than a few events in the series it’s not easily managed, the new editor solves this.
We can’t just skip that and release a recurring events manage that ‘will do for now’ as the issues we are working on simply become compounded the more events/datetimes/tickets you add.
The developers are working solely on the changes mentioned above so it is our top priority but there’s a lot of moving parts, new models that needed to be created, essentially a new framework for the editor so it’s no simple task. The way it’s being done should hopefully make it much quicker to develop new features in the editor like recurring events that it would have done previously, that extra time now should help in the future.
So recurring events are most definitely on our roadmap and will be included with EE4, however, when people ask the above the next question is usually around when it will be released and that I can’t answer currently, at least not with any certainty.
|
