Archived from ZwikiIssueTracker. Use that page for new comments.


Nice, Simon! --SunirShah

thanks Sunir.

4-dec-2001 17:15 Israel (via web too...):

Excellent! I love the idea of a tracker within the ZWiki! but the ZCatalog instructions are kinda greek to me... I'll improvise on a throwaway wikiweb before I try it on my real one, and add my comments here if I succeed. if anyone can simplify/expand on stages 2 through 4 and specify minimal working version for stage 1 (I just got 0.9.8 so I guess I'm ok), I'll be really grateful!

...and more at 19:45 - I defined the meta-data, what indices do I need? I'm not sure I totally understand the issues with managing the ZCatalog. plus IssuePrototype? seems to have its source hidden... any help? :-) End of the day, tommorow I'll get on the ZWiki list, promise :)

I still can not get a copy of issue prototype. I am also not clear on the catalog business. Thanx
Daniel

Daniel Mahler <mahler@cyc.com>, 2001/12/12 17:43 US/Pacific (via mail):
It would be nice to integrate ZwikiIssueTracker with WikiMail. When somebody submits a bug, autoamtically subscribe them to the page generated for the issue. One could also add a process for assigning issues to resolvers: Initially a triage person is autoatically notified of each issue creation, and subscribed to each issue page. When the triage person assigns an actual resolver, the resolver is also subscribed.

Daniel

2001/12/16 16:55 US/Pacific (via web):
updated this and HowToInstallAZwikiCatalog - hope it helps

2001/12/17 01:19 US/Pacific (via web):
Thanks This makes it a lot clearer. I am still having a few problems, but at least they are specific.

  1. It seems like we now need to get the render_issuedtml method from somwhere. Where?
  2. I cannot view any of the pages I have created. The main Tracker page complains about sort_order (despite appearances, I am using Zope-2.4.3 - I patched the original source directory):

Simon Michael <simon@joyful.com>, 2001/12/17 13:31 US/Pacific (via mail):

> 1. It seems like we now need to get the render_issuedtml method from
> somwhere. Where?

zwiki 0.9.8


> 2. I cannot view any of the pages I have created. The main Tracker
> page complains about sort order ...
> Error Type: KeyError?
> Error Value: sort_order

It seems to be from this code in the Tracker page:

 _.getattr(REQUEST,'sort_order','')

I don't know how this can cause a keyerror - it doesn't on the zope/python combinations I've tried - but I think you are not the only one seeing this problem.

Daniel Mahler <mahler@cyc.com>, 2001/12/17 13:51 US/Pacific (via mail):
206.184.139.140 writes:

 > ++added:
 > It seems to be from this code in the Tracker page::
 > 
 > _.getattr(REQUEST,'sort_order','')
 >

That's what I figured. I even tried setting a sort_order string property on both the page and on the whole wiki, with no effect:

 > I don't know how this can cause a keyerror - it doesn't on the
 > zope/python
 > combinations I've tried - but I think you are not the only one seeing
 > this
 > problem.

The GetattrProblem? is either an instance of the same thing or something very similar.

Daniel

anon
just think an instant instead of moaning

_.getattr(REQUEST,sort_order, '') GetAttribute? sort_order FROM REQUEST so ? as you're debugging this frigging mess, just add ?sort_order=value to your url

AND sort_order is the sorting attribute to dtml-in tags, it's only an matter of presentation. if it crash your work, and you don't know why, just comment it out or trash all references to it

2002/02/19 22:01 GMT (via web):
How can I copy three pages needed to setup a WikiTraker?? (ZWikiTracker?,AddIssue?,IssuePrototype?) When I try I only get pages as they are in this wiki Thanks Robert@recor.ch

Simon Michael <simon@joyful.com>, 2002/02/20 16:27 GMT (via mail):
To copy the source, click edit this page on this site and copy from there. Paste that into the corresponding edit form on your site. Then you may need to adjust the page type etc. as described elsewhere.

