Thread

After updating to 2.2 from the last stable build release, my Control Panel is inaccessible.

WHAT I DID:
Accessed http://www.sitename.com/admin.php

WHAT HAPPENED:
The Control Panel home page appears as expected, with the following error:

A PHP Error was encountered
Severity: Notice
Message: Undefined index: zero_tolerance
Filename: low_nospam/ext.low_nospam.php
Line Number: 244

None of the AJAX top menu controls (Content, Design, Add-Ons, Members, Admin, Tools) work. The code appears to be there when I view source, but it’s not executing.

WHAT I EXPECTED:
Not to have a problem with low_nospam.
My Control Panel to work properly.

mfraase,

Can you temporarily disable extensions and make sure the control panel works normally in that case?

Disabling extensions in the config.php file is the first thing I tried. No change.

I did some dinking around and ended up re-downloading and re-installing 2.2. The AJAX bits in the Control Panel now appear to work (in non-AJAX form) in Firefox 5 and Chrome 13.0.782.32 but *not* Safari 5.0.5.

Please fix this.

Hi Michael,

By AJAX bits, what in particular are you referring to? The dropdown menus? Have you completely cleared Safari’s cache? Glad you’re making progress, just want to try to pinpoint this further.

Yes, by AJAX bits, I mean the drop-down menus and the pop-up accessories.

Yes, I’ve cleared all the caches, everywhere.

Here’s another interesting data point: In Safari, when I go in via the old administration URL <http://www.sitename.com/<system_folder>> the AJAX bits work. When I go in via the new admin.php <http://www.sitename.com/admin.php> the AJAX bits don’t work (in Safari).

Man, I really cannot replicate this with Safari. Have you renamed your system folder, and if so, have you made the appropriate changes to admin.php?

See this documentation page:
http://ellislab.com/expressionengine/user-guide/installation/best_practices.html

Yes, my system folder name has been changed and yes, I’ve made the appropriate changes to admin.php.

Well, this is weird. After updating to Mac OS X 10.6.8 and a restart, the AJAX problem in Safari is resolved and the Control Panel is working as expected.

Hi, mfraase -

This very much sounds like an issue with some caching somewhere along the pipe.  I am sorry you ran into this, but I"m glad that it has cleared up.  Before I close this, I just want to ensure that it has remained in working order?

Thank you.

Yes, this can be closed.

Thanks Michael.  If anything else comes up, please start a new thread, and have an awesome weekend.