MOSS specific buttons aren't working

[Tom.S]

Hi again,
 I've recently upgraded a server from WSS v3 to MOSS and installed the full featured trial version of the RAD editor. When clicking on the MOSSLinkManager or the MOSSTemplateManager im getting a javascript error and no window is loading.

It seems that the code isn't able to get a hold of the MOSS asset picker as far as i can tell. I know that this is expected if you just have WSSv3, but MOSS has been installed over the top and it's still not working.

I don't have a server where i can install MOSS cleanly and retry this, so i was hoping if you could help.
Thanks
Tom.

[Georgi Tunev]

Hi Tom.S,

From what you've posted as information, it seems that something went wrong during the update process. What I can suggest at this point is to try the following:

1. Open your MOSS website and go to a page with a RadEditor in it.
2. Once the RadEditor is loaded, right-click somewhere on the page and select View Source
3. In the Html dump, search for AssetPickers.js (the file holding the asset picker's javascript). The string should look something like this: <script type='text/javascript' src='/_layouts/1033/AssetPickers.js' ....
4. Check if the file exist in the corresponding folder (in the example above: Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\1033). If the file is not there, this is the reason for the buttons not working.
5. In this case, open your Program Files\Common Files\Microsoft Shared\web server extensions folder. Search in the subfolders for the AssetPickers.js file and then copy that file in the corresponding folder (in this example Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\1033)

I hope this helps.


Sincerely yours,
Georgi Tunev
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

[Tom.S]

Hi,
 Thanks for the information.

Within the HTML markup of a page containing a rad editor there is a reference to AssetPickers.js and the actual file exists in the correct location.

Furthermore the OOB Content Editor Web Part works correctly, and is able to load the AssetPickers.js file. To test this i removed the file, restarted IIS and recieved and error when trying to open the rich text editor stating that the JS file couldn't be found.

So its definetly there. Could the installation of the rad editor mucked up some how?

Tom.

[Lini]

Hello Tom,

Please give us the details from the javascript error. If it is something like "Object Expected" on line 215, then this is a known problem with the current build of the editor. We had a dependency on the form.js (the RTE_GetNearestContainingParentElementOfTypes function). This file is usually loaded when you have RadEditor open, but there were a few cases where it did not load and the MOSS asset picker dialogs failed. We have already fixed this problem and the fix will be in the next RadEditor for MOSS release. I apologize for the inconvenience this caused you.

All the best,
Lini
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

[Tom.S]

Hi,
 The details of the Javascript error are:

Line: 116
Char: 2
Error: Object Expected
Code: 0

Within my copy of MOSSEditorTools.js is:
115: var elemLink=RTE_GetNearestContainingParentElementOfTypes(editor.ContentWindow.frameElement.id, RadE_GetCurrentElement(docEditor), new Array("A")); 
116: if( !elemLink )

So it looks like i'm experiencing what you have described.

Do you have a list of known bugs for the currently released RadControls for SharePoint somewhere, would be handy.

Thanks,
Tom.

[Lini]

Hello Tom,

The current list of bugs, which will be fixed in the next release:

- the editor is no longer dependant on the MOSS form scripts (fixes Object Expected JS error).
- CssEditor.css file now loaded properly (if it exists) in presentation mode as well as authoring mode.
- ImagesPaths,DocumentsPaths, etc. path properties now read from the ConfigFile as well.
- removed title attributes from ToolsFile. Tool titles should only be set from the Main.xml localization file.
- fixed a problem with the AssetPickers.js file registration (sometimes it was registered more than once).
- disabled the editor viewstate. The editor is created on each page load so it should not need ViewState.
- Upgrading from SPS 2003 no longer needs an additional assembly (added the old webpart type name to the MOSS editor assembly).

Greetings,
Lini
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

[Maria]

Hi,

We are experiencing the same problem. We tried to add the button MOSSTemplateManager, but get the javascript error "Object expected" when clicking on it. We don't have a problem with MOSSLinkManager, that dialog works fine. We are currently using the 4.3.1 version of Full featured rad editor (trial version at the moment). Was this problem fixed in this version or do we need to update it to the next? Or is it something else since the link dialog works?

Best regards
Maria

[Lini]

Hi Maria,

Try the 4.32 build. The release notes for that version specify that a problem with the asset pickers was fixed:

Changes in version 4.32 (8/17/2007)

- BUGFIX: Editor scripts were not loaded correctly in some cases. Caused errors with Asset Picker dialogs.

Regards,
Lini
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center