anon
I can't edit the source for AddIssue? to grab it, and I don't know what defaults are used for issue_categories, issue_severities, issue_statuses. help? Maybe ('user-browsing', 'user-editing', 'user-editing-stx', 'user-editing-rst', 'user-editing-moin', 'user-editing-wwml', 'user-editing-plaintext', 'user-editing-html', 'user-editing-epoz', 'user-editing-extedit', 'user-editing-stxlatex', 'user-pagehierarchy', 'user-rating', 'user-mail', 'user-issuetracking', 'user-dtmlscripting', 'user-fittests', 'user-purplenumbers', 'admin-installing', 'admin-configuring', 'admin-customizingskins', 'admin-defaultcontent', 'general-i18n', 'general-plone', 'general-skins', 'general-docs', 'general', 'site-zwiki.org', 'site-plone.zwiki.org', 'site-zopewiki.org', 'other')..?

SM
http://zwiki.org/AddIssue/editform

This site's current issue_severities:

 critical
 serious
 normal
 minor
 wishlist

issue_categories:

 don't know
 zwiki: installation
 zwiki: general
 zwikidotorg template
 zwiki.org
 zwiki tracker
 other

issue_statuses:

 open
 pending
 closed

anon
Cool; thanks. I get a Zope error on this page: Zope Error Zope has encountered an error while publishing this resource. Error Type: KeyError?? Error Value: sort_order

PB
I am flattered. However, the main feature of IssueTracker (formally named SiteTracker?) is its simplicity. It was originally built for visitors of a website to use and if a visitor is going to spend the time you want to make it as simple as possible for them.

I shall study this product closely to see if I can learn something from it to my benefit. Perfect!

SimonMichael, 2002/04/08 03:05 GMT (via web):
Thanks for the feedback Peter. I think it's about as simple as the original SiteTracker? I looked at - same basic UI features - am I wrong ? It may seem otherwise because of the wiki stuff going on around it ?

2002/04/19 22:16 GMT (via web):
Is this up to date for 0.9.9?

warning, this is probably out of date. Bring your wellington boots.

Simon, 2002/05/21 18:33 GMT (via web):
Integrated AddIssue?'s form & issue creation code into ZwikiIssueTracker. You can update your [zwikidir/Extensions/mailin.py]? (like this ) and get rid of AddIssue? if you like.

2002/06/24 23:09 GMT (via web):
I had to add in a lastEditTime index -- docs should be updated, or dtml/html on tracker page, that is.

Simon Michael, 2002/06/28 00:32 GMT (via mail):
Updated the index & metadata lists on HowToInstallAZwikiCatalog .

Simon, 2002/08/11 22:54 GMT (via web):
Installation instructions changed above - the issueprototype page is no longer required.

DeanGoodmanson, 2002/09/18 01:20 GMT (via web):
Added some information to the Install text.

Copying FilterIssues is also helpful.

Especially helpful for stealing the code from the Frontpage for the links.

In the front page it may make sense to put the dtml-let numissues be just around the latest bugs block. page.

WimBekker, 2002/09/18 15:00 GMT (via web):
Where do I put issue_.. variables?

DeanGoodmanson, 2002/09/18 16:32 GMT (via web):
Wim - Put your issue_* properties in your wiki's folder properties.

WimBekker, 2002/09/23 10:49 GMT (via web):
Ok, it's running, thanks to point 3 above! Next question, if I inspect an issue, I have the page with the '<<',^^ and >>. But the ^^ links to ZwikiIssueTracker and mine tracker has another name. How can I change the link?

Simon, 2002/09/23 16:07 GMT (via web):
It's hard-coded in Tracker.py, you'll have to change it there. Congrats on getting it working, by the way. I don't hear that too often.

DeanGoodmanson
I added a bunch of lines in the online ZWikiTracker? page noting which lines need be commented, perhaps I forgot similar comments in FilterIssues ?

DeanGoodmanson, 2002/10/07 05:01 GMT (via web):
What is the line < dtml-var title missing html_quote> in the "Issue title:" section for?

For me it puts the page name (BUGTracker?) in the title of the Bug, which (I think) trounced . More later.

