Thread

Hi, Stephen. Are you still using the Corporate theme when testing in Safari? Does the same thing happen with the Default theme?

Hi Sue,

This is using the default theme.

Cheers,
Stephen

I’ve just installed the beta version 2.1.4 locally, with no additional add-ons, and no .htaccess. I’ll probably be nuking test-ee.com on MT today to test again. Are you game to try with the beta locally?

Hi Sue,

Are you game to try with the beta locally?

Downloading as I type…

Cheers,
Stephen

Hi Sue,

I started with a fresh install of the beta, and at first things appeared to be working.

However, as soon as I updated (a copy of) a site containing a reasonable amount of data, everything started to go pear-shaped. Here’s what happened, using Safari 5.0.3 running on Mac OS 10.6.6:

1. I opened the Publish Entries page, and created a new channel entry. As an aside, there was a PHP error on the Publish Entries page, which caused problems with the layout; that’s another issue entirely though.
2. After successfully saving the new channel entry, I navigated to “Edit Entries”, and attempted to filter by Channel. Nothing happened. I went to Content → Edit, and tried again. Still nothing. Opening Safari’s Web Inspector displayed a JavaScript error.
3. Thinking that maybe it was a caching issue, I decided to refresh the page using CMD-R, rather than navigating to it via the menu. White screen of death. Repeated refreshes made no difference.
4. Next, I tried removing the class and method parameters from the query string, in an attempt to get back to the home page. Still nothing.
5. Finally, I removed the session ID, in an attempt to at least get back to the CP login screen. This time a page was displayed; unfortunately (and bizarrely) it was the “ExpressionEngine Installation and Update Wizard” screen.
6. Hitting CMD-R on this screen finally brought me back to the CP home page (still logged in).

As that was such a roaring success, I figured I’d try it again. I skipped the “Publish Entry” bit this time.

1. First, I navigated to “Edit Entries”, and attempted to filter by Channel. Again, nothing happened.
2. Learning from my previous experience, I decided to filter by Channel without the aid of JavaScript, and hit the “Search” button.
3. White screen of death.
4. CMD-R. White screen of death.
5. CMD-R. White screen of death.
6. CMD-R. White screen of death.
7. Swear. White screen of death.
8. Go to browser location bar, and press ENTER (without changing the URL). Success!

Despite that glimmer of hope, from that point on most page load attempts resulted in a WSOD. That included all the pages in the “Add-ons” section (where I was heading to disable add-ons).

I then tried using the CP in Firefox 3.6.13. It all worked perfectly (aside from the aforementioned PHP error on the Publish page of course).

Finally, I gave it whirl in Chrome, just in case it was a Webkit issue. Again, no problems.

In summary then, the CP still doesn’t work in Safari on a Mac.

Cheers,
Stephen

Thank your for the detailed feedback.

Has there been any progress on determining what may be causing this?

I have been experiencing this problem off and on for over a year now.

For me, when Safari starts screwing up, it seems everything goes back to normal as soon as I open Chrome. Open Chrome, and Safari magically starts loading pages again.

I’ve used both Safari and WebKit nightly, this issue exists in both. It’s strange that it doesn’t exist in Chrome.

Brian

Hello brianearwood,

I am sorry to hear you are running into this problem.

What version of ExpressionEngine are you using?

What version of each browser are you on?

Looking forward to your response.

Cheers,

Shane,

I’m using EE v2.3.1
Safari 5.1.2
Google Chrome 16
Webkit nightly

Thanks,
Brian

Hello Brian,

Browser issues are very difficult to solve, as I am sure you know.

What kind of plugins do you have installed in your browsers?

Have you been running version 2.3.1 the entire time you have had this issue popping up?

Are you open to updating? The current version is 2.4.

I am looking forward to your response.

Cheers,