Can't aquire lock on some assets using IE

Squiz Matrix Support
1

We've just upgraded to v3.12.3 and when using IE 6.0.2800 I'm getting an IE error when I try to aquire a lock on some page content assets when trying to edit content (I've copied it twice so you can see all the content in the scroll area of the error):


[attachment=187:attachment]



[attachment=188:attachment]



Anyone else experiencing this?



cheers

Matt
error1.gif (8.25 KB)
error2.gif (9.21 KB)

2

We haven't had any reports of problems acquiring locks. Try clearing your browser cache to make sure you have the latest JS files.

3

[quote]We haven't had any reports of problems acquiring locks. Try clearing your browser cache to make sure you have the latest JS files.
[right][post=“15732”]<{POST_SNAPBACK}>[/post][/right][/quote]



I've cleared the cache locally and under system management in matrix and am still getting the same error. Sys Admin guys have assured me there is no proxy server and these are the only 2 locations cached files could reside.



Here's a screendump of what I get when I go to debug:



[attachment=190:attachment]



It happens when I press the aquire lock button. I've also tried appending _nocache to no avail.



Any ideas?



cheers
debug_screendump.gif (31.8 KB)

4

I tried creating and new page and pasting the content into it but still got the same error. So I'm thinking there might be something content that matrix or IE doesn't like? Its weird that its only happening to 2 pages, and it's accuring with all users using IE6. Anything in here that could be throwing it out?:

The Kiosk starts with a Welcome screen as shown below;

Screen capture of Welcome screen
Kiosk Welcome Screen

If the kiosk has been unused for a few minutes the automatic demo will start. Just touch the screen anywhere to clear this. The demo will stop and the Welcome screen will appear.

Screen capture of Demo
Kiosk Automatic Demo

If the kiosk has been left at a different screen by the previous user – just press the Start again button in the top left corner of the screen. The Kiosk will return to the Welcome screen.

Start again button

Help is available on the following subjects:
  
5

Actually I've answered my own question here…looks like it was the div id "buttons" in the content that was conflicting with buttons = array() in the js file. It makes sense as these are the only content pages where I've used this id, although I've used it in the parse files with no problem.


So the lesson is don't use a div id or class called "buttons" in content…its probably bad coding practice anyway as its a bit too generic.



cheers

Matt