BillSeitz, 2002/11/20 (via web):
re 9/23 comments, I have a similar but more nasty problem. When adding a new issue I get an error message because it seems to be posting to ZwikiIssueTracker instead of my pagename (IssuesView?). But the issue actually gets added anyway. (I see ZwikiIssueTracker hard-coded in mailin.py - is that the issue (even though I haven't done anything to turn on mail features)?)

Never mind, I found the redirect DTML code the ZwikiIssueTracker page (that even had a comment sayng it needed to be renamed, doh!). All working now.

But this raises the question: why do the instructions say to use a different name for the form, if it's going to be hard-coded in various places anyway! I would recommend that a new name be used everywhere (I'd vote for IssueTracker something like that), so that the hard-coding can be left as is for now.

SimonMichael, 2002/11/21 18:32 GMT (via web):
Hi Bill - I agree with you, what are these developers playing at.

Ok, I'm renaming this site's tracker page to IssueTracker. I'll still call the implementation ZwikiIssueTracker.

Simon, 2002/04/08 23:36 GMT (via web):
Turned off the header/footer on the main tracker pages to see how it works out.

DeanGoodmanson, 2002/10/03 14:37 GMT (via web):
I am very interested in ZwikiIssueTracker . I see a large number of feature requests, and a few bugs.

SimonMichael, 2002/12/05 19:37 GMT (via web):
I renamed ZwikiIssueTracker -> ZwikiIssueTracker -> IssueTracker as promised. Seems to have been painless.. I replaced the ZwikiIssueTracker name in mailin.py and the tracker page dtml. Also fixed a small bug with the new issue title field.

ZwikiIssueTracker has lots of backlinks, but I think most of them will make sense - change ZwikiIssueTracker links to IssueTracker wherever it seems needed.

DeanGoodmanson, 2002/12/05 20:47 GMT (via web):
IssueTracker page changed

I'd like to modify IssueTracker to be a purely copy/pastable page. First by making all references to ZWiki links RemoteWikiLinks, well, that's all I can think of for now. I think most of the other stuff was related to teh page name itself.

Nifty job chucking the comment area.

DeanGoodmanson, 2002/12/06 06:47 GMT (via web):
IssueTracker changes

Very glad for the page name change. My previous implementation annoyances are now only in the previous statement. (Haven't check FilterIssues or FrontPage yet, though.)

Here's my suggestion for the following block in IssueTracker:

This is the ZWiki bug database. The last ten issues modified are shown by default.

To perform more advanced search queries visit FilterIssues, and for more search help see ZWiki:TrackerSearchTips.

For issues you will probably hit when implementing a ZWiki visit ZWiki:IssueTracker and ZWiki:KnownIssues.

For discussion and more information on this tool visit ZWiki:ZwikiTracker.

Other related bug lists: zope bugs, debian zope-zwiki bugs and ancient ZWiki:ZwikiProblems.

Toni Arnold, 2002/12/08 22:01 GMT (via web):
Installation of an IssueTracker is annoying, so I automatized it with a SetupIssueTracker? script.

DeanGoodmanson, 2002/12/09 02:39 GMT (via web):
AdminHowtos

Thank you !!!

Hopefully later this can be seperated for two other seperate parts: Set a Catalog, Setup an IssueTracker

Toni, Have you had other IssueTracker type extension thoughts for ZWiki? Your input at ZwikiRecordBook would be appreciated. Your code helps this effort also.

SimonMichael, 2002/12/09 21:36 GMT (via web):
Nice one Toni - this brings #267 simpler catalog setup/268 much closer. I hope to offer these as options on the add zwiki web form.

DeanGoodmanson, 2003/01/06 02:54 GMT (via web):
Did you use regulations to hide the comment box?

SimonMichael, 2003/01/07 14:11 GMT (via web):
Permissions, yes. I disable add comments permission on the tracker page to make it simpler.

Test

FlorianKonnertz, 2003/01/11 09:46 GMT (via web):
Installed tracker without problems on Zope-2.5.0, Zwiki-0.13.1, (manually); - Cool!

Some examples and experience reports how to use it in certain environments (company intranet, ProjectManagement?, TodoLists?) would be good to have. I gonna see if it's useful to shift to the tracker from my current todolists and report.

TrackerDiscussion? , refactoring --FlorianKonnertz, 2003/02/02 06:14 GMT
What about an extra TrackerDiscussion? page. I'd like to add some info about tracker usage in SubWiki-s, but it's not clear where the DocumentMode? stops and the ThreadMode? begins, so i'd do some refactoring if you also want.

RefactorMe --FlorianKonnertz, 2003/02/05 08:36 GMT
RefactorMe

2003/02/06 20:52 GMT
Here is a comment

Inside of Plone? --JMR Sat Feb 8 15:13:16 CST 2003
Does the issue tracker work inside an CMF environment like plone?

Installed OK, can't add any issues --JBD 2003-03-18 14:26 CST
Clean Zope 2.6.1, Zwiki 0.16.0 using setupIssueTracker script (very nice!) When I try to add an issue I get a KeyError?: ZWiki.Tracker, line 161, in CreateIssue?. Anybody know what might be wrong?

Installed OK, can't add any issues --SimonMichael, 2003/03/18 20:53 GMT
Note tracker code is in flux at the moment. Use the code in ZWiki/content/tracker/IssueTracker.stxdtml for your tracker page, not this site's IssueTracker which requires the latest zwiki-cvs.

issue tracking resources --DeanGoodmanson, 2003/03/20 15:06 GMT
Good article on Issue Tracker etiquite: http://bugzilla.mozilla.org/page.cgi?id=etiquette.html

Thanks to [Roundup]? blog : http://www.mechanicalcat.net/cgi-bin/log/python/oss_projects.html

ZwikiIssueTracker upgraded --SimonMichael, 2003/03/21 23:22 GMT
I think the tracker changes for 0.17 are complete. Bugs have been squashed, there are no more issuedtml pages on this site, and upgrade issues have been worked out. AdminHowtos has some notes, if you have a tracker I'd like to know if they match your experience.

One unforeseen consequence of all this: changing an issue description (used to be "title") in a big wiki is now much slower, because it means a page rename. It's issue 474 if you find a solution. Otherwise, it seems to have all worked out well.

AttributeError? --FlorianKonnertz, 2003/03/22 14:43 GMT
I upgraded today to 0.17cvs, latest tracker and filterissues code, i updated my catalog and did the upgradeAll action, and now get the following error - do you have any ideas:

  Traceback (innermost last):
    * Module ZPublisher.Publish, line 102, in publish
    * Module ZPublisher.mapply, line 88, in mapply
    * Module ZPublisher.Publish, line 43, in call_object
    * Module Products.ZWiki.ZWikiPage, line 215, in __call__
    * Module Products.ZWiki.ZWikiPage, line 227, in _render
    * Module Products.ZWiki.ZWikiPage, line 399, in render_stxprelinkdtmlfitissuehtml
  AttributeError: hasFitTests

AttributeError? --SimonMichael, 2003/03/25 00:12 GMT
Ah.. the main code assumes hasFitTests but it wasn't defined if you don't have fit installed. cvs update Fit.py now and it should work, thanks.

appending comments to issue property change. --DeanGoodmanson, 2003/04/04 04:25 GMT
Code change:

    def changeIssueProperties(self, title=None, category=None, severity=None,
                              status=None, note=None, REQUEST=None ):
        """
        Change an issue page's properties and redirect back there.

        Less flexible but more secure than changeProperties.

        It expects title to be the issue description, not the complete
        page name.  Changing this will trigger a page rename, which may be
        slow.

        XXX security: allows title/category/severity/status properties to
        be set without Manage properties permission.
        """
        comment = ""
        if title:
            # title
            # XXX upgrade issue: if they have not yet upgraded to
            # 0.17-style issue page ids, this will mess things up.
            comment += "Title changed from:"+self.title_or_id()+" to:" # this one may go?
            title = self.getId()[:11]+' '+title
            self.rename(title,updatebacklinks=1,sendmail=1,REQUEST=REQUEST)
            comment += title+" ... "
        if category:
            comment += "\nCategory changed from:"self.category+" to:"+category+" ... "
            self.manage_changeProperties(category=category)
        if severity:
            comment += "\nSeverity changed from:"+self.severity+" to:"+severity+" ... "
            self.manage_changeProperties(severity=severity)
        if status:
            comment += "\nStatus changed from:"+self.status+" to:"+status+" ... "
            self.manage_changeProperties(status=status)
        if not note:
            note = "Property change."
        self.comment(text=comment, use_heading=1, subject_heading=note, REQUEST=REQUEST)
        self._setLastEditor(REQUEST)
        self.reindex_object()
        if REQUEST:
            REQUEST.RESPONSE.redirect(self.page_url())

Form change:: Note:   

IssueTracker change --DeanGoodmanson, 2003/04/04 04:27 GMT
Well that got messed up. Sorry...here it is again.

NOTE: THIS CODE HAS NOT BEEN RAN, LET ALONE TESTED!

detail page change :

 <b>Note:</b> <input type="text" name="note" value="" size="55" maxlength="55">&nbsp;&nbsp;

IssueTracker change --SimonMichael, 2003/04/04 06:44 GMT
Hmm.. like that ?

Nice one!! Let's play with it.

next prev , top links in issue view: << ^^ >> --DeanGoodmanson, 2003/04/04 19:10 GMT
These look to be dropped in the latest incarnation.

When my peer noted that the ^^ were links to "ZwikiIssueTracker", the discussion concluded with: These navigation links are not needed (and may be mis-understood when jumping for a filtered list) but having a link back to the main IssueTracker page is important (previous ^^).

next prev , top links in issue view: << ^^ >> --SimonMichael, 2003/04/04 19:41 GMT
I've been wondering where those went..

I agree, some easy link back to IssueTracker (that works in simple/minimal mode) is useful.

next prev , top links in issue view: << ^^ >> --SimonMichael, 2003/04/04 19:54 GMT
But,

hard-coding a link to IssueTracker doesn't seem like the answer. Could link to the (first) parent, but that seems a bit confusing. So I'm not sure how to improve it.

next prev , top links in issue view: << ^^ >> --DeanGoodmanson, 2003/04/04 21:56 GMT

>> hard-coding a link to IssueTracker doesn't seem like the answer.

Yes, but can it wait until the bigger issues (multiple trackers/wiki) get addressed? For a user savvy (or obscure) enough to not use IssueTracker as their main tracker page (which I wouldn't recommend, based on default FilterPages? and FrontPage tracker views), they'll probably be using something with a heirarchy (we plan to, even in simple mode)...

With all that, my recommendation if you want to bother to put it in: Don't display it if the page doesn't exists, similar to the edit page's TextFormattingRules.

Closing thought: Why do I have a sudden urge to go an ASCII art exhibition this weekend?

tracker upgrade notes --DeanGoodmanson, 2003/04/08 02:53 GMT
I had to recatalog (clear and find) after upgrading (upgradeAll) to get my issue pages to be recognized. Bad news without it--multiple IssueNo001?'s.

The FrontPage code from the past needed more work than changing the catalog lookup. Easily rectified by grabbing the latest from here.

The isIssue implicit property was a bit confusing, but I haven't grokked catalogs yet. The method was enlightening.

I attempted to dtml-ify the "last 5 changes", filterissues, adn issuetracker with mixed success. a. Wanted to put it in /wiki/support, but coudln't figure out dtml-var wiki.support.method calls, and didn't want to dtml-with it, so ended up putting them as filterissues_dtml names in wiki. Lost STX formatting and wikilinking,without regret, and added a couple of wikilink calls for the headers. (b.horribley tried it as a wikipage from the Add a Zwiki Page menu...gave up quick) c. What's the trick to passing in the number of items to the "last five issues" method? I can deal with/without the value when I get it, but can't figure out how to pass it in.

Detail pages seem to render in a similar speed as before, while IssueTracker and Filter issues are much faster (about as long as a detail page.)

Strange crash --DeanGoodmanson, 2003/04/16 14:18 GMT
I haven't found much information about a "guarded item" crash, but seem to be experiencing it when trying to Add a string field to each issue and add a couple of statuses. I've made the appropriate (duplicate the pattern) changes to Tracker.py, folder properties, each tracker page (added property), and Catalog (added fields/metadata,toasted recycle_bin objects, cleared & re-found), yet I get the following traceback on an original IssueTracker page. Note: On other wikis in the same server that have only had the tracker.py and new field added, the "old" page support does not crash. Heres the old IssueTracker crash with the updates above :

 File /Zope251/lib/python/DocumentTemplate/DT_Let.py, line 76, in render
    (Object: open=&quot;_.len(Catalog(isIssue=1,status='open'))&quot;
 pending=&quot;_.len(Catalog(isIssue=1,status='pending'))&quot;
 closed=&quot;_.len(Catalog(isIssue=1,status='closed'))&quot;
 tracked=&quot;open+pending+closed&quot;)
  File /Zope251/lib/python/DocumentTemplate/DT_In.py, line 695, in renderwob
    (Object: issue_statuses)
  File /Zope251/lib/python/DocumentTemplate/DT_Util.py, line 159, in eval
    (Object: _[_['sequence-item']])
    (Info: _)
  File &lt;string&gt;, line 2, in f
  File /Zope251/lib/python/AccessControl/DTML.py, line 32, in guarded_getitem
    (Object: IssueTracker)
  File /Zope251/lib/python/AccessControl/ZopeGuards.py, line 90, in guarded_getitem KeyError

My next step is to flush cache and upgradeAll to clear pre-renders. (right?)

Anything else I should do?

strange crash-source found --DeanGoodmanson, 2003/04/17 14:03 GMT
By removing the section open/pending/closed and open/total sections I was able to render and get around my problem with also removing this code:

 <dtml-let
 open="_.len(Catalog(isIssue=1,status='open'))"
 pending="_.len(Catalog(isIssue=1,status='pending'))"
 closed="_.len(Catalog(isIssue=1,status='closed'))"
 tracked="open+pending+closed"
 >

As FilterIssues gathers the same information I'm going to try to gather it that way.

python script. For use with IssueTrackerZPT. --FlorianKonnertz, 2003/04/17 15:10 GMT
I extracted the catalog query part as a python script. For use with IssueTrackerZPT. - just FYI.

FogBUGZ? sounds very nice --simon, 2003/04/26 20:45 GMT
http://fogcreek.com/FogBUGZ , mentioned on ZwikiScrumDiscussion. To read: http://www.fogcreek.com/FogBUGZ/help/PainlessBugTracking.html .

Lots in common with ZwikiIssueTracker, and should be mined for ideas. See also CVSTrac?.

Strange crash --Simon Michael, 2003/04/26 20:51 GMT
zwiki-wiki@zwiki.org (DeanGoodmanson) writes:
> a couple of statuses. I've made the appropriate (duplicate the pattern)
> changes to Tracker.py, folder properties, each tracker page (added

Did you update your issue_statuses folder property ?

You can tell (pretty much) from the traceback that's what it's complaining about. It's got a sequence-item that doesn't exist in issue_statuses. So either issue_statuses needs something added, or your loop is coming up with unexpected items. You could also try putting the offending line inside dtml-try, and in the except clause print sequence-item and anything else interesting (these may be in angle brackets so you may need to view source).


comments:

... -- 2003/07/31 20:55 GMT reply
I'm having a problem with IssueTracker (zwiki 0.20.0rc3) where, after following the directions in AdminHowtos and adding a IssueTracker page whose content was grabbed from ZWiki/content/tracker/IssueTracker.stxdtml, when I attempt to go to /wiki/IssueTracker, I get:

  <pre>
  NameError
  Sorry, a site error occurred.
  Traceback (innermost last):
  File C:\Usr\ZOPEDE~1.1\lib\python\ZPublisher\Publish.py, line 150, in publish_module
  File C:\Usr\ZOPEDE~1.1\lib\python\ZPublisher\Publish.py, line 114, in publish
  File C:\Usr\ZOPEDE~1.1\lib\python\Zope\__init__.py, line 159, in zpublisher_exception_hook
    (Object: wiki)
  File C:\Usr\ZOPEDE~1.1\lib\python\ZPublisher\Publish.py, line 98, in publish
  File C:\Usr\ZOPEDE~1.1\lib\python\ZPublisher\mapply.py, line 88, in mapply
    (Object: IssueTracker)
  File C:\Usr\ZOPEDE~1.1\lib\python\ZPublisher\Publish.py, line 39, in call_object
    (Object: IssueTracker)
  File C:\Usr\ZOPEDE~1.1\lib\python\OFS\DTMLDocument.py, line 127, in __call__
    (Object: IssueTracker)
  File C:\Usr\ZOPEDE~1.1\lib\python\DocumentTemplate\DT_String.py, line 473, in __call__
    (Object: IssueTracker)
  File C:\Usr\ZOPEDE~1.1\lib\python\DocumentTemplate\DT_Let.py, line 75, in render
    (Object: Catalog="_.getattr(folder(),getCatalogId())")
  File C:\Usr\ZOPEDE~1.1\lib\python\DocumentTemplate\DT_Util.py, line 159, in eval
    (Object: _.getattr(folder(),getCatalogId()))
    (Info: folder)
  File <string>, line 2, in f
  NameError
  </pre>

Any suggestions?

-roy

... --DeanGoodmanson, 2003/08/01 01:04 GMT reply
Roy - Try emptying your recycle_bin folder, then empty and re-catalog your catalog.

... -- 2003/08/01 15:57 GMT reply
Nope, didn't do the trick. Any other suggestion?

-roy

IssueTracker inside Plone Site problem? -- Mon, 25 Aug 2003 21:57:57 +0000 reply
I'm having a problem with IssueTracker (zwiki 0.20.0rc3) where, after following the directions in AdminHowtos and adding a IssueTracker page whose content was grabbed from ZWiki/content/tracker/IssueTracker.stxdtml, when I attempt to go to /Wiki/IssueTracker, which is inside a Plone site I get:

Site Error An error was encountered while publishing this resource.

CatalogError?

Sorry, a site error occurred.

Traceback: (snipped)

IssueTracker inside Plone Site problem? --simon, Mon, 25 Aug 2003 23:51:52 +0000 reply
Yes, we have an open issue on this.. the default plone catalog lacks certain indexes and metadata that IssueTracker relies on. Here it's complaining about a missing index.

IssueTracker inside Plone Site problem? --simon, Mon, 25 Aug 2003 23:54:08 +0000 reply
PS you can try to figure out what it needs and add them by hand in the ZMI. This will be automated when possible.

setupTracker feedback -- Sun, 21 Sep 2003 21:11:19 -0700 reply
I just got a 0.23CVS and setup via SOMEPAGEURL/setupTracker (Zope 2.7b1). Seems OK except that the catalog was empty after I created it. Because of this, FuzzyUrlMatching? didn't work until the catalog was populated also. - DeanG

setupTracker feedback --Simon Michael, Tue, 23 Sep 2003 00:11:30 -0700 reply
Thanks for testing Dean - good point, we should make it do a catalog find as the last step.

Problem with issue_colours -- Thu, 06 Nov 2003 15:39:45 -0800 reply
If you include issueColour as a metadata entry on your zwiki Catalog (as suggested in this page and on ZwikiAndZCatalog) the mechanism for overriding the issue colours doesn't work. You're supposed to be able to establish your own issue color scheme via a issue_colours lines property on your zwiki folder. This didn't work for me unless I removed the issueColour metadata from the catalog. I think it has to do with namespace - i.e. DTML references to issueColour would hit the object property established by the Catalog first, instead of bottoming out in the Tracker.Py function as intended.

Problem with issue_colours -- Thu, 06 Nov 2003 15:49:21 -0800 reply
Also - on the whole I'm disappointed with Zwiki's chronic use of explicit style formatting. I've had to touch far too many files in an effort to apply consistent CSS usage while customizing my Zwiki. This relates to the issue_colours problem because even now that I fixed it, it's an ungainly mechanism. I should not be putting raw color codes into my top-level zwiki folder properties. That's just wrong. That's what the stylesheet is for. Now that I've got it working, I plan on adapting it to use class markers instead of bgcolor.

Problem with issue_colours --simon, Sun, 30 Nov 2003 13:33:16 -0800 reply
That's a good idea (styles for issue colours).

Error on "Add issue" -- Sat, 20 Dec 2003 08:59:31 -0800 reply
This wiki's issuetracker template gave an error. Traceback (most recent call last):

  File "/usr/local/zope/instance/Products/ZWiki/UI.py", line 538, in issuetracker
    body = default_issuetrackerdtml.__of__(self)(self,REQUEST)
  File "/usr/local/zope/2.6.1/lib/python/App/special_dtml.py", line 61, in __call__
    (self,)+args[1:],kw)
  File "/usr/local/zope/2.6.1/lib/python/DocumentTemplate/DT_String.py", line 474, in __call__
    try: result = render_blocks(self._v_blocks, md)
  File "/usr/local/zope/2.6.1/lib/python/DocumentTemplate/DT_Let.py", line 76, in render
    return render_blocks(self.section, md)
  File "/usr/local/zope/2.6.1/lib/python/DocumentTemplate/DT_Util.py", line 201, in eval
    return eval(code, d)
  File "", line 0, in ?
  File "/usr/local/zope/instance/Products/ZWiki/Tracker.py", line 215, in createIssue
    self.create(pageid,text=text,REQUEST=REQUEST)
  File "/usr/local/zope/instance/Products/ZWiki/Editing.py", line 58, in create
    raise 'Unauthorized', (
 Unauthorized: You are not authorized to add ZWiki Pages here.

-Trevor

Error on "Add issue" --SimonMichael, Tue, 23 Dec 2003 01:28:36 -0800 reply
Give yourself Zwiki: add pages permission.

ZWikiTracker? 0-26-0 Setup problem -- Mon, 05 Jan 2004 13:41:01 -0800 reply
Hi, I'm a Zwikki Newbie and I've just installed ZWiki 0-26-0 y URL "http://pepito.usb.ve:8080/zwiki/"(really the loopback interface). I try to run "http://pepito.usb.ve:8080/zwiki/setupTracker" and it created a Zwiki page with id="setupTracker".... What's the problem?

ZWikiTracker? 0-26-0 Setup problem --Simon Michael, Tue, 06 Jan 2004 02:58:54 -0800 reply
It should be http://pepito.usb.ve:8080/zwiki/FrontPage/setupTracker

IssueNo? RemoteWikiLink? shortcut --DeanGoodmanson, Sun, 01 Feb 2004 17:14:45 -0800 reply
Quick test to see how this works...

IssueNo:0001

IssueNo? RemoteWikiLink? shortcut --DeanG, Mon, 02 Feb 2004 07:06:10 -0800 reply
Of course! RemoteWikiLinks work on Plain Text pages. I didn't expect that. The IssueNo? page worked as I hoped, but getting parameter parsing in the page doesn't work as I can't save it in DTML mode.

Use of prefix "Issue" for page names --Alan Cowderoy, Tue, 23 Mar 2004 05:41:15 -0800 reply
This discussion has been refactored as #761 different prefix for issue page names.

IssueNo? RemoteWikiLink? shortcut --SimonMichael, Mon, 24 May 2004 03:36:20 -0700 reply
IssueNo? is no longer considered an issue.

issue pages begin with numbers ? --SimonMichael, Mon, 24 May 2004 03:37:19 -0700 reply
What do you think of the example at the end of #761 different prefix for issue page names ?