as i just found out, making a ’back to top link’ that goes to an anchor at the top of the page results in it going to the anchor on whatever is the site start page. ok, so i’d have to make it a variable for each page, and that works, but each page gets totally reloaded, resulting in a brief wait. the wait kinda defeats the purpose of a quick ’click this link to go back to nav instantaneously’ thingy. i assume then that this is a limitation of working with a cms, but i’m just checking to see if there’s any workaround.
my solution is to just have the actual menu links so people can skip to another section rather than a back to menu that reloads the page in order for peeps to skip to another section.
Sorry - not using ModX anymore 01/01/2007
If your pages are long, having menu links at both ends is usually good.
But I think your issue is either due to you not using Friendly URLs, or to the presence of a base href in the template.
Quote from: OpenGeek at Aug 29, 2006, 11:35 AM
This should work fine if you create those links like this:
<a href="[~[*id*]~]#anchorName" title="anchorName">Go to anchorName</a>
...
<a name="#anchorName"></a>
If you try to create them without the URL generated by [~[*id*]~], i.e. href="#anchorName", that is going to always go back to the root of the site.
Mmm... are you sure?
I’ve no problem at all setting anchors like
<a href="#top" title="Go to the top">Go to the top</a>
...
<a name="#top"></a>
@arphaus
Perhaps you’ve set the base-url in your template?