#10612 closed defect (duplicate)
WikiLinks using square brackets fails in certain cases
| Reported by: | Owned by: | Steffen Hoffmann | |
|---|---|---|---|
| Priority: | normal | Component: | TagsPlugin |
| Severity: | normal | Keywords: | wikilinks |
| Cc: | Trac Release: | 0.12 |
Description
When using the tags plugin and entering a reference to a tag using square brackets, in some cases this fails. Currently if you enter the following syntax:
[tag:tagname]
The tag will fail to render correctly. However the following syntax works:
[tag:tagname ] or [tag:tagname tagname]
~/ross
Attachments (1)
Change History (8)
comment:1 Changed 13 years ago by
Changed 13 years ago by
| Attachment: | t10612-r12165-1.patch added |
|---|
comment:2 Changed 13 years ago by
This ticket interested me because I've previously ([11689]) tried to make use of trac.wiki.tests.formatter in order to setup tests for the wiki formatter (and would also like to utilize the module when making tests for PlantUmlMacro). This patch gets closer to that, however I'm still running into an issue in which I can't activate a component in the environment. The only way I can get tractags enabled is to recreate the environment (note: formatter_setup gets called after the environment is created in the trac.wiki.tests.formatter.WikiTestCase constructor).
The patch also resolves the issue reported in this ticket, and cleans up the regex.
comment:3 follow-up: 4 Changed 12 years ago by
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Ryan, thanks for providing the patch.
I'll follow it loosely, but especially won't rely on the import from trac.wiki.tests. Rather easy to provide a minimal formatter.py in this plugin for not requiring a full Trac developer setup to run these unit tests.
But the issue is essentially a duplicate of #9630. Please follow-up overthere as required.
comment:4 follow-up: 5 Changed 12 years ago by
Replying to hasienda:
I'll follow it loosely, but especially won't rely on the import from
trac.wiki.tests. Rather easy to provide a minimalformatter.pyin this plugin for not requiring a full Trac developer setup to run these unit tests.
Is it possible to run the unit tests without a Trac developer setup anyway? The test harness in [13129] imports from trac.test, and I can't see how that would be available in any case that trac.wiki.tests is not.
comment:5 follow-up: 6 Changed 12 years ago by
Replying to rjollos:
Replying to hasienda:
I'll follow it loosely, but especially won't rely on the import from
trac.wiki.tests. Rather easy to provide a minimalformatter.pyin this plugin for not requiring a full Trac developer setup to run these unit tests.Is it possible to run the unit tests without a Trac developer setup anyway? The test harness in [13129] imports from
trac.test, and I can't see how that would be available in any case thattrac.wiki.testsis not.
While trac/test.py is packaged, all the trac/*/tests/ are not. So the answer is Yes, what I've seen in my test environments for a long time, because I did not install Trac from source/with deploy in there - just regular easy-install setups.



I can reproduce with r12165 (the latest) version of the trunk and Trac 0.12.3.