forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Crossley (JIRA)" <>
Subject [jira] Commented: (FOR-762) Default page URL for breadcrumbs and site: links
Date Mon, 27 Mar 2006 04:42:19 GMT
    [ ] 

David Crossley commented on FOR-762:

It is sometimes necessary to link to a directory listing on a static website.

In my sites, i always have an entry in the site.xml for each "index.html" file or other file
that serves that purpose. Sometimes there is no @label attribute if it is not wanted in the
menu. I never link to the directory listing unless that is what is intended. This enables
everything to work for me in both 'forrest' and 'forrest run' modes. So is this aspect just
a user/documentation issue?

The breadcrumbs issue does remain however.

> Default page URL for breadcrumbs and site: links
> ------------------------------------------------
>          Key: FOR-762
>          URL:
>      Project: Forrest
>         Type: Bug
>   Components: Skins (general issues)
>     Versions: 0.7, 0.8-dev
>     Reporter: helena
>     Priority: Blocker
>      Fix For: 0.8-dev

> When employing breadcrumbs,
> example generated links:  home > dir > subdir
> if the user is in node subdir, then clicks dir,
> cocoon returns "The requested resource "/dir /" could not be found.
> The link's absolute path during testing is http://localhost:8888/dir/
> Case 1. If you place an index.html file under http://localhost:8888/dir/ for a redirect
or viewable content,
> clicking on breadcrumbs'  dir link throws the error.
> Case 2. If you manually enter the index.html in the browser path after http://localhost:8888/dir/,
the request is handled.
> Case 3. If sitemap has match="dir/index.html", cocoon still isn't happy with request
> Cocoon does not appear to assume the end node directory is index.* and thus appends no
file automatically as tomcat or the http server does so it must be manually done. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message