forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [issues] New comment: (FOR-129) Give forrestbot the ability to upload the breadcrumbs.js file
Date Thu, 01 Jan 1970 00:00:00 GMT
The following comment has been added to this issue:

     Author: Glen Mazza
    Created: Mon, 12 Apr 2004 11:43 PM
So do you really need the ability to upload an alternate specific breadcrumbs.js or it just
that the default one is broken? 

The latter, actually.  I suspect just fixing the default breadcrumbs.js would be simplest.
 But does someone have the write access to forrestbot?

If you click on any of the preview sites [1] you'll notice that the breadcrumbs aren't working
for any of the sites.  So changing the default one to the *old* breadcrumbs.js [2] should
help all of us.

Later, when the forrestbot updates to a new version that can work with the new breadcrumbs.js
file, then go to that *new* breadcrumbs.js version.


View the issue:

Here is an overview of the issue:
        Key: FOR-129
    Summary: Give forrestbot the ability to upload the breadcrumbs.js file
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Forrest
  Component: Forrestbot

   Reporter: Glen Mazza

    Created: Mon, 12 Apr 2004 1:02 AM
    Updated: Mon, 12 Apr 2004 1:02 AM
Environment: standard Apache forrestbot at

(From the XML Apache FOP team)

As discussed here [1], after running the publish command from the forrestbot we need to manually
update the breadcrumbs.js within xml-site/targets/fop/skin directory [2].  (The forrestbot
overwrites our breadcrumbs.js with a version that does not work.)

I see no way to currently switch the buggy version that the Forrestbot uses to overwrite the
breadcrumbs.js file.

As an enhancement, to save us the need for the manual reversion everytime we publish the site,
give Forrestbot the ability to read content/skin/breadcrumbs.js in our project directory [3]),
and use *that* file when it publishes to xml-site.

Of course, content/xdocs/* and content/skins/** already transfer over (as defined here [4],
also see [5][6] for the Forrest site, for example.)  We just need the ability for content/skin/breadcrumbs.js
to do the same.

Glen Mazza
Apache FOP Team 


This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message