BugsContrib


After manually installing the BugsContrib into an existing web with a different name, I'm wondering what is the "correct" way to do this?

I notice that in some places "Bugs." is hardcoded into the topic text, while other places INCLUDINGWEB or WEB macros are used. Is the idea that BugsContrib is installed in the (default) Bugs web, and that its topics are then included in the other web where it is desired to track bugs or tasks etc?

In my install I changed the created page name to TaskXXXXXX, and I wonder if this can be parameterised through a preference variable eg Bug or Item or Task or Issue. Also would apply to "Open Tasks for X" etc.

-- EliotBlennerhassett - 14 Apr 2009


i'd like to add the FormPlugin as a dependency to BugsContrib, to provide a better-looking form view and better data entry and validation. any objections?

-- WillNorris - 02 Feb 2010

Can we think about this a little? BugsContrib has (to date) been an example of a dataform app that works using the core that we distribute. This has always seemed like a positive.. And while I'd like FormPlugin to be part of the core, it needs more work to get to that point.

I think it would be worth enumerating what changes you perceive as being difficult without it - or just making FormPlugin ready for core..

-- SvenDowideit - 02 Feb 2010


Topic revision: r3 - 02 Feb 2010, SvenDowideit - This page was cached on 19 Oct 2020 - 12:54.

The copyright of the content on this website is held by the contributing authors, except where stated elsewhere. See Copyright Statement. Creative Commons License    Legal Imprint    Privacy Policy