Question

I am interested in using more than one web for issue tracking in our wiki. This means multiple BugsContrib webs in one TWiki.

I think it should work except the current BugsContrib package creates a new web named "Bugs" when installed. The first iteration would need to be renamed so the next can come in as "Bugs." In then end, I don't want any of the BugsContrib webs to continue with the name "Bugs" either.

I see that MegaTWiki has a web renaming capability but I am reluctant to patch my entire TWiki to get one function.

I see some other pages with web renaming discussions and manual steps. Should I use these manual processes to accomplish my goal?

Environment

-- AlanDayley - 03 Jan 2007

Answer

No need to patch TWiki with MegaTWiki, TWiki4 supports rename of webs. Although I do not know if the Bugs app survives a rename of the web.

-- PeterThoeny - 03 Jan 2007

Thanks, Peter. Subsequent reading of TWiki4 documentation showed be that web renaming is supported. I did not know this since I have not yet upgraded to TWiki4. That will be step 1 on my way to using the Bugs app.

I may have to test the functionality of the Bugs app after renaming in a test upgrade prior to the "real" one.

-- AlanDayley - 03 Jan 2007

Renaming the Bugs web worked but required a bit of tweaking before and after.

• The BugsContrib? Bugs web has a very sparse WebPreferences page. I had to copy and paste the

%INCLUDE{%TWIKIWEB%.WebPreferencesHelp}%

line from Main.WebPreferences into Bugs.WebPreferences. I could then click on the "Rename/move/delete web..." link, fill out the form and click the Rename/Move button.

• The first time the rename ran, I got some error, I don't remember what it was but it was from the RCS wrapper. When I tried again to document it, it worked!
• There were a few places in the Bugs web that use the word "Bugs" in headers and so on. These places really do mean to indicate bugs, such as the header "Active Bugs" on the Bugs.AllOutStandingItems topic. These text uses of the word "Bugs" were also changed by the web rename script, making for some odd wording depending on the new name. Not a big deal but a funny side effect.

My next step is to install another BugsContrib in the same TWiki. With the first one renamed and working, I expect the second one will work too.

I don't know where else to document this experience so I am doing it here. If there is a better place, point me to it and I'll gladly do the editing.

-- AlanDayley - 11 Jan 2007

The AppliesTo field and page did not match the use I intend which encompasses issues beyond just code bugs. I renamed the page to FocusOn. After renaming the page I found item searches did not work. Searching through the wiki source, I found several places where the AppliesTo name was called out. I changed references in the following files:

* data/Productdev/Tabulator.txt * data/Productdev/WebSearch.txt

After some priority changes, it may be some time before I install a second BugsContrib installation. So, this page still does not report on the question that triggered it. Anyone else is welcome to report success or issues, of course.

-- AlanDayley - 15 Jan 2007

I finally got around to creating a second BugsContrib installation. It is working fine! I did it like this:

• Used the ManagingWebs page to create the new web using the first BugsContrib web as the template. This copied only the Web* topics, as expected.
• Logged into the TWiki server console via ssh.
• Changed current directory to the /path/to/twiki/data/SecondBugsWeb.
• Copied all *.txt files from data/FirstBugsWeb directory except files Web*.
• Deleted all the numbered Item??.txt files.
  • Check that the files ItemTemplate.txt and ItemPriority.txt are not deleted. If so, recopy them from data/FirstBugsWeb directory.
• Issued the command chown -R apache:apache * to set web server ownership.
• Did cosmetic edits SecondBugsWeb.WebHome to change text to match the new web usage.
• Edit FocusOn (aka AppliesTo) page to categories appropriate to new web use.

The first few test issues went into the new web just fine.

-- AlanDayley - 14 May 2007

A couple of steps that I missed:

• Copy the pub/FirstBugsWeb/HideTextarea directory to pub/SecondBugsWeb/HideTextarea
• Issued the command chown -R apache:apache pub/SecondBugsWeb to set web server ownership.

-- AlanDayley - 15 May 2007

---

Change status to: AskedQuestions AssignedQuestions AnsweredQuestions ClosedUnanswered