Member Avatar for saucy6969

Hi there, I am working on a site for my organisation's festival and all seems to be going well outside of 2 pages having issues. I basically copied the same code throughout the site for the navigation buttons but once you are on the "PROGRAM" and "SPONSORS" pages, the rest of the navigation buttons don't work. Can anyone have a look and let me know if there is something I missed?
Click Here

Cheers!

  • 3 Contributors
  • 2 Replies
  • 274 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by blackmiau
asdfghjklasdfgh commented: bad question... +0

Dani AI

Generated

Thread shows reported navigation links that work site-wide except on the PROGRAM and SPONSORS pages; and noted the OP later solved it but did not record the cause. The absence of a root-cause post leaves a gap for future readers. Below is a compact, prioritized checklist and quick fixes that address the usual reasons links stop responding only on specific pages.

Most likely culprits (short list)

  • Invisible/transparent element overlaying the nav (z-index, fixed positioning, or an absolutely positioned container).
  • JavaScript error on those pages that aborts event handling (check Console).
  • Resource path differences (scripts/CSS loaded via relative paths that break when page path differs).
  • CSS rule like pointer-events: none applied to the link or a parent.
  • HTML structure problems (unclosed tags) creating unexpected stacking/coverage.
  • Stacking-context quirks (transforms or opacity on parents change z-index behavior).

Diagnosis checklist (in order)

  1. Check the browser Console for JS errors and the Network tab for 404s on scripts/CSS.
  2. Disable JavaScript briefly — if links work, the problem is script-related.
  3. Inspect the problem spot with DevTools: observe which element is on top. In Console try:
    var el = document.elementFromPoint(200,100);
console.log(el && el.outerHTML);

    Adjust coordinates to the non-responsive area.

  4. Temporarily add simple outlines to reveal overlays:
    
/* debug only */
  • { outline: 1px solid rgba(255,0,0,0.15); }
    a { background: rgba(0,255,0,0.03); }
  1. Check computed styles for pointer-events, z-index, position, and any transform on parents.

Quick fixes and cautions

  • If an overlay blocks clicks, remove it or set .overlay { pointer-events: none; } only as a diagnostic; this disables its interactivity.
  • Raising nav z-index (.nav a { position: relative; z-index:9999; }) can help but may hide intended elements—fix the underlying HTML/CSS layout instead.

Because and confirmed a resolution without details, this checklist aims to help future readers reproduce the problem and apply a safe fix.

Member Avatar for radenli

It seems like you solved your problem. I didn't see any there.

Member Avatar for blackmiau

Because it has been solved by the poster.

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.