Using MS FrontPage Shared Border (top) to hold a pop-up menu generated by Macromedia Fireworks. The generated HTML file is saved as top.htm which is embedded in the top border of all pages within the web (this is for ease of maintenance of the site menu)
On its own, top.htm functions AOK - the menu does all it should no problem. However, as the top border I get screip errors (missing object) in preview mode within FP. If I previoe in browser I get no script error but the menu does nothing (no rollovers, drop-downs etc).
Have tried exporting the thing from fireworks as both FP html and Dreamweaver html but same results.
I've published to a server but, although there are no script errors, the menu does nothing.
As I say, top.htm is perfect when checked in isolation but only fails as the top shared border. It must be a referncing error to the .js file or something, but I can't suss it. Thanks
I am aware that I can achieve (and have now achieved) what I want via Dreamweaver Templates. The reason I was hoping to use FP is simply that it's a rather large FP site and it would just be easier to leave it with FP.
I would really like to know why FP is letting me down - these things really niggle me!
However, if I can not crack this problem I will just move to the Dreamweaver template route.
it must be a referencing error, and it's obviously being caused by the fact that you've set FP to use a shared border. FP can't handle the fact that the same .js file can be used, regardless of which page you're on, and it's not something that I've come across before.
When I get more time I'll delve into it a little more deeply, because such a thing would niggle me too, but for the time being I think you're right - use DW instead.
As per MS Knowledge base, any script within the header of a page used as a border is ignored. All script must appear within the body.
I cut and pasted all lines of script from the top.htm <head> to <body>. Also, all images used by the .js file were cut from the _borders folder to the web root folder (i.e. the same folder as that in which the .js file resides) and all now works OK.
This thread is now locked and can not be replied to.