Back To Start Of Archive
Taken From The Forum: Archived Topics for the old Version 3.0 JavaScript Menu
Forum Topic: Click to view post
Last Updated: Wednesday July 18 2012 - 06:07:28
Frames/asp vb script error breaking menus in main page
Poster: sam
Dated: Monday August 5 2002 - 14:53:38 BST
Does anyone have a workaround for dealing with broken menus that occur when a vb script error hoses the main page? We use Frames with a top nav frame, and a bottom display page. When a script error occurs in rendering the bottom display page, its menus are likewise broken...
We are looking for a way either avoiding the broken menus, or handling the error, while repairing the menus so that they work.
Thanks
Poster: menufurfer
Dated: Monday August 5 2002 - 21:45:10 BST
I use a top frame and main area and haven't experienced the problem since I have control over the display pages on the web site. And they don't get ftp'ed to the site until they work as designed on my system.
When you say "script error" do you mean Andy's code or additional code not related to the menus?
If the menu option is a link to an external site (I have a couple of these), the question is irrelevant since the menu links are broken anyway. For these one needs to use the back button to load something onsite. /mfurf
Frames/asp vb sript error: some clarification
Poster: sam
Dated: Tuesday August 6 2002 - 13:37:13 BST
Thanks for your reply.
By "script error" we are not referring to Andy's code; that is rock solid. No, the errors are ours coming from unhandled errors from our asp vb script-- like a stored procedure timing out, or somthing like that.
When you say your "pages don't get ftp'ed to the site until they work as designed", I guess (assuming you use asp) you have extensive error trapping so that unhandled error messages never "slip out" across the wire and end up on the client's browser.
Also, our menu option links are all internal, dynamically generated asp pages, not links to external sites; and you are right, such a broken external link is really another situation.
It seems that in order to force Andy's script code to always render in a target frame, any asp script errors generated during that target's page processing have to be trapped and then re-directed to a page containing the menus that would have otherwise appeared on the broken page...I am just wondering if there are other alternatives to this.
Thanks for your comments. I appreciate you ideas!
sam