|
I just upgraded my Imail 8 to the latest 2006 build. Here are my comments on what I modified.
Useroptions.aspx - Placed comment tags around the "forward to address" section. Removing it causes a server error so I had no choice but to comment it out. Am I the only person who doesn't want their users forwarding their mail out? This should be an option to disable.
<!--
<tr>
<td valign=top width=40></td> <td class=contentLabelCell valign=top nowrap><asp:label id="lblUserOptsAddToForwardTo" runat="server"></asp:label></td> <td class=contentLabelCell valign=top width="100%"><asp:textbox id="txtForwardAddress" runat="server" width="240px"></asp:textbox></td></tr> -->
Also commented the change password section out as I don't want my users even knowing that changing the password is an option. I have integrated Imail with my portal and use ODBC for the database. All changes are done via the portal. This should be an option to hide.
Toolbar.aspx - Wrote _javascript_ to set a page title. Setting it in Default.aspx where it really should be so I did it with this hack: <script>parent.document.title = "My Page Title"; </script>
Obviously this needs to be part of Imail natively... Its a simple page title... Basic html from 15 years ago.
I wanted to change the help url to use my global help system and change the Logout link with an Exit link to close window. Tried changing the links in toolbar.ascx but removing the server side garbage causes an error. I did it with _javascript_ and an onload event handler in the body tag of toolbar.aspx. This needs to be an option to change the links for help and logout.
<script>
function qlink()
{ document.getElementById("ucToolbar_lnkLogOut").innerHTML='Exit'; document.getElementById("ucToolbar_lnkLogOut").href=''; document.getElementById("ucToolbar_lnkLogOut").target='_parent'; document.getElementById("ucToolbar_lnkHelp").innerHTML='<a href="" >Help</a> ';
} </script> Login.aspx - Hid the language dropdown list per the documentation on the Ipswitch site. Not a big deal except the next upgrade I run it will simply overwrite my change and I have to do it again. Just a needless hassle.
Composemsg.aspx - It really bothered me that the compose box was locked at 263 pixels. I want it to fill all of the remaining space below the toolbars. I tried changing the height of the editor box with _javascript_ using an onresize and onload event handler. The onresize worked perfectly but the onload wouldn't work. I determined that Ipswitch added an onload to the page to fire "SetFocus()" but the code is compiled in their DLL. The thing is uneditable so I had to create this hack. Basically I had to add the same function name at the bottom of the page with their code and mine inside the function so both would fire. You can't have 2 onload calls on the same page. Is there a reason the editor window is locked to such a small size?
<script> //on resize make editor bigger window.> //hack to override the compiled use of the onload variable
//just recreated setfocus function and included my code to run resizewin window.>function SetFocus()
{ resizeWin(); //ipswitch original contents of SetFocus()
document.compose['txtTo'].focus(); } function resizeWin() { //height of top toolbars
height = 240 //set height of editor box to the window height minus the toolbar height
document.getElementById("txtMessage_designEditor").style.height = document.body.clientHeight-height + "px" } </script> |
