I have the Preferences set to "Open Compose In: New Window"... everything is fine until Send is clicked, the page refreshes and gives the error :

'parent.parent.frames.folderlist' is null or not an object

To me it seems like the "new window" is trying to refresh teh folder list of the parent window which does not exist in the child window.

any one else running into this? anyone have a fix? thanks in advance!

It is possible that this is bug that has been found and fixed in a newer version or it may be one that hasn't been discovered until now.  It could also be some problem with your installation. 

If you will provide some additional information about how to reproduce the problem, we will investigate the issue and see what is going on.  Please let us know what version you are using as well as the exact steps to produce the issue.  For example what folder you are in before sending the message and what your preferences are set to?  Also are you seeing this issue for all uses or just one and does it occur for all messages or just certain ones?

We are using Collaboration Suite 2006.1

The issue appears when the Preferences are set to open the Message Window to New window. The error seems to be related to the window trying to refresh the Folder List, which does not exist in the new window with the composer in it. This also occurs on New Messages, Replies and Forwards.

If you need any more info please let me know. This is starting to affect more and more users. Thanks!

Exact Process....

Open Email -> Click New -> Compser window opens -> type out message and To -> Click Send -> Message goes out, page refresshes, error shows.

This issue should be fixed in the release that is scheduled to come out very soon (2006.2).  In the meantime, here is a fix you can make to correct the problem and prevent the error from appearing.

1.  Look in your webclient directory and locate the "javascripts" folder.

2.  Open the MsgList.js file and wrap any references to parent.parent.frames['folderlist'] inside of a try/catch block.  An example of this is show below.

try

parent.parent.frames['folderlist'].updateFolderCount(sFolder,sUnread,sTotal,sAction);

}

catch(e){}

3.  Save your changes to the file and the error should no longer appear. 

Please note that it is always a good idea to make a backup of the original file before making any changes, just in case you make a typo or something along those lines and need to roll back to quickly to correct the problem until you have time track down your mistake. 

If you have any problems or issues, please post a note here and I will try to respond as quickly as possible. 

The fix I mentioned should have corrected the problem.  Is it possible for you to set up a test account that I can use to log in to the webclient and observe the problem myself?  If so, please send a login name/password and a url to tallen@alpha.ipswitch.com.  In the body of the message indicate that the information needs to be forwarded to Marc Rosamond and I will investigate the issue further.  Thanks.

Thanks for setting up the account for me.  Being able to log in and see the error firsthand enabled me to trackdown exactly where it is occurring.  The issue you are seeing is basically a bug which we have since fixed.  That fix will be in 2006.2 which is currently in beta.

As you mentioned in your forum post, the page is calling parent.parent.frames['folderlist'].updateDiskSpace which doesn't exist when the compose page is set to open in a new window.  Unfortunately, this particular piece of javascript is generated by the serverside code and inserted into the page and not in the MsgList.js file as I originally thought.  Since it is being generated by the .Net code that means you don't have the ability to wrap a try/catch block around it to fix the issue in this instance. 

The particular line of code that is causing problems is only executed if you have "open compose in new window" and "Save copy of outgoing messages in sent folder" both enabled in your preferences, so a quick fix would be to disable one or both of those features for your users.  A better, more longterm fix would be to upgrade to version 2006.2 which includes the bug fix.  Although it is still technically still in beta we have finished all development work on it and are just waiting for the marketing/sales and other people to do all the other stuff that goes on when we release a new version.

Anyway I hope this helps answer your question about why the error is occurring and what you can do to fix it.  If you have any further questions or comments, please post them here and I'll respond as quickly as I can.

Thanks,

Marc Rosamond