That's a new one. Make sure you have:
[components]
tractags.* = enabled
in your trac.ini, and that you *do not* have default_handler =
TagsWikiModule anywhere.
Also, ensure that you've completely removed any old versions of tags.
FYI this same combination of Trac 0.11 and Tags works for me. I
I get prompted for upgrades. It seems like I am running into a
situation similar to the one described at
https://hosted.fedoraproject.org/projects/setroubleshoot/changeset/725:dfdd01f207f4
when running trac-admin /path/to/myproject upgrade
On Aug 24, 6:31 am, Alec Thomas [EMAIL PROTECTED] wrote:
On 8/15/07, cobwebsmasher [EMAIL PROTECTED] wrote:
Alec, I'm eager to try out your port. I have 3 questions before I try
1) - the default_handler requirement being removed - are you saying that the
default_handler line shouldn't exist at all even if it is set to an actual
default value?
Excellent, thanks Gary :)
On 8/15/07, Gary Oberbrunner [EMAIL PROTECTED] wrote:
Alec Thomas wrote:
Hello,
I've made a start at porting Tags to 0.11. It's pretty much feature
equivalent to the 0.10 version as it stands.
To try it out:
easy_install
I forgot to mention that you must no longer set the default_handler.
That is, you MUST NOT have this in your trac.ini:
[trac]
default_handler = TagsWikiModule
Remove this line completely if it exists.
On 8/15/07, Alec Thomas [EMAIL PROTECTED] wrote:
Hello,
I've made a start at porting Tags
this port affects the Blog
plugin?
Thanks,
Vincent
- Original Message
From: Alec Thomas [EMAIL PROTECTED]
To: trac-users@googlegroups.com
Sent: Tuesday, August 14, 2007 9:45:57 AM
Subject: [Trac] Re: Preliminary port of Tags to 0.11
I forgot to mention that you must no longer set
Alec Thomas wrote:
Hello,
I've made a start at porting Tags to 0.11. It's pretty much feature
equivalent to the 0.10 version as it stands.
To try it out:
easy_install http://trac-hacks.org/svn/tagsplugin/trunk/
It requires Genshi trunk, so it'll probably pull that down as well.
cobwebsmasher wrote:
3) - Also curious as to whether or not you know how this port affects
the Blog plugin?
Can't answer the first two, but I think I can speak authoritatively to
the third.
The port will now allow the blog plugin to be ported to 0.11. The port
shouldn't be very hard,
