|
Ashleigh James
|
October 21, 2012 at 9:59 pm
Hi there,
It would seem that I’m having some technical difficulties with the calendar add-on. The controls at the top (left, right, today, month, week, day) are displaying but the calendar itself (essentially, the espresso_calendar div) isn’t.
The site in question:
http://110.232.141.190/~fantasea/palmbeachferries.com.au/events-calendar/
WordPress Theme: Roots
Things I’ve tried:-
- View source to determine if multiple jQuery files are being referenced – they’re not.
- Disabled/enabled numerous plugins in different combinations to check conflict – no change.
- Switched to Themeroller from legacy styling – only differences being cosmetic.
- Created a custom page template with PHP to run the shortcode – no change.
Any ideas?
|
|
Dean
|
October 22, 2012 at 1:43 am
Hello Ashleigh,
Unfortunately your site is behind an under construction page.
Can you provide login details?
If so, please send them via https://eventespresso.com/contact/
Choose the “I am sending login info as requested” option and fill out the form
|
|
Ashleigh James
|
October 22, 2012 at 1:54 am
Hi Dean,
It might’ve helped if I had’ve disabled that!
In any case, I’ve sent through the login details as requested.
Hopefully it’s simply something I’ve missed.
|
|
Dean
|
October 22, 2012 at 2:29 am
Hello Ashleigh,
Yes this is odd, I deleted and reinstalled the add on but no joy.
There are 2 Javascript errors coming up. One for something called bootstrap-dropdown.js in your assets folder and another for the calendar itself.
Its hard to say whether the bootstrap issue is causing the calendar issue but I think if the bootstrap is sorted first then we will have a clearer picture.
I would also recommend using WordPress’ built in javascript rather than pulling Googles as that often can resolve many JS errors.
|
|
Ashleigh James
|
October 22, 2012 at 6:21 pm
Hi Dean,
Alrighty – the reference to bootstrap-dropdown.js has been removed – no change. The dropdown menu is still functioning so I’m not even sure why I included that javascript file in the header to begin with.
I’ve also switched out Googles jQuery for one within my WordPress theme. Is that what you meant? I wasn’t 100% sure about your mention of WordPress’ ‘built in javascript’ so I downloaded a clean copy of jQuery 1.8.2.
Any further suggestions?
|
|
Kevin Ackert
|
October 22, 2012 at 7:31 pm
Same problem here…
|
|
Dean
|
October 23, 2012 at 12:42 am
Hi guys,
OK, so the calendar script we use for the calendar does not work past jquery 1.8.1
I will request the devs to look into this.
In the mean time a workaround can be done by downloading fullcalendar 1.5.4 from here http://arshaw.com/fullcalendar/download/ and replacing the fullcalendar.min file in the add on scripts folder.
Of course back up the one you already have.
OR you can revert back to the WordPress supplied Jquery which is ver 1.7.2
|
|
Ashleigh James
|
October 23, 2012 at 1:08 am
Okie dokie..
I downloaded the older release of jQuery (1.7.2) and replaced the one I was using (1.8.2) and..
SUCCESS! =D
One further issue however..
After navigating the calendar and finding an event, clicking on the event takes me to a file not found page. It would seem that it’s taking out the parent category section of the link so it’s domain.com/?page_id=000 etc. instead of domain.com/EVENTS/?page_id=000 and so on.
I can probably figure this one out on my own given a few hours but if you could point me in the right direction – specifically the file I should be looking at – that’d be awesome.
|
|
Dean
|
October 23, 2012 at 1:32 am
Hi,
Glad its back to functionality.
Re the new question – you had the Event Espresso > General Settings > Page Settings set to Main Page for the main registration page. It didnt exist. I changed it to the page called Events and it kicked in.
Double check it’s what you want, but it looks right to me.
|
|
Ashleigh James
|
October 23, 2012 at 3:14 am
Oops – cheers for that! Works great.
Thanks so much for your prompt assistance.
=D
|
|
Dean
|
October 23, 2012 at 3:28 am
No problem, glad its sorted.
@Kevin. If this doesn’t resolve your issue as well, please open a fresh ticket, I am marking this as resolved.
|
|
Kevin Ackert
|
October 23, 2012 at 11:32 am
Looks like your workaround (replacing the fullcalendar.min file) solved the issue as well. Thanks!
|
