Runtime Errors in Simple Edit Interface

[tina_ye]

Hi I created a Simple Edit Layout for our International courses by following the Examples the MySource Matrix Simple Edit Layouts Manual and applied to the Standard Page. Everytime when I went to the Simplet Edit Interface I would get some JS Runtime Errors on different lines. The Errors are: "Object expected" and "'tooltips' is undefined". I am not sure if it's because of those errors that I wasn't be able to do safe edit and commit the changes. Can someone please help me? I have pasted what I put in the Simple Edit Layout - it's identical with the one in the manual:


Editing the asset %globals_asset_name%

To edit a page change the Status to Safe Edit. Once you have finished editing the page select Apply for Approval.



%details-S_status%



You can change the Page Name and Page Short Name here:



%details-S_details%



Edit the contents of the page in the box below.



%__custom-contents%



Fill out the metadata fields below.



%metadata-F_metadata_values%



To save your changes click Commit %commit_button%

[Chris_Horikx]

Hi Tina,


You wouldn't happen to have mootools installed would you? Mootools is known to interfere with the simple edit JS. If you aren't using Mootools, try disabling all of the JS files you have in the design applied to the page you are trying to edit. You can do this conditionally with the use of a Show IF design area.



Chris

[tina_ye]

You wouldn't happen to have mootools installed would you? Mootools is known to interfere with the simple edit JS. If you aren't using Mootools, try disabling all of the JS files you have in the design applied to the page you are trying to edit. You can do this conditionally with the use of a Show IF design area.

Thanks Chris, We didn't have mootools installed but we did have a few crossfade javascripts. I followed your instructions and disabled all of the JS files we have by using conditionally Show IF design area. But I am still unable to change to Commit the changes. I am still getting Runtime Errors on two consistent lines: Line: 122 Error: Object expected and Line: 40 Error: Not implemented. What can I do next?



Thanks a lot!

Tina

[nnhubbard]

[quote]Thanks Chris, We didn't have mootools installed but we did have a few crossfade javascripts. I followed your instructions and disabled all of the JS files we have by using conditionally Show IF design area. But I am still unable to change to Commit the changes. I am still getting Runtime Errors on two consistent lines: Line: 122 Error: Object expected and Line: 40 Error: Not implemented. What can I do next?


Thanks a lot!

Tina[/quote]



What browser is this you are getting errors in? If you are using Firefox with firebug, what js file is the error in, or is it in the main /_edit page?

[tina_ye]

What browser is this you are getting errors in? If you are using Firefox with firebug, what js file is the error in, or is it in the main /_edit page?

Thank Nic. I mainly use IE7. When I use Firefox 3, I didn't get those runtime errors but the Commit button simply didn't work. However, a good news is that after I changed %metadata-F_metadata_values% in the Simple Edit Layout to print a specific metadata schema field %metadata-F_{metadata schema field id}% For example: %metadata-F_1753%, those js runtime errors disappeared and the commit button also worked. We then tried to use multiple Simple Edit Layouts for different screens. What we are getting now on the Contents Edit screen is around 20 FIXME "Unknown toolbar iten: undefined error messages. After that, we get Error: 'this.config.btnList[…]' is null or not an object. Then when we tried to edit the contents, we got Type Mismatch error and weren't be able to edit at all. What we put into the Contents Screen Layout is just %__custom-contents% Any idea?

[nnhubbard]

Thank Nic. I mainly use IE7. When I use Firefox 3, I didn't get those runtime errors but the Commit button simply didn't work. However, a good news is that after I changed %metadata-F_metadata_values% in the Simple Edit Layout to print a specific metadata schema field %metadata-F_{metadata schema field id}% For example: %metadata-F_1753%, those js runtime errors disappeared and the commit button also worked. We then tried to use multiple Simple Edit Layouts for different screens. What we are getting now on the Contents Edit screen is around 20 FIXME "Unknown toolbar iten: undefined error messages. After that, we get Error: 'this.config.btnList[…]' is null or not an object. Then when we tried to edit the contents, we got Type Mismatch error and weren't be able to edit at all. What we put into the Contents Screen Layout is just %__custom-contents% Any idea?

Where are you looking for these errors? Is IE7 showing these?

I think that you should trust Firebug, I have always thought that debugging js in IE is pretty bad. It will throw strange errors when other browsers don't. Just my experience.

Are you still not able to add text to the wysiwyg editor if the only thing you have in the layout is %__custom-contents%?

[tina_ye]

[quote]Where are you looking for these errors? Is IE7 showing these?


I think that you should trust Firebug, I have always thought that debugging js in IE is pretty bad. It will throw strange errors when other browsers don't. Just my experience.



Are you still not able to add text to the wysiwyg editor if the only thing you have in the layout is %__custom-contents%?[/quote]



Thanks agian Nic. Yeah, it's IE7. I just tried it in Firefox 3 I got 2 FIXME errors but still wasn't be able to edit the wysiwyg editor. %__custom-contents% is the only thing I have in the layout. I have never used Firebug before but will give it a go. Cheers

[nnhubbard]

Thanks agian Nic. Yeah, it's IE7. I just tried it in Firefox 3 I got 2 FIXME errors but still wasn't be able to edit the wysiwyg editor. %__custom-contents% is the only thing I have in the layout. I have never used Firebug before but will give it a go. Cheers

Strange that it is not working with only the %__custom-contents% keyword. Do you have any additional .js file or script on your page or in your design that could be interfering with this?