Hi,

I've got a major problem I cannot solve. I'm working in Dreamweaver MX 2004. A client wanted their site converted into templates. OK, no problem there. However, once completed my jsScript popup menus ceased to work and I can't repair them.

I've tried eveything conceivable. Nothing works. The navBar contains direct links to pages and they seem to work alright. But when I try and use the popup menus to link to another page, it throws an error: page not found. It seems to remain stuck in the last directory while trying to find a new page vis-a-vis a popup item.

This is driving me nuts!! I've tried changing the popup link configuration from ../someDirectory/page.htm to just someDirectory/page.htm. NO LUCK...

For your convenience I've included the link to a tempSite:

Here you can review the problems for yourselves.

I thank you in advance for any help or suggestions you folks can offer me.

Regards,

Gareth

Dani AI

Generated

Following 's report and 's hint, here are practical checks and durable fixes for JS popup menus that stop resolving pages after converting to Dreamweaver templates. The problem is typically about how the browser resolves relative URLs at runtime (document base, a template-inserted <base> tag, or previewing via file://), not a mysterious popup blocker.

Try these steps:

  • Open the page in a browser, use View Source / DevTools and the Network panel to see the actual href requested when the popup link is clicked. That shows whether the path is being rewritten or returning 404.
  • Look for a <base> element in the template head. A base changes how all relative links resolve; removing or adjusting it often fixes surprises. See the HTML base element docs: HTML base element.
  • If the menu builds links in JavaScript, build absolute or root-relative URLs at runtime instead of relying on the page file location. Example pattern:
var url = new URL('/folder/page.htm', document.baseURI).href;
window.open(url, 'popupWin', 'width=600,height=400');
  • Avoid testing purely via file:// previews; run a local HTTP server (for example: python3 -m http.server) so paths resolve like production.

Extra tips: prefer root-relative paths (/path/page.htm) for portability, or generate the full path dynamically if the site moves domains. If Dreamweaver keeps altering links, check the site definition/testing server settings so link generation matches your live layout. For URL construction reference, see the URL API: URL.

Recommended Answers

All 2 Replies

Could it be that they are working, but popups are blocked by either the server or the browser?

Could it be that they are working, but popups are blocked by either the server or the browser?

I figured it out. Rather than using relative links I needed to use direct links with the full address: .

Once I did this they work fine.

Thank you for responding!

Gareth

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.