Fireworks pop-up menus with multi directory Dreamweaversites

I'm using Fireworks MX2004 to create a pop-up menu which I'm then exporting to
a Dreamweaver MX 2004 web site. The web site uses templates and is multiple
directories in it's structure.

The problem is that the menu stops functioning an any pages that do not rest
in the root folder. I understand the reason for this is that the .js file that
the menu uses is sitting in the root folder and so the menu will only work with
sites also sitting in this directory.

Is there any way around this problem, so that the menu html in the page
somehow points to the .js file even though it's not the same folder?

I know having a "flat" site layout (i.e. all pages in the root folder) would
get around this problem but this really isn't an option given the nature of the
site.

Thanks for any suggestions.

I'm using Fireworks MX2004 to create a pop-up menu

Why? Have you read the hundreds of posts advising not to use them?

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================

"Charred" <webforumsuser (AT) macromedia (DOT) com> wrote

which I'm then exporting to

a Dreamweaver MX 2004 web site. The web site uses templates and is
multiple
directories in it's structure.

The problem is that the menu stops functioning an any pages that do not
rest
in the root folder. I understand the reason for this is that the .js file
that
the menu uses is sitting in the root folder and so the menu will only work
with
sites also sitting in this directory.

Is there any way around this problem, so that the menu html in the page
somehow points to the .js file even though it's not the same folder?

I know having a "flat" site layout (i.e. all pages in the root folder)
would
get around this problem but this really isn't an option given the nature
of the
site.

Thanks for any suggestions.

Originally posted by: Newsgroup User

I'm using Fireworks MX2004 to create a pop-up menu<BR><BR>Why? Have you
read the hundreds of posts advising not to use them?<BR><BR>-- <BR>Murray ---

ICQ 71997575<BR>Team Macromedia Volunteer for Dreamweaver<BR>(If you *MUST*
email me, don't LAUGH when you do
so!)<BR>==================<BR>http://www.macromedia.com/support/search/ -
Macromedia (MM) Technotes<BR>==================<BR><BR>"Charred"
<webforumsuser (AT) macromedia (DOT) com> wrote in message
<BR>news:cmagn9$89p$1 (AT) forums (DOT) macromedia.com...<BR>which I'm then exporting
to<BR>> a Dreamweaver MX 2004 web site. The web site uses templates and is
<BR>> multiple<BR>> directories in it's structure.<BR>><BR>> The problem is
that the menu stops functioning an any pages that do not <BR>> rest<BR>> in the
root folder. I understand the reason for this is that the .js file <BR>>
that<BR>> the menu uses is sitting in the root folder and so the menu will only
work <BR>> with<BR>> sites also sitting in this directory.<BR>><BR>> Is there
any way around this problem, so that the menu html in the page<BR>> somehow
points to the .js file even though it's not the same folder?<BR>><BR>> I know
having a "flat" site layout (i.e. all pages in the root folder) <BR>>
would<BR>> get around this problem but this really isn't an option given the
nature <BR>> of the<BR>> site.<BR>><BR>> Thanks for any suggestions.<BR>>
<BR><BR><BR>


Did you mean to say "Have you NOT read the hundreds of posts advising not to
use them?".?

In any event I have used them, so if you're able to answer my question then
please do so.

Read these. You should reconsider your use of them....

http://apptools.com/rants/jsmenu.php
http://apptools.com/rants/menus.php


--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================

"Charred" <webforumsuser (AT) macromedia (DOT) com> wrote

Originally posted by: Newsgroup User
I'm using Fireworks MX2004 to create a pop-up menu<BR><BR>Why? Have you
read the hundreds of posts advising not to use them?<BR><BR>--
BR>Murray ---
ICQ 71997575<BR>Team Macromedia Volunteer for Dreamweaver<BR>(If you
*MUST*
email me, don't LAUGH when you do
so!)<BR>==================<BR>http://www.macromedia.com/support/search/ -
Macromedia (MM) Technotes<BR>==================<BR><BR>"Charred"
webforumsuser (AT) macromedia (DOT) com> wrote in message
BR>news:cmagn9$89p$1 (AT) forums (DOT) macromedia.com...<BR>which I'm then exporting
to<BR>> a Dreamweaver MX 2004 web site. The web site uses templates and
is
BR>> multiple<BR>> directories in it's structure.<BR>><BR>> The problem
is
that the menu stops functioning an any pages that do not <BR>> rest<BR
in the
root folder. I understand the reason for this is that the .js file <BR
that<BR>> the menu uses is sitting in the root folder and so the menu will
only
work <BR>> with<BR>> sites also sitting in this directory.<BR>><BR>> Is
there
any way around this problem, so that the menu html in the page<BR
somehow
points to the .js file even though it's not the same folder?<BR>><BR>> I
know
having a "flat" site layout (i.e. all pages in the root folder) <BR
would<BR>> get around this problem but this really isn't an option given
the
nature <BR>> of the<BR>> site.<BR>><BR>> Thanks for any suggestions.<BR
BR><BR><BR


Did you mean to say "Have you NOT read the hundreds of posts advising not
to
use them?".?

In any event I have used them, so if you're able to answer my question
then
please do so.

I'd read both those articles in full before posting here (google will bring
them right up on the subject). I've also seen the numerous recommendations
(many from yourself) for avoiding them.

I AM using them, however, as my situation is quite specific.

I also know what I'm trying to achieve is possible.

Are you able to advise me on how to achieve this? To reiterate once more,
assume I am definately using them at this point.

You could try making your link to the js files a root relative one.

I'm curious what specific need could ever justify the use of such broken
technology.

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================

"Charred" <webforumsuser (AT) macromedia (DOT) com> wrote

I'd read both those articles in full before posting here (google will
bring
them right up on the subject). I've also seen the numerous
recommendations
(many from yourself) for avoiding them.

I AM using them, however, as my situation is quite specific.

I also know what I'm trying to achieve is possible.

Are you able to advise me on how to achieve this? To reiterate once more,
assume I am definately using them at this point.

Can you expand on what that process entails? Is it modifying the javascript
directly in each page?

The "justification" is long winded to be honest. I'm working to design. I'd
use another form of pop-up menus (i.e. non-marcromedia ones) if I knew of an
accessible and appropriate one.

Hi Charred

The JavaScript okay, make it external and link your pages to the .js file,
make sure the links in the js file are pointing to
http://www.yoursite.com/whatever/whatever.html and not
/whatever/whatever.html.

Cheers

Pablo

A local Hero who wears blue tights.



"Charred" <webforumsuser (AT) macromedia (DOT) com> a écrit dans le message de news:
cmaouv$iq6$1 (AT) forums (DOT) macromedia.com...

Can you expand on what that process entails? Is it modifying the
javascript
directly in each page?

The "justification" is long winded to be honest. I'm working to design.
I'd
use another form of pop-up menus (i.e. non-marcromedia ones) if I knew of
an
accessible and appropriate one.

Thanks for the replies. That's a lot to be going on with.

So it's not pop up menus in general that are ropey, but just the firework ones?

I wanted to avoid having to get to grips with anything new and lengthy because
this project has been delayed enough as is. But I will look into the other
options you've suggested.

So it's not pop up menus in general that are ropey, but just the firework
ones?

It's almost any all-javascript menu system, and there are plenty.

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================

"Charred" <webforumsuser (AT) macromedia (DOT) com> wrote

Thanks for the replies. That's a lot to be going on with.

So it's not pop up menus in general that are ropey, but just the firework
ones?

I wanted to avoid having to get to grips with anything new and lengthy
because
this project has been delayed enough as is. But I will look into the
other
options you've suggested.