LCGSCO

I had the same problem, but worked only with Firefox browser previously, but seems to work now with IE browser.

No, I meant the edit button on existing events, (not posts) but for some reason it now works okay with IE browser. Not sure if Dan fixed it, but it was only a problem using IE browser, but worked okay as I later discovered worked with Firefox browser previously.

This is a followup post that the IE compatibility on the main edit function with the Gigs calendar events now works. I’m not sure why it works without any new updates, but it does.

Sean, I’m having exactly the same problem after changing to a new theme. None of the dates are showing in the date column for any event. Did you or anyone else finad a soluiton to this problem?

I finally found the solution on the Gigs edit function problem after reading one of Dan’s developer notes on his last Gigs update. Apparently Dan uses the Firefox browswer for compatibility with his Gigs calendar plug-in and hasn’t updated the Gigs software for IE compatibility. After using Firefox, the edit function worked satisfactory. The edit furnction doesn’t work with IE 8 or 9. Hopefully, Dan will eventually fix the IE compatibility issue.

I found the solution to my WordPress 500 error by deactivating the plugins:

Here’s the details from Troubleshooting FAQs:

How to deactivate all plugins when not able to access the administrative menus?

Sometimes it may be necessary to deactivate all plugins, but you can’t access the administrative menus to do so. One of two methods are available to deactivate all plugins.
■ Use phpMyAdmin■ In the table wp_options, under the option_name column (field) find the active_plugins row
■ Change the option_value field to: a:0:{}

or via FTP
■ Create an empty plugins folder ■ Via FTP or your host’s control panel, navigate to the wp-contents folder (directory)
■ Via FTP or your host’s control panel, rename the folder “plugins” to “plugins.hold”
■ Via FTP or your host’s control panel, create new folder called “plugins”
■ Login to your WordPress administration menus
■ Via FTP or your host’s control panel, delete the empty “plugins” you previous created
■ Via FTP or your host’s control panel, rename “plugins.hold” back to “plugins”

I used the FTP method and was successfully in getting looged back in and activating the right plugins for sp 3.2.1. Website working correctly with the updates.

Thanks WordPress!