Something on your site is applying a z-index to every single element – probably a plugin. The problem is that it’s assigning a -157 value to the calendar events, which pushes them behind the calendar grid, and is the reason you can’t click on them.
That said, follow the FAQ troubleshooting guide to narrow down the cause of the problem and remove the conflicting code.
I can not edit the details on my calendar either. The details modal window does not display.
http://www.lancasterfreethought.org/calendar/
@s_rhoades: I just tried your site and everything appears to be working fine on the front-end. There’s no way for me to test the back-end of your site without access. That said – I recommend following the troubleshooting process outlined in the FAQ and see if you can isolate the cause.
We are having the same issue. When we click on an event to edit it, it gets stuck on “Loading Event Form…” However, if we click on a date that does not already have an event on it, then the event details modal window displays fine. We have not added any new plugins (the calendar was working perfectly fine before the upgrade) or extra scripts for other features, and we have already tried deactivating, removing, and installing a new version of the Ajax Calendar plugin. The calendar also works fine on the front-end – it’s just the back-end that we’re having issues with. Any info on how to fix the issue would be appreciated!
Please follow the instructions described in the FAQ for submitting issues.
Also, details are critical, without them I can’t begin to replicate the problem.
Was a solution to this found? If so, please post it, as I am having the same problem!
Follow the troubleshooting tips in the FAQ and try to narrow down the cause of the issue – it’s most likely a javascript conflict. If you are successful in identifying the cause, please post your findings here for everyone’s benefit. Thanks!
In my case, it has turned out to be a plugin conflict with Hiroaki Miyashita’s very useful plugin, Custom Field Template. I’m not expert enough to find a solution, so that may mean I simply can’t use your plugin. Too bad…
UPDATE: I just found out that is a documented conflict (see this thread). Removing date.js did not work for me so I just switched to the Advanced Custom Fields plugin.
