[opencms-dev] FW: Static export publishing of"anchor" linksfailsin 6.0.0

[apoorv.durga at wipro.com]

This works if the links are in template.

What we are facing is a slightly different problem. Let's say there's a
page created using the rich text editor called faq.html. This has number
of items, each pointing to an anchor tag on another page called
details.html. These pages are create by content editors using the rich
text editors and they link from one page to another using the lonk and
anchor buttons  found on the toolbar of the editor.

Now when we do a static publish, opencms is unable to resolve anchor
links that point to an anchor on another page. For example if the links
are:

Page1.html
===========
<a href="#">Top</a>

<a href="/somepath/page2.html#anchor">Glossary</a>

The first link is resolved properly in the static export as it is a link
to anchor on same page whereas the second link which points to another
page is resolved to dynamic site and not to static site. If I remove the
"#anchor" from second link, it also gets resolved properly.


> -----Original Message-----
> From: opencms-dev-bounces at opencms.org
> [mailto:opencms-dev-bounces at opencms.org] On Behalf Of
> Christian Steinert
> Sent: Wednesday, March 01, 2006 4:25 AM
> To: The OpenCms mailing list
> Subject: Re: [opencms-dev] FW: Static export publishing
> of"anchor" linksfailsin 6.0.0
>
> Nigel Kersten wrote:
> >
> > On 25/02/2006, at 8:39 PM, Jonathan Woods wrote:
> >
> >> Assuming you're generating links like this:
> >>
> >> <a href="<cms:link>/path#anchor</cms:link>"
> >>
> >> you could instead put the anchor outside the <cms:link> tag's body:
> >>
> >> <a href="<cms:link>/path</cms:link>#anchor.
> >
> >
> > This brings up an interesting point I've been wondering about.
> >
> > I'd always assumed that Jonathon's suggestion is the
> 'correct' way to
> > use cms:link ?
> >
> > ie, that the idea is that OpenCMS 'knows' what the relevant
> URL in the
> > current context is for '/vfs/path/to/some/file' in
> >
> > <cms:link>/vfs/path/to/some/file</cms:link>
> >
> > and to instead put the anchor, or any parameters like ?___scale or
> > anything else inside the cms:link tag would be incorrect,
> as you're no
> > longer referencing a VFS object inside the cms:link tag?
> >
> >
> Dear Nigel,
>
> all request parameters must be INSIDE the cms:link - tag.
> Only like that the CMS  can know that there are various
> requests with different parameter sets that go to the same resource.
>
> But Anchors are only interpreted by the browser. Therefore
> anchor references have to stay OUT of cms:link
>
> Christian
>
>
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list To
> change your list options, or to unsubscribe from the list,
> please visit http://lists.opencms.org/mailman/listinfo/opencms-dev
>


The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com