Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

General Questions /

General questions about getting started with SilverStripe that don't fit in any of the categories above.

Moderators: martimiz, Sean, biapar, Willr, Ingo, swaiba, simon_w

Admin interface not working in Chrome?


Go to End
Reply


21 Posts   5110 Views

Avatar
Max Bradbury

Community Member, 7 Posts

20 July 2011 at 11:46pm

Hi, I'm also having this problem (Chrome 12.0.742.122). The funny thing is, it was working fine until yesterday. I even removed all my modules and the problem was still there. Here's the JS error log, seems like the same problem someone above was having.

Uncaught TypeError: Cannot read property 'height' of undefined (LeftAndMain.js:186)
Uncaught TypeError: Cannot call method 'match' of undefined (prototype.js:1100)
Uncaught TypeError: Cannot set property 'display' of undefined (LeftAndMain.js:769)
Uncaught TypeError: Cannot call method 'match' of undefined (prototype.js:1100)
Refused to set unsafe header "Connection"

Avatar
CoolEP

Community Member, 5 Posts

21 July 2011 at 5:24am

did you try the layout_helpers.js-modification?

for me it seems like a bug in chrome...

Avatar
Max Bradbury

Community Member, 7 Posts

29 July 2011 at 12:34am

It started working again without even having to change anything. Maybe there was a bug and the Chrome devs fixed it.

Avatar
moloko_man

Community Member, 72 Posts

29 July 2011 at 8:56am

I have been able to use chrome to edit the CMS, but the only issue I have is that the Image pane and link pane opens behind the Page Tree pane. Every other browser I try it works fine. Its annoying because chrome is my preferred browser, but I have to use FF if I want to place any images or links into the editor.

Mostly annoying, but would be really sweet if I could find an fix for it.

Avatar
StoneMan

Community Member, 1 Post

1 August 2011 at 4:59am

hmm,
have the same problems with Chrome, but the errors differ a little bit.
Started to use it in IE8 - everything is fine...

Go to Top