ticket	summary	component	version	milestone	type	severity	owner	status	created	_changetime	_description	_reporter
4431	wiki_to_wikidom	wiki system	0.10.3	topic-wikiengine	enhancement	critical		new	2006-12-20T10:09:23+01:00	2023-04-19T04:23:33+02:00	It would be good for plugins if parsing of wiki text will be broken to two stages. first take the text and convert to some data object tree (ala DOM, but with wiki orientation, so nodes are 'text', 'macro', 'link' etc.), then different formatters can go over the tree and format it, and plugins can search it.	ittayd@…
1386	Adding properties to Wiki Pages	wiki system	devel	next-major-releases	enhancement	major		new	2005-03-31T22:23:28+02:00	2021-12-30T03:07:32+01:00	"I think adding properties to Wiki pages would be a great feature.  Such as owner, cc, rss feeds, and specifcally, properites.

Some ideas for properties include

 * Publishing status - Published | Nonpublished[[br]]
 * Document Status - In Progress | Complete | Inconsistent | etc..

The idea for this is that I am in the process currently of adding content to the Wiki, however some items that I am documenting have not been completed either in terms of the documentation or having the items being documented having been completed.  I would like to be able to have an owner associated with the Wiki, perhaps a list of people who want to subscribe to change notifications for a particular wiki page, and a report for instance that the owner could view to see which pages they have that are in various states a defined by my definition of the various properties.

My definitions may need some refining but the idea still holds.  Anyway, I would be happy to discuss this further and possibly try to create some patches to demonstrate what I'm discussing if interested.
"	jon.brandenburg at theronyx.com
3021	wiki namespace support like the one in dokuwiki	wiki system	none	next-major-releases	enhancement	major		new	2006-04-11T17:47:04+02:00	2015-05-26T20:50:57+02:00	"It would be very great to have wiki namespace support, for sorting wiki pages and protect user to build too big pages. I think it's very important to support wiki namespaces. 
----
As the topic is broad, it's worth to discuss it in a specific proposal page, see TracDev/Proposals/WikiNamespaces."	trac.ticket@…
3386	Embedding part of Wiki in other Wiki (e.g. Help: prefix for the TracGuide)	wiki system	0.9.6	next-major-releases	enhancement	normal		new	2006-07-12T11:43:19+02:00	2015-05-26T20:50:57+02:00	"I'd like to be able to embed part of Wiki associated with some project in Wiki of other project, in order to reduce duplication of information and avoid using external links between wikis.

By `embed` i mean they do share (part of?) namespace, and links between them are internal to wiki. The embedded part should be accessible, linkable and editable from both Wikies, without using any special syntax nor, possibly, addresses.

Example:
lets say i have:
 * /projects/FlagshipProject, containing:
  * wiki/Globals/AboutDevelopers/*,
  * wiki/Globals/AboutCompany/*,
  * wiki/Globals/OtherStuff;
and 
 * /projects/OtherProject.
In Wiki of the later i'd like to embed /projects/FlagshipProject/wiki/Globals/*"	dexen^^^goofy.pl
7658	Option to disable automatic linking of CamelCase	wiki system	0.11-stable	next-major-releases	enhancement	normal		new	2008-09-22T13:32:30+02:00	2022-03-09T23:02:43+01:00	"It must have been brought up a million times by now. I can see that #476 almost addressed the problem for me, but didn't quite cut the mustard. Simply setting ignore_missing_pages isn't sufficient, as I'd like to see missing pages, but not automatic camelcase detection. Our naming convention uses camelcase and it's getting in the way. Trac is supposed to ""stay out of the way"" of developers. I'd just rather a wiki link was explicit.

I'd like to see either a global option in the ini file to switch this off completely, or a more configurable option, something like that suggested here: http://trac.edgewall.org/ticket/476#comment:23

The fix suggested in http://trac.edgewall.org/ticket/476#comment:26 would do just fine. If it breaks my wiki pages like the default Trac* wiki, that's my problem, and I'm quite prepared to deal with that. It's such a simple fix, I can't see why anyone would have any objections. I'll hack my installation for now, but I'd rather not.

Thanks,
Dave."	dave@…
8645	More readable header IDs	wiki system	0.11.4	next-major-releases	defect	normal		new	2009-09-07T20:19:51+02:00	2015-05-26T20:50:57+02:00	"The initial report was about invalid header IDs; they're actually not invalid in XHTML 1.0, but their readability can nevertheless be greatly improved. Re-targeting the ticket that way, see comment:5 for details.


=== Original Report

Headers IDs generated from headers with non-ASCII characters keep/have them what is invalid:

  An ID attribute does not conform with the HTML document type specification. ID tokens must begin with a letter, and may contain only letters, digits, hyphens, underscores, colons, and periods.

We could do something like [http://search.cpan.org/~sburke/Text-Unidecode-0.04/lib/Text/Unidecode.pm Text::Unidecode]."	Mitar
9037	Incorporate footnotes into Trac (for use in documentation)	wiki system	0.12dev	next-major-releases	enhancement	normal		new	2010-02-06T07:34:27+01:00	2023-06-11T16:46:44+02:00	"As I have tried to contribute a little bit to the documentation, it has occurred to me that it would be really nice for the sake of page layout and clarity to have footnotes available for use in the documentation.

I have used the th:FootNoteMacro for quite some time and there does not seem to be any issues with it. There are currently not even any open tickets filed against the macro.

Would it be possible to incorporate this macro into the next Trac distribution if we were to refactor the code to fit the style guidelines for Trac, write some unit tests, or whatever else might be necessary?

Or is the preferred way to go about this through a direct incorporation into the wiki markup language, like I see is available with Restructured Text (as shown on WikiProcessors - see Example 2)?

I [/search?q=footnote searched] around but did not find any similar suggestions."	Ryan J Ollos
9574	add filters to TicketQuery from query string arguments	wiki system	0.13dev	next-major-releases	enhancement	normal		new	2010-08-18T21:54:08+02:00	2011-10-25T15:03:19+02:00	"I'm using wiki pages and the TicketQuery macro to create ticket summary/overview pages, as I find them much more flexible than reports as I can have multiple 'views' on the same page (for example, have 'Assigned to you', 'Awaiting assignment', 'In progress', etc - each shows top 10, has different filters and ordered by different columns, all in the same page. Creating a page like that isn't possible with reports).

So - what I'm trying to do is create a per-project ('project' being a custom field I added) and per-components ticket overview using the Wiki. Instead of copying the wiki page for every project/component I have, I want to use something like `wiki/TicketSummary?project=foobar` and than read the query-string argument (`project`) to be used inside the TicketQuery macro and `[query:]`.

I was trying to do it using IWikiSyntaxProvider and get_wiki_syntax (http://pastie.org/private/evw1r9jkhcmq3m6jjgrojw), by replacing ${foobar} with `req.args['foobar']`, which works - but not inside other macros.

I think the best way is adding this functionality to core, by parsing custom arguments inside the TicketQuery macro and `[source:]` link, in a similar way to how $USER is replaced with the currently logged in user - but replacing them with query-string arguments instead.

This will give users better control and flexibility in creating their own custom ticket overviews, which can replace the reports in some cases if those pages could be dynamic and show different content based on arguments."	shesek
4790	a blockquote after a list gets nested into two <blockquote> tags	wiki system		topic-wikiengine	defect	normal		new	2007-02-19T22:19:48+01:00	2021-09-02T20:09:32+02:00	"This text:
{{{
a list:
 * item 1
 * item 2

  a blockquote after a list
}}}

turns into:
{{{
#!xml
<p>
a list:
</p>
<ul><li>item 1
</li><li>item 2
</li></ul><blockquote>
<blockquote>
<p>
a blockquote after a list
</p>
</blockquote>
</blockquote>
}}}

Same thing happens for a blockquote following a blockquote following a list:
{{{
a list:
 * item 1
 * item 2

  a blockquote after a list

  a blockquote after a blockquote after a list
}}}

turns into:
{{{
#!xml
<p>

a list:
</p>
<ul><li>item 1
</li><li>item 2
</li></ul><blockquote>
<blockquote>
<p>
a blockquote after a list
</p>
</blockquote>
</blockquote>
<blockquote>
<blockquote>
<p>
a blockquote after a blockquote after a list
</p>
</blockquote>
</blockquote>
}}}"	Gary Wilson <gary.wilson@…>
8140	nested lists with multiple paragraphs should work properly	wiki system	0.12dev	topic-wikiengine	enhancement	normal		new	2009-03-18T18:56:50+01:00	2020-05-10T11:32:37+02:00	"When you need to nest list with multiple paragraphs, the markup rendered is not what is expected.  With the source input

{{{
 * lists can be used to denote all sorts of things
   
   '''Examples:'''
    - listing tickets
    - listing other things that need doing
    - laundry lists

 * this is another list item

 * and so is this
}}}

the markup rendered is

{{{
<ul><li>lists can be used to denote all sorts of things
</li></ul><p>
   
</p>
<blockquote>
<blockquote>

<p>
<strong>Examples:</strong>
</p>
</blockquote>
</blockquote>
<ul><li>listing tickets
</li><li>listing other things that need doing
</li><li>laundry lists
</li></ul><ul><li>this is another list item
</li></ul><ul><li>and so is this
</li></ul>
}}}

The markup desired is more like:
{{{
<ul><li>lists can be used to denote all sorts of things

<p>
<strong>Examples:</strong>
</p>

<ul><li>listing tickets
</li><li>listing other things that need doing
</li><li>laundry lists
</li></ul></ul>
<ul><li>this is another list item
</li></ul><ul><li>and so is this
</li></ul>
}}}

This can be worked around with the `[[BR]]` tag:

{{{
* lists can be used to denote all sorts of things[[BR]]'''Examples:'''
    - listing tickets
    - listing other things that need doing
    - laundry lists

 * this is another list item

 * and so is this
}}}

But this is non-semantic"	jhammel@…
9879	wiki_to_text()	wiki system	0.12-stable	unscheduled	enhancement	major		new	2010-11-26T15:59:24+01:00	2021-09-01T01:37:05+02:00	"Currently it's not possible to render wiki content to plain text without some hacks like normalizing the html output.

Related tickets: #1502, #8165"	Thijs Triemstra
8499	Cannot obtain link to paragraph/section when reST used	wiki system	0.11-stable	unscheduled	enhancement	minor		new	2009-07-22T09:51:35+02:00	2015-05-26T20:55:39+02:00	"{{{
#!rst

Hello. When writing wiki content with reST i noticed strange differences between HTML output which prevents from linking to specific paragraph. For heading ""Jakis tytul"" I get:

With reST:
 <h1><a id=""jakis-tytul"" name=""jakis-tytul"">Jakis tytul</a></h1>

With Wiki markup:
 <h1 id=""Jakistytul"">Jakis tytul</h1>

I don't know exactly how your JS works to find headings and add a icon next to them when mouse hovered to allow obtaing a link to paragraph, but it definitely fails here.
I attach two pictures, on with ""O.o"" heading from reST hovered, one with ""Jakis tytul"" written with Wiki markup. Notice status bar address.


My setup:
 * Trac:	0.11
 * Python:	2.6.2 (r262, Jun 15 2009, 00:07:25) [GCC 4.1.1 (Gentoo 4.1.1-r3)]
 * setuptools:	0.6c9
 * psycopg2:	2.0.11
 * Genshi:	0.5.1
 * Pygments:	1.0
 * GIT:	        1.6.0.6
 * jQuery:	1.2.3
}}}"	vic@…
13012	Allow direct docutils configuration	wiki system		1.7.1	enhancement	normal		new	2018-04-20T01:15:22+02:00	2021-05-28T21:28:12+02:00	"Add an option for the path to a docutils configuration file. This isn't strictly needed because there are [http://docutils.sourceforge.net/docs/user/config.html#configuration-files other ways to specify a configuration], but it might be a convenience.

Discussed in gmessage:trac-users:bxWbIZwZbh0/VHnIdD-4AAAJ."	Ryan J Ollos
9222	"""full delete"" of wiki page could be a non-fatal operation"	wiki system		next-dev-1.7.x	enhancement	normal		new	2010-04-12T17:09:32+02:00	2020-12-29T09:45:39+01:00	"When I delete a file from SVN, it stays there in previous versions. Would be nice to have the same possibility in Trac (maybe configured from trac.ini):

When I delete a page from Wiki, it goes off and I don't see it in Index and I '''can't''' reach it from web. But I can reach its previous versions! I just deleted the page in version 5. When I go to this page from web - Trac says that the page is absent and asks me whether I want to create it. But when I go to this page with `@5` suffix, I get directly to the deleted page, its latest version.

Such a behavior looks more effective/consistent for me, than ""full delete"", as it is now."	team@…
12567	Image macro should support protocol-relative URLs	wiki system		next-dev-1.7.x	enhancement	normal		new	2016-08-25T00:18:48+02:00	2020-12-29T09:45:39+01:00	"For example, `//www.edgewall.org/gfx/trac_bullet.png` could be used on WikiStart.

URLs starting with `//` should be interpreted as protocol-relative. Unfortunately, the Image macro interprets URLs starting with `//` as //server-relative//. If we were starting again, I might suggest we use something like `^//` for server-relative.

The only idea I have is to use `://` to indicate protocol-relative URLs. Other ideas are welcome."	Ryan J Ollos
12928	Pass author to wiki_page_deleted and wiki_page_version_deleted	wiki system		next-dev-1.7.x	defect	normal		new	2017-10-11T19:19:45+02:00	2020-12-29T09:45:39+01:00	"See [https://github.com/trac-hacks/trac-wikinotification/issues/11 trac-wikinotification issue #11].

One possibility would be to modify the `page` object before passing to the change listener:
* Set the `author` to the user deleting the page
* Set the `content` to an empty string
* Set the `version` to `None`?

Similar changes made be wanted elsewhere, such as the `Ticket` model."	Ryan J Ollos
1242	[ER] Generalized automatic cross-references in Trac	wiki system	0.8	next-major-releases	enhancement	critical		new	2005-03-03T11:13:58+01:00	2022-11-16T06:31:00+01:00	"== Problem == 

Trac provides a fast, easy and flexible way to relate Trac objects together, 
by the use of TracLinks in the WikiFormatting.

However, there's no automatic support for back-linking.
This lack has been noticed in several circumstances:
 * BackLinks for Wiki pages (tickets #611 and #646,
   the latter containing a [http:/trac/ticket/646#change_4 note]
   which also highlights the genericity of the problem)
 * Related Changesets for a given Ticket (ticket #508)
 * Ticket dependencies and other relationships (tickets #31 and #226)

Instead, the backlinking is done manually. For example, when
closing a ticket with a resolution of {{{duplicate}}}, 
the convention is to comment the closing of the ticket
by saying ''this is a duplicate of #xyz'' 
and to mention the existence of the duplicate ticket 
on the original #xyz ticket.
With a generalized backlinking facility, this would cease to be necessary.

== Solution ==

What I would propose is that every relationship that
gets detected while parsing new wiki content is recorded.
Then, each wiki, changeset and ticket page could contain
a '''See also:''' section at the end, listing the other
objects that contain TracLinks targeting it, along with
a bit of context, to catch the semantic of the link as well.

----
Example given:

Consider the following wiki !OutstandingPatches page:
{{{
= Outstanding Patches page = 

I think that the patches #187, #909, #919, #944 and #948 are great!
}}}

Then, each time this page is edited, the content of an 
{{{XREF (source, target, context}}} 
table would be cleared for this page:
{{{
delete from XREF where source = 'wiki:OutstandingPatches'
}}}

and when the content is processed, each time a TracLink is 
detected, the table would be filled:
{{{
insert into XREF values ('wiki:OutstandingPatches',
                         'ticket:187',
                         'I think that the patches #187, #909, #919, #944 and #948 are great!')
}}}

Then, while browsing !#187, one could easily get the
backlinks:
{{{
select source, context from XREF where target='ticket:187'
}}}

in order to create the following output at the end of the ticket page:

{{{
#!html
<div>
<strong>Backlinks:</strong>
<a href=""/trac/wiki/OutstandingPatches"" title=""I think that the patches #187, #909, #919, #944 and #948 are great!"">OutstandingPatches</a>
</div>
}}}

----

Of course, I'm willing to provide a patch for that, but I would like 
to get some feedback before.

-- Christian"	Christian Boos
611	Backlinks	wiki system	0.7.1	next-major-releases	enhancement	major		new	2004-07-11T14:52:44+02:00	2021-04-07T13:43:14+02:00	"A nice feature would be automatic backlink generation for wikipages.

if there is intrest in this sugested enhancement i would like to contribute in coding this feature (wih a little guidance)

keep up the good work!"	siegfried@…
695	Keywords for wiki pages	wiki system	0.7.1	next-major-releases	enhancement	major		new	2004-08-11T16:49:42+02:00	2021-11-26T13:29:21+01:00	"It would be nice to see a keywords field for wiki pages, same as the one for tickets. This list of manually chosen keywords can serve multiple purposes:

 * for searching and ranking, grouping, ...

 * to automatically generate the ""See also"" list of links at the bottom of a page, listing all other pages that share 1 or more of the keywords. Currently this seems to be done manually, so if a wiki page changes such that it should not be related anymore, then one would have to hunt down and change all other pages that ""See also"" to it. "	mario at ruggier.org
2656	Make built-in documentation independent from wiki	wiki system	0.9.3	next-major-releases	enhancement	major		new	2006-01-24T11:13:55+01:00	2019-09-16T01:54:34+02:00	"I noticed that there are various links to the built-in documentation pages in the wiki.  We use the wiki for internal documentation and development matters and therefore anonymous users don't have rights to access it.
So it would be nice if the online documentation pages would be independant from the wiki, because anonymous users can't view them if they have no right to access the wiki and it is annoying if you have those links to is everywhere, which lead you (as an anonymous user) to pages which say ""Access denied"".
A quick workaround would be to only display the links if you have rights to access the wiki.

Best regards

Florian Lahr"	flo@…
2702	markdown support	wiki system	0.9.3	next-major-releases	enhancement	major		new	2006-01-31T19:55:45+01:00	2017-04-04T01:55:59+02:00	It'd be nice to see support for [http://daringfireball.net/projects/markdown/ Markdown] with [http://daringfireball.net/projects/smartypants/ SmartyPants] support. Both are available as PHP libraries, so it shouldn't be difficult to include.	anonymous
3251	A documentation about components should be added	wiki system	0.9.6	next-major-releases	enhancement	minor		new	2006-06-11T21:31:37+02:00	2015-05-26T20:50:57+02:00	I'm trying to update the list of components for my ticket system, but I've been unable to find any way in either the gui or configuration that will allow me to do this.	dcarter@…
8961	[PATCH] Linkable lines on diff view	wiki system	0.12dev	next-major-releases	enhancement	minor		new	2010-01-12T14:44:39+01:00	2015-12-19T16:38:37+01:00	Lines are not linkable in diff view. This patch modifies diff_div.html so that lines are linkable.	niko.sten@…
9526	Fine Grained Permission possible realms and paths format are not documented.	wiki system	0.12	next-major-releases	defect	minor		new	2010-07-27T10:09:14+02:00	2019-09-06T19:51:32+02:00	"I'm trying to configure authz_policy.py (TracFineGrainedPermissions) for things other than Wiki Pages.

I can see that this is possible and working, but I'm waisting my time discovering ""paths and realms"" for every single thing I want to manage via authz_policy.

All the samples and documentation I've found describe configuration for wiki: realms *only* and while this is probably most common usage I'd like to create a ticket to expand the documentation in this topic."	dpc@…
10032	Wiki page mouse hover tooltip	wiki system	0.11.7	next-major-releases	enhancement	minor		new	2011-02-17T12:58:02+01:00	2011-02-17T15:28:28+01:00	When I am currently in a comment (or even on the timeline), the WikiPages and CamelCase words are highlighted in red. But they do not show tooltips when the mouse hovers over them. It is really nice when the mouse hovers over ticket numbers like #1 it will show the summary of the ticket. This would be nice if it works with WikiPages and CamelCase words as well.	francoishill11@…
10167	"Column ""Date"" in Change History of a Wiki Page"	wiki system	0.12.2	next-major-releases	enhancement	minor		new	2011-05-05T18:35:29+02:00	2011-05-05T22:47:42+02:00	"This column should by labelled ""Age"" (and the css class should be ""age""), since it actually shows the age of the changes (... days '''ago'''), not the date."	wilfred.berger@…
10350	e.g. [#1234] in svn commit 5678 comment generates wrong Trac link	wiki system	0.12.2	next-major-releases	enhancement	minor		new	2011-09-09T12:08:04+02:00	2020-07-14T19:19:11+02:00	"The effect is that the Trac generated link will be http://......./changeset/5678#1234 which on clicking does not lead to the ticket 1234. The link should rather be http://....../ticket/1234.

IMHO the link generator should ignore the brackets if it sees the #.

The whole problem is because some people are used to brackets instead of parenthesis when they write additional comments in their texts. Actually, they should write {{{ (#1234) }}}, but I think you should also be able to stand the one with brackets."	fbrettschneider@…
11163	Option to set HTML title.	wiki system	0.12.2	next-major-releases	enhancement	minor		new	2013-04-16T05:01:26+02:00	2015-11-30T22:30:50+01:00	"Currently no option to set HTML title. At preset, title seems to be the same as the page name. The problem with this is the title can end up like ""section/subsection/subsubsection/mypage"" which isn't very handy.

I've tried using the html processor, as follows; 
!{{{
#!html
<head><title>Test Title</title></head>
}}}
but no luck there either."	anonymous
425	Wiki page name need to support digits and periods	wiki system	0.8	next-major-releases	enhancement	normal		new	2004-05-19T15:00:40+02:00	2015-03-02T22:31:46+01:00	"Restricting Wiki page names to only alphabetic chars makes
it very have to create pages that discuss MilestoneV1.0 etc

Is there any problem with allowing digits and period?
"	barry.scott@…
1513	Multi-language support in the wiki	wiki system		next-major-releases	enhancement	normal		new	2005-05-06T16:14:51+02:00	2015-05-26T20:50:57+02:00	Let trac be the first-ever multi-lingual wiki on the market!  Have the ability to translate wiki articles into different languages.  A user can select their language when they view the wiki.  We have looked around and there isnt a wiki out there that handles this.  And if you dont have time to do it, do you mind having some volunteers help you out? :)	Paul Baranowski <paul@…>
1520	Highlight TracLinks in browser	wiki system	0.8.1	next-major-releases	enhancement	normal		new	2005-05-08T11:45:46+02:00	2015-05-26T20:50:57+02:00	"It would be nice to highlight TracLinks in browser file view.

For example to display ticket links when viewing source:trunk/ChangeLog@latest. 
 //This is already possible by specifying text/x-trac-wiki as the mimetype for this kind of files//

Another example would be to wiki format the inline Wiki syntax present in comments (this needs some cooperation from the syntax highlighter, e.g. the Pygments renderer)."	shad
4022	Provide Etag and/or Last-Modified HTTP headers to ease cache control	wiki system	0.10	next-major-releases	defect	normal		new	2006-10-24T21:32:30+02:00	2015-05-26T20:50:57+02:00	"Trac serves pages without any Etag or Last-Modified header, which makes cache management rather troublesome, and increases the server load. This is particularly important for RSS feeds, which might be checked relatively often.

(In one of the comments for #663 it was mentioned that conditional GET was planned for 0.9, but one of Trac setups I'm checking on is based on 0.10 and the functionality seems to be missing.)

I think most pages could be served with a Last-Modified header containing the date of the last change (for wiki and ticket pages) or the date of the most recent thing changed (for RSS feeds).
"	Giuseppe Bilotta <giuseppe.bilotta@…>
4412	batch copy/rename wiki pages	wiki system	0.10.3	next-major-releases	enhancement	normal		new	2006-12-17T11:22:09+01:00	2015-05-26T20:50:57+02:00	"==== Use cases
===== cross cutting wiki versions
If I have a product in version 1.x and I'm about to release 2.0, there are probably many changes to the wiki. However, I'd like to still retain a view of the 1.x wiki, for users of 1.x. Moreover, the 1.x wiki may continue to change with releases to the 1.x stream."	ittayd@…
4468	better support for relative name handling	wiki system	0.10.3	next-major-releases	defect	normal		new	2006-12-28T06:30:09+01:00	2019-11-12T03:50:48+01:00	"relative names should have support for:
 * getting page name from the relative name
 * getting page href (self.env.href.wiki) from relative name

this will allow something like:
{{{
[[Include(./RelativePage)]]
}}}"	ittayd@…
4778	simplified wikification of svn log messages	wiki system	devel	next-major-releases	enhancement	normal		new	2007-02-19T01:11:11+01:00	2015-05-26T20:50:57+02:00	"Is it possible to simplify the wikification of svn log messages? The problem I get is if we have 
some math content (like 
{{{
x^5+x^4+x
}}}
which will show like x^5+x^4+x. There are some other things as well, which we don't actually need in or project, as the log messages are and will always be plain text. The only thing I'd like to keep is the recognition of revision numbers in the log messages with the appropriate links.

Is it hard to achieve this? (Would be ok if it is in the source, i.e. not configurable by admin/user)

Thanks."	Sergei Haller <sergei@…>
7990	Can't view plain text wiki links	wiki system	0.11.2.1	next-major-releases	enhancement	normal		new	2009-01-20T21:27:14+01:00	2015-05-26T20:50:57+02:00	"You can no longer view the plain text version of a wiki page in your browser by selecting the plain text link - instead you are forced to download.

I understand the security concerns but, having read #7603, I expected to be able to enable the old behaviour by setting
{{{
[wiki]
render_unsafe_content = yes
}}}
However, this doesn't work. Is it meant to?

Admittedly the description of this option in TracIni#wiki-section doesn't say this will work. However, wouldn't it make sense to make this consistent with the same option from the `browser` and `attachment` sections?"	David Matthews
8526	SubWiki link & SubMapTxt page	wiki system	0.12dev	next-major-releases	enhancement	normal		new	2009-07-28T01:34:52+02:00	2010-06-24T18:25:49+02:00	"There are several nice features added to support SubWiki in Trac to categorize simliar wiki pages in hierarchical tree structure however linking to SubWiki from an arbitary Trac page can be really tedious if the level of depth become more than one.

If I have a SubWiki page Page/SubPage/SubSubPage/SubSubSubPage and it should be explicitly specified using full path to the SubWiki page.

{{{
[wiki:Page/SubPage/SubSubPage/SubSubSubPage]

or

[wiki:Page/SubPage/SubSubPage/SubSubSubPage ""This is SubSubSubPage""]

}}}

I can use InterWiki and InterMapTxt to create shortcuts to SubWiki pages under Page/SubPage/SubSubPage/.

{{{
Define an entry in InterMapTxt
===
SubSubPage http://localhost/trac/wiki/Page/SubPage/SubSubPage/$1 # Categorized under SubSubPage

}}}

and then use it as shown below

{{{
SubSubPage/SubSubSubPage

or

[SubSubPage/SubSubSubPage ""This is SubSubSubPage""]

}}}

It worked almost but a problem is that it does not create internal Trac database update (as it is treated as external link) which means Trac does not know the relationship between pages. i.e. [th:BackLinksMacro BackLinksMacro] can not display the back link to SubWiki page if InterWiki is used.

SubWiki macro support simliar to InterWiki using customizable SubMapTxt (like InterMapTxt) would be of great use for those who using SubWiki intensively to categorize simliar wiki pages.

This macro can possibly add /SubSubPage handler which can be utilzed in maintab or navtab to create direct access to categorized SubWiki pages list from Trac menu. (Simliar to [th:HierWikiPlugin#SubWiki HierWikiPlugin#SubWiki] mcaro)

I created a Requset-a-Hack ticket [th:#5569] in Trak-Hacks site as well."	Jae <zzzzoooo@…>
8640	Enable headline numbering	wiki system	0.11.5	next-major-releases	enhancement	normal		new	2009-09-06T10:52:36+02:00	2016-04-08T21:00:48+02:00	"For larger wiki pages with a lot sections it's often difficult to differentiate the sections ""level"" (i.e. h1 - h6). It would be helpful if headline numbering could be enabled, e.g.:

== 1. First <H2> headline ==
=== 1.1. First <H3> headline ===
=== 1.2. Second <H3> headline ===
== 2. Second <H2> headline ==
=== 2.1. First <H3> headline ===
==== 2.1.1. First <H4> headline ====
=== 2.2. Second<H3> headline ===
== 3. Third <H2> headline ==

This could be implemented as a user preference so that each user could decide whether he/she wants headline numbering or not. Also note that <h1> headlines (i.e. `=`) should not be numbered as they most likely only appear once on each page."	Sebastian Krysmanski <sebastian@…>
8735	wiki import should maintain page hierarchy	wiki system	none	next-major-releases	enhancement	normal		new	2009-10-12T17:46:55+02:00	2010-06-24T18:45:14+02:00	"When importing wiki pages via 
{{{
trac-admin ENV wiki import
}}}
it would be great if the directory structure in the import directory was maintained as the page hierarchy in the wiki. Alternatively, it could be useful if an import directory could be placed in some specific page in the wiki page hierarchy.
"	anonymous
8949	add sortable tables to wiki	wiki system		next-major-releases	enhancement	normal		new	2010-01-10T00:37:19+01:00	2015-03-01T03:54:53+01:00	"See

http://en.wikipedia.org/wiki/Help:Sorting

for Wikipedia's approach to sortable tables.

An approach that does not require JavaScript is preferred, even if it causes the page to reload, but any approach will do.

Useful trac-hacks related to this ticket may include:

http://trac-hacks.org/wiki/FlatTableMacro
http://trac-hacks.org/wiki/MultiSortReportPatch
http://trac-hacks.org/wiki/WikiTableMacro
http://trac-hacks.org/wiki/SqlQueryMacro

A work-around is also appreciated."	anonymous
9123	WikiFormatting in link text does not work	wiki system	0.12dev	next-major-releases	enhancement	normal		new	2010-03-09T10:42:09+01:00	2015-05-26T20:50:57+02:00	"Try to use a link which has a text that makes use of WikiFormatting. Like this [SandBox link to `SandBox`] or this [source:/ link to the ''root'' of the Trac sources]. I expect the link texts to be rendered in a way so that they contain “`SandBox`” and “''root''”, respectively, not “!`SandBox`” and “!''root!''”.

It is impossible to use markup consistently in, for example, a ticket comment when you also like to link to files, other tickets, revisions, etc., and you use monospace highlighting for file names, or have some other convention or personal preference for using markup.

I have successfully been able to reproduce this shortcoming in the sandbox in the [/demo-0.11/wiki/SandBox 0.11] and [/demo-0.12/wiki/SandBox 0.12] demo installations."	n-roeser@…
9214	expandable blockquotes	wiki system		next-major-releases	enhancement	normal		new	2010-04-10T12:19:49+02:00	2015-05-26T20:50:57+02:00	"Would be nice to have an ability to configure blockquotes as ""expandable by jQuery"". Sometimes the content of blockquote is very large, say, 1000 lines, and a wiki page would look ugly with such a long text. Making a blockquote ""expandable"" would help, for example:

{{{
{{{+expandable
#!xml
...very long xml...
}} }
}}}

Maybe such feature exists already, but I didn't find it. Thanks."	team@…
9248	Trac as reST editor	wiki system	0.12dev	next-major-releases	enhancement	normal		new	2010-04-19T21:15:02+02:00	2011-02-25T15:52:39+01:00	"Trac markup is nice, but it is not suitable for documentation that should be distributed in various formats. For example, for Bitten reST is a better option as it could transformed by Sphinx into various stuff.

It could be nice if Trac could maintain documentation in specially designated wiki namespace as reST docs, so that these docs can be then synced back with version control system.

If it is possible to create a 1:1 symmetrical Trac to reST markup mapper (Genshi?), even partial - Trac could be used as online editor for Bitten docs, which will surely improve community participation."	anatoly techtonik <techtonik@…>
9537	to implement cherry-picking for wiki pages	wiki system		next-major-releases	enhancement	normal		new	2010-08-01T16:25:42+02:00	2015-05-26T20:50:57+02:00	"partially motivated by #1114

Would be nice to have an ability to pick any version from wiki revision history and ''copy'' it, making it the latest version. This way we don't need to delete anything (as mentioned in #1114). Instead, we keep full history intact, but just bring the version we need to the ""head""."	team@…
9554	plain text download of wiki pages reveals comments not meant for public consumption	wiki system	0.12dev	next-major-releases	enhancement	normal		new	2010-08-07T00:16:20+02:00	2015-05-26T20:50:57+02:00	"I find this one critical in that one might prototype content in the wiki that is not meant to be released to the public yet.

In order to reconstruct the scenario,

1. create a new wiki page
2. enter some content
3. enter
{{{

{{{
#!comment
TBD

Critical information that must not yet be leaked to the public.
}}}

}}}

4. download as plain text

in the downloaded plain text you can see also the comment with content that was not yet meant to be consumed by the public.
"	Carsten Klein <carsten.klein@…>
9947	Unexpected resolver result for TracLinks in wiki page within hierarchy	wiki system	0.12-stable	next-major-releases	defect	normal		new	2010-12-26T23:10:46+01:00	2014-03-14T00:55:54+01:00	"Current wiki parser seems unable to translate links like
{{{WikiPage}}}, {{{[../WikiPage]}}} or even {{{[wiki:WikiPage]}}}
to the expected target, a least if used to reference an equally named page from within a wiki subpage:

See [wiki:TranslationDe/TracWiki@1], where I tried to reference {{{[wiki:TracWiki]}}} by typing just TracWiki at the top of the page but got the equivalent of {{{[wiki:TranslationDe/TracWiki]}}} instead, what is plain wrong.

I tried all of the aforementioned syntax and came up with {{{[/wiki/TracWiki]}}} as valid workaround to get the expected «top-hierarchy page» for a fixed revision in [wiki:TranslationDe/TracWiki@2]."	Steffen Hoffmann
10201	[Patch] WikiProcessors lacks detailed help	wiki system	0.13dev	next-major-releases	enhancement	normal		new	2011-05-29T18:32:23+02:00	2015-12-19T16:52:05+01:00	"I've recently discovered the detailed help-feature of WikiMacros, which is activated by adding a question sign (`?`) after a macro name. Example:

{{{
[[TitleIndex?]]
}}}

This will show the detailed help, instead of the result. This is very handy during side-by-side edit to quickly find out the details of the macro.

This feature does **not** work for WikiProcessors, which would be a-nice-to-have feature, and natural since a processor really is a macro. Example:

{{{
{{{
!#TitleIndex?
}}}
}}}

This yields the normal output and not the help information as intuitively expected due to the behaviour of WikiMacros.

It would also be nice if all in-built processors (`div`, `span`, `table` etc) are capable of providing help information that could be brought up during side-by-side editing."	Mikael Relbe
10323	Enable sorting in TitleIndex macro	wiki system		next-major-releases	enhancement	normal		new	2011-08-19T10:05:15+02:00	2021-11-19T05:32:16+01:00	"The goal is to be allowed to order the result of the macro `TitleIndex` in the same way that `RepositoryIndex` with the addition of the parameters `order` and `desc`.
 * `Order` possible values: [title|date]
 * `Desc` possible values: [0|1], same repositoryindex.

For example:
{{{
[[TitleIndex(order=title, desc=1)]]
}}}"	carlos.lopezperez@…
10376	Opening a link in a new window?	wiki system		next-major-releases	enhancement	normal		new	2011-09-27T15:54:08+02:00	2016-12-19T15:54:19+01:00	What code is necessary for me to create a link that will open in a new window, as opposed to opening within the existing window? I am including a link on a new webpage on gsa.gov that will take the customer away from the GSA site and onto a non-government site. 	jennifer.johns@…
10633	TicketQuery 'clist' format	wiki system		next-major-releases	enhancement	normal		new	2012-03-19T19:11:52+01:00	2018-07-13T12:29:32+02:00	"I had a need for a short delimited list that was more than 'compact' and 'list'; but less than 'table'.  I am typically using this in a sidebar to get a current list of tickets with more useful information.  The coding may be horid, as i am not a python programmer most days; but it works and gives a very useful function if you want to add it.
{{{
Index: trac/ticket/query.py
===================================================================
--- trac/ticket/query.py	(revision 1322)
+++ trac/ticket/query.py	(working copy)
@@ -1332,6 +1332,24 @@
             else:
                 alist = [ticket_anchor(ticket) for ticket in tickets]
                 return tag.span(alist[0], *[(', ', a) for a in alist[1:]])
+
+	elif format == 'clist':
+            if query.group:
+                return tag.div(
+                    [(tag.p(tag_('%(groupvalue)s %(groupname)s tickets:',
+                                 groupvalue=tag.a(v, href=href, class_='query',
+                                                  title=title),
+                                 groupname=query.group)),
+                      tag.dl([(tag.dt(ticket_anchor(t)), 
+                               tag.dd(' - '.join(map((lambda x:t[x].__str__()),kwargs['col'].split('|'))) )) for t in g],
+                             class_='wiki compact'))
+                     for v, g, href, title in ticket_groups()])
+            else:
+                return tag.div(tag.dl([(tag.dt(ticket_anchor(ticket)), 
+                                        tag.dd(' - '.join(map((lambda x:ticket[x].__str__()),kwargs['col'].split('|'))) ))
+                                       for ticket in tickets],
+                                      class_='wiki compact'))
+
         else:
             if query.group:
                 return tag.div(
}}}"	branson@…
10670	Image macro references inconsistent with attachment links	wiki system	0.13dev	next-major-releases	enhancement	normal		new	2012-04-17T23:47:11+02:00	2015-03-02T22:27:22+01:00	"The format of the reference for [WikiMacros#Image-macro Image macro] is not aligned with that of `attachment:` links.

External reference to attachment is stated as ""`attachment:file:module:id`"". It would be nice if one could copy an attachment link to the Image macro by just ripping away ""`attachment:`""

Now, one has to swap parts of the attachment reference to suit the Image macro:

 `attachment:file:module:id` > `[[Image(module:id:file)]]`

This is annoying/confusing.

My view is that the Image macro is fault since both `attachment:` and `comment:` links use the same pattern. ''(Hard to accept, I imagine, since that would break existing image references to external resources.)''"	Mikael Relbe
11078	Perform fine-grained permission checks on resource in get_navigation_items	wiki system		next-major-releases	enhancement	normal		new	2013-02-23T18:00:27+01:00	2017-05-21T01:36:16+02:00	First mentioned in comment:1:ticket:11067, fine-grain permissions checks should be performed in `get_navigation_items`, taking into account the resource that may be specified in the `[mainnav]` section through the `href` option. See comment:4:ticket:11067 for additional suggestions.	Ryan J Ollos
11323	WikiProcessor argument to limit line width	wiki system		next-major-releases	enhancement	normal		new	2013-10-10T00:41:50+02:00	2014-03-09T18:36:07+01:00	"The th:EmailProcessorMacro can be used to limit the width of text in a `pre` block. It would be generally useful to add an argument to WikiProcessors for limiting the width of the text. The argument could be `wrap` or `cols` and should allow for a numeric argument for number of columns (`wrap=79` or `cols=79`).

Additionally, we might consider ""auto-wrapping"" columns based on the width of the screen."	Ryan J Ollos
11937	Improve suggestion of similarly named pages	wiki system		next-major-releases	enhancement	normal		new	2015-01-26T23:59:49+01:00	2019-09-06T19:51:32+02:00	"Trac suggests similarly named pages when navigating to a non-existent page with a CamelCase name, but the suggestion is naive. Trac will suggest CamelCase if CamelCas is entered, but not if CameCase is entered. The code that generates suggestions is [browser:/tags/trac-1.0.3/trac/wiki/web_ui.py@:636-638#L618 here]. The aim of this ticket will be to improve the suggestions.

The [browser:/tags/trac-1.0.3/trac/util/text.py@:703#L703 levenshtein_distance] function used by [browser:/tags/trac-1.0.3/trac/admin/api.py@:152#L140 AdminCommandManager] may be useful in implementing this ticket."	Ryan J Ollos
11963	#!td processor inserts unwanted <p>...</p>	wiki system	1.0.4	next-major-releases	defect	normal		new	2015-02-19T10:51:32+01:00	2021-05-18T02:37:47+02:00	"The table using the html processors has additional padding due to `<p>` elements that get inserted automatically.

{{{
{{{#!th
some
}}}
{{{#!td
example
}}}
}}}

{{{#!th
some
}}}
{{{#!td
example
}}}

In a long table, this vertical margin wastes too much space. I would prefer the compact style from the pipe syntax, but need to add css styling."	bastiK
12572	Add a download link to patch/diff renderer	wiki system		next-major-releases	enhancement	normal		new	2016-08-31T01:25:06+02:00	2019-09-06T19:51:32+02:00	It would be nice to be able to download a patch that is posted inline of a comment. For example: comment:1:ticket:12546. We could add a download link to the patch renderer. I'd use it to grab a URL that could be passed to wget.	Ryan J Ollos
12741	Make WikiProcessors foldable	wiki system		next-major-releases	enhancement	normal		new	2017-03-22T23:00:10+01:00	2019-09-06T19:51:32+02:00	"Discussed in #11550, extend WikiProcessors with features similar to:
* [th:FoldMacroProcessorMacro] (see th:#13184 for description of how the macro fails to do its whole job)
* [th:CollapsiblePlugin]"	Ryan J Ollos
12780	Save wiki expander state	wiki system		next-major-releases	enhancement	normal		new	2017-04-19T10:02:35+02:00	2019-09-06T19:51:32+02:00	"Replying to [comment:3:ticket:12640 Christian Boos]:
> As for the expander, ... the possibility to save as a UI preference the initial state of the wiki page, expanded or constrained.
"	anonymous
12828	"Add a ""wiki set"" trac-admin command"	wiki system		next-major-releases	enhancement	normal		new	2017-06-05T19:49:52+02:00	2018-03-03T00:48:34+01:00	"Similar to the `repository set` command,
{{{
repository set <repos> <key> <value>

    Set an attribute of a repository
}}}
it would be useful to have a `wiki set` command for setting the readonly attribute."	Ryan J Ollos
12900	Hierarchy-specific PageTemplates	wiki system		next-major-releases	enhancement	normal		new	2017-08-30T15:06:13+02:00	2019-09-06T19:51:32+02:00	"The PageTemplates feature uses:
> wiki pages having a name starting with ''!PageTemplates/''
as templates.

And the default selection:
> will be ''blank page'', or ''!DefaultPage'' if ''!PageTemplates/DefaultPage'' exists.

What's missing are templates that are only relevant to certain page hierarchy path prefixes, and a default template for those. For example when creating the page `wiki:Machines/NewMachine` the templates under `wiki:Machines/PageTemplates` should also be available. and `wiki:Machines/PageTemplates/DefaultPage` (or at least `wiki:PageTemplates/Machines/DefaultPage`) should be the default.
"	anonymous
11305	`#!table` with `|| cell ||` is rendered as a broken table	wiki system	0.12-stable	next-stable-1.6.x	defect	minor		new	2013-09-17T16:09:11+02:00	2023-09-23T22:33:10+02:00	"Trac renders the following wiki to a broken table. See demo-0.12:wiki:SandBox/NestedTable.

=== case 1
{{{
{{{#!table
{{{#!td
cell 1,1
}}}
{{{#!td
cell 1,2
}}}
|----
{{{#!td
|| nested || table || //cell 2,2// is lost ||
}}}
{{{#!td
cell 2,2
}}}
}}}
}}}

=== case 2
{{{
|| cell 1,1 ||\
{{{#!td
cell 1,2
  {{{#!table
  {{{#!td
  nested
  }}}
  {{{#!td
  table
  }}}
  }}}
}}}
|-------
{{{#!td
|| nested || table || **`</td>` is one too many here** ||
}}}
{{{#!td
cell 2,2
}}}
}}}"	Jun Omae
11720	Table with inline diff can misposition the wiki editor textarea	wiki system	1.0-stable	next-stable-1.6.x	defect	minor		new	2014-08-16T21:07:09+02:00	2023-09-23T22:33:10+02:00	"I've been unsuccessfully trying to edit the WikiProcessors page to append the content added in [wiki:WikiProcessors@62?action=diff] to the end of the table. I haven't been able to create a table with 3 rows. Along the way, I ran into an issue that can be reproduced with the following markup:
{{{
{{{#!tr
{{{#!td
Some examples:
 {{{
{{{
#!text/html
<h1>text</h1>
}}}
 }}}
}}}
{{{#!td
The result will be syntax highlighted HTML code:
 {{{
#!text/html
<h1>text</h1>
 }}}

The same is valid for all other [TracSyntaxColoring#SyntaxColoringSupport mime types supported].
}}}
}}}
{{{#!tr
{{{#!td
 {{{
{{{
#!diff
--- Version 55
+++ Version 56
@@ -115,8 +115,9 @@
     name='TracHelloWorld', version='1.0',
     packages=find_packages(exclude=['*.tests*']),
-    entry_points = """"""
-        [trac.plugins]
-        helloworld = myplugs.helloworld
-    """""",
+    entry_points = {
+        'trac.plugins': [
+            'helloworld = myplugs.helloworld',
+        ],
+    },
 )
}}}
 }}}
}}}
{{{#!td
'''`#!diff`''' has a particularly nice renderer:
{{{
#!diff
--- Version 55
+++ Version 56
@@ -115,8 +115,9 @@
     name='TracHelloWorld', version='1.0',
     packages=find_packages(exclude=['*.tests*']),
-    entry_points = """"""
-        [trac.plugins]
-        helloworld = myplugs.helloworld
-    """""",
+    entry_points = {
+        'trac.plugins': [
+            'helloworld = myplugs.helloworld',
+        ],
+    },
 )
}}}
}}}
}}}
}}}
Pressing **Preview Page** while in side-by-side edit mode results in the edit window being positioned in the preview area, inside one of the table cells.

[[Image(MispositionedEditor.png,100%)]]"	Ryan J Ollos
10539	intertrac links not working properly with diff	wiki system	0.11-stable	next-stable-1.6.x	defect	normal		new	2012-01-23T21:23:54+01:00	2023-09-23T22:33:10+02:00	"According to the InterTrac page you can use any flavour of TracLinks. However, not all forms of diff work. For example (using the examples from the TracLinks page):

Work fine:
 * trac:diff:@1:3
 * trac:diff:plugins/0.12/mercurial-plugin@9128:9953
Fail:
 * trac:diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default
 * trac:diff:trunk/trac@3538//sandbox/vc-refactoring@3539"	Dave Matthews
11374	Image macro doesn't display image containing a colon	wiki system		next-stable-1.6.x	defect	normal		new	2013-11-20T04:39:01+01:00	2023-09-23T22:33:10+02:00	"For example, see the attachment:

{{{
[[Image(2013-11-19_19:34:53.png​)]]
}}}

[[Image(2013-11-19_19:34:53.png​)]]"	Ryan J Ollos
11522	Unexpected block-quoted text	wiki system	1.0.1	next-stable-1.6.x	defect	normal		new	2014-03-07T00:10:53+01:00	2023-09-23T22:33:10+02:00	"th:comment:30:ticket:11553 demonstrates an issue with unexpected block-quoted text.

Apologies if this is a duplicate. I'm not very proficient in deciphering issues with the wiki markup."	Ryan J Ollos
11526	New style italics markup doesn't render correctly with CamelCase words	wiki system		next-stable-1.6.x	defect	normal		new	2014-03-09T11:15:56+01:00	2023-09-23T22:33:10+02:00	"The new-style italics markup `//` seem to have an issue:

{{{
 //WikiStart and CamelCase// [[BR]]
 ''WikiStart and CamelCase''
}}}
 //WikiStart and CamelCase// [[BR]]
 ''WikiStart and CamelCase''"	Ryan J Ollos
11536	Wrong label on wiki diff view between initial version and version 1	wiki system	0.12-stable	next-stable-1.6.x	defect	normal		new	2014-03-12T16:18:54+01:00	2023-09-23T22:33:10+02:00	" 1. Viewing wiki:WikiStart?action=diff&version=1&style=sidebyside, label in diff header is ""Version currently edited"".
[[Image(sidebyside-diff-en.png,width=300)]]

 2. Viewing wiki:WikiStart?action=diff&version=1&style=sidebyside with non-english locale, label in diff header is ""Version""
[[Image(sidebyside-diff-ja.png,width=300)]]

 3. Viewing wiki:WikiStart?action=diff&version=1&style=inline, both labels in diff header are ""v1"".
[[Image(inline-diff-en.png,width=300)]]
"	Jun Omae
11670	Wiki edit page should more clearly show when page doesn't exist	wiki system		next-stable-1.6.x	enhancement	normal		new	2014-07-10T09:35:29+02:00	2023-09-23T22:33:10+02:00	"Like the change that was made in #11663 for the Milestone Edit page, it would be more clear to use the green notification to indicate when the page does not exist.

Before:

[[Image(Before.png)]]

After:

[[Image(After.png)]]


{{{#!diff
diff --git a/trac/wiki/templates/wiki_view.html b/trac/wiki/templates/wiki_view.
index 4797b6a..f4be55a 100644
--- a/trac/wiki/templates/wiki_view.html
+++ b/trac/wiki/templates/wiki_view.html
@@ -74,7 +74,6 @@
           </div>
         </py:when>
         <py:otherwise>
-          <p i18n:msg=""name"">The page ${name_of(page.resource)} does not exist.
           <py:if test=""higher"">
             <p>You could also create the same page higher in the hierarchy:</p>
             <ul>
diff --git a/trac/wiki/web_ui.py b/trac/wiki/web_ui.py
index b524dba..a4d8dcb 100644
--- a/trac/wiki/web_ui.py
+++ b/trac/wiki/web_ui.py
@@ -602,6 +602,8 @@ class WikiModule(Component):
             if 'WIKI_CREATE' not in req.perm(page.resource):
                 raise ResourceNotFound(_('Page %(name)s not found',
                                          name=page.name))
+            add_notice(req, _(""The page %(name)s does not exist. You can""
+                              "" create it here."", name=page.name))
             formatter = OneLinerFormatter(self.env, context)
             if '/' in page.name:
                 parts = page.name.split('/')
}}}
"	Ryan J Ollos
11814	Wiki edit form area height preference is not saved without an explicit preview	wiki system		next-stable-1.6.x	defect	normal		new	2014-11-04T23:34:30+01:00	2023-09-23T22:33:10+02:00	"The `editrows` preference is only updated when rendering the editor. Therefore the value will only be updated in the `session_attributes` table when the user explicitly submits a //Preview//. The value won't be saved when submitting wiki edits.

This might be a bit confusing to the user because other preferences are saved immediately. For example, changing the //Edit side-by-side// preference will trigger a //Preview//, which will result in the editor being rendered again and the preference being saved."	Ryan J Ollos
12054	Normalize newline of wiki text to CRLF on initenv, saving wiki and fetching wiki	wiki system		next-stable-1.6.x	defect	normal		new	2015-05-01T05:40:24+02:00	2023-09-23T22:33:10+02:00	"Currently, Trac creates default pages with LF as newline on initenv. However, browsers send request with CRLFs for newline in textarea elements. Therefore, Trac creates a new version of the page even if the page is saved without changes.

{{{#!pycon
>>> v1 = WikiPage(env, 'WikiStart', 1)
>>> v2 = WikiPage(env, 'WikiStart', 2)
>>> v1.text[:40]
u""= Welcome to Trac 1.0.5 =\n\nTrac is a '''""
>>> v2.text[:40]
u""= Welcome to Trac 1.0.5 =\r\n\r\nTrac is a '""
>>> v1.text.replace('\n', '\r\n') == v2.text
True
}}}

I think we should normalize newlines in text of wiki page on initenv, saving wiki and fetching wiki."	Jun Omae
12214	Description lists are unescapable	wiki system		next-stable-1.6.x	defect	normal		new	2015-09-23T05:30:17+02:00	2023-09-23T22:33:10+02:00	"The following issue, reported in comment:7:ticket:2082, can be reproduced on 1.0-stable (r14332).

{{{
 {{{desc1::}}}:: blahblabla
}}}
 {{{desc1::}}}:: blahblabla

{{{
  `desc1::`:: blahblabla
}}}
  `desc1::`:: blahblabla"	Ryan J Ollos
12678	InterTrac link fails to link to a heading	wiki system		next-stable-1.6.x	defect	normal		new	2017-02-05T22:54:24+01:00	2023-09-23T22:33:10+02:00	I noticed while writing in [wiki:1.3/TracUpgrade], trac:TracFaq#Q:Attachmentsaremissingafterupgrade fails to link to the heading, whereas the full URL works fine https://trac.edgewall.org/wiki/TracFaq#Q:Attachmentsaremissingafterupgrade.	Ryan J Ollos
12733	Inconsistent linking for bold-formatted CamelCase words	wiki system		next-stable-1.6.x	defect	normal		new	2017-03-16T23:47:25+01:00	2023-09-23T22:33:10+02:00	Note in comment:3:ticket:11427, ExtensionOption, ExtensionOption: and **ExtensionOption** (`**ExtensionOption**`) are are rendered as links, but **ExtensionOption:** (`**ExtensionOption:**`) is not.	Ryan J Ollos
12756	Pseudo anchors should allow whitespace and special characters	wiki system		next-stable-1.6.x	defect	normal		new	2017-04-03T06:10:27+02:00	2023-09-23T22:33:10+02:00	"It doesn't seem to be possible to use whitespace or special characters in a [TracLinks#Linkanchors pseudo anchor] (#10284).

For example, I've wanted to have an anchor to `class Environment(Component)` in [browser:trunk/trac/env.py].
* [browser:trunk/trac/env.py#/Environment] anchors to an earlier instance of the `Environment` token
* None of the following work:
 * [browser:trunk/trac/env.py#/class%20Environment]
 * [browser:trunk/trac/env.py#/Environment(]
 * [browser:trunk/trac/env.py#/Environment%28]
 * [browser:trunk/trac/env.py#/'Environment(']
 * [browser:trunk/trac/env.py#/""Environment(""]"	Ryan J Ollos
2064	Timeline WikiFormatting mis-parses WikiLinks with aliases.	wiki system	devel	topic-wikiengine	defect	major		new	2005-09-14T18:38:11+02:00	2020-05-08T04:21:26+02:00	"In the timeline, the snippet of text that supports WikiFormatting will mis-parse a [wiki:TracLinks link] of the format: {{{[wiki:foobar foo]}}}.

If the literal text ""{{{[wiki:foobar foo]}}}"" is longer than the line permits, it will produce:

||Blah blah blah [wiki:foobar ...||

when it could easily fit

||Blah blah blah [wiki:foobar foo]||

into the line."	chandlerc@…
3895	Provide Trac API for returning all outbound links in a page	wiki system	0.10	topic-wikiengine	enhancement	major		new	2006-10-09T22:15:28+02:00	2015-05-26T20:59:21+02:00	"I have a suggestion that could kill a lot of birds with one stone.

I see a lot of people asking for functionality in Trac that relates to connections between pages (Backlink, Orphaned Pages, and MissingLinks among them).  I see some attempts by the community to provide that functionality.  I also see that those attempts are:

1) Very poor, and 
2) getting poorer by the day.

The reason they are getting poorer is that Trac already matches on a large array of patterns.  The bar is set fairly high, and the current plugins do not meet it.  Also, the Trac development team routinely introduces new additions/changes that increase the number of ways to connect two pages.  There is really no way for the plugin community to catch up.

Instead of asking us to do so, I ask you to help us help you:  Please provide (and document) an API function that takes some sort of reference to a Trac document (name perhaps) and returns a set of all outbound links from that page.  This functionality should identically match (or perhaps replace?) the functionality Trac uses to generate and HTML page.  As new patterns are added to the system, plugins would then automatically detect the new links.  With this function as a basis, a host of other functions could be provided, correctly, by the community.

If and when Trac tracks links between pages, the API could be modified to use the stored information, rather than calculating it on the fly.  


"	anonymous
4848	Unable to return to previous indentation within wiki	wiki system	0.10.3	topic-wikiengine	defect	major		new	2007-02-26T19:10:17+01:00	2015-05-26T20:59:21+02:00	"{{{
 0. Item 1[[BR]]
   Some text regarding Item 1
    * Item 1.a
    * Item 1.b
   Further text regarding Item 1
 0. Item 2
}}}

is rendered as:

 0. Item 1[[BR]]
   Some text regarding Item 1
    * Item 1.a
    * Item 1.b
   Further text regarding Item 1
 0. Item 2

i.e. with Trac 0.11.4stable-r7988
{{{
#!xml
<ol class=""arabiczero""><li>Item 1<br /> 
Some text regarding Item 1
<ul><li>Item 1.a
</li><li>Item 1.b
</li></ul></li><li>Further text regarding Item 1
</li></ol><ol class=""arabiczero""><li>Item 2
</li></ol>
}}}

""Further text regarding Item 1"" should be rendered at the same indent level as ""Some text regarding item 1"", and without becoming a new list item itself (or causing Item 2 to be rendered as the first item in a new list)."	charles@…
1240	Persistent   [[Timestamp]]	wiki system	0.8	topic-wikiengine	enhancement	minor		new	2005-03-03T01:14:15+01:00	2020-01-05T17:12:24+01:00	"If a wiki page is used to document a progress/process it may occur that multiple timestamps are used during successive edits. 

Doing so results in renewal of older timestamp. 

This ticket may be seen in context with ticket #955"	chrisb .not at. ewetel .dot. net
3794	Invalid table(with indentation) layout in wiki.	wiki system	devel	topic-wikiengine	defect	minor		new	2006-09-27T07:17:14+02:00	2015-05-26T20:59:21+02:00	"The following wiki markup:
{{{
 * this is a table example.
   || This row has a '''wrong''' indentation. ||
   || This row has a correct indentation. ||
   || This row has a correct indentation. ||

 * this is a correct block example.
   {{{
#!c
int i = 0;
printf(""%d"", i);
   }}}
}}}

Renders as:
 * this is a table example.
   || This row has a '''wrong''' indentation. ||
   || This row has a correct indentation. ||
   || This row has a correct indentation. ||

 * this is a correct block example.
   {{{
#!c
int i = 0;
printf(""%d"", i);
   }}}"	tdkim@…
3970	Wiki parsing error when using exclamation at the end of phrase	wiki system	0.10	topic-wikiengine	defect	minor		new	2006-10-19T16:35:53+02:00	2015-11-23T10:56:59+01:00	"When using this bold text:
{{{
'''testing!'''
}}}
I see this:

 '''testing!'''

It also happens with italics:

 ''testing!''
"	sid@…
5059	PageOutline macro is hardcoded to truncate long names	wiki system		topic-wikiengine	defect	minor		new	2007-03-29T18:37:41+02:00	2015-05-26T20:59:21+02:00	"when using `PageOutline` as of 0.10, long heading names are truncated, with an ellipsis ""..."" at the end.  This behavior should be removed, or at least an option added to `PageOutline` so that its configurable.

matt good refers to [changeset:3408] as the location of the change, where the call to `_parse_heading()` should get `False` as its last argument.
"	mike_mp@…
7721	Allow cascaded definition lists	wiki system		topic-wikiengine	enhancement	minor		new	2008-10-15T14:14:18+02:00	2015-05-26T20:59:21+02:00	"The definition list TracWiki syntax ""` name::`"" doesn't work eh n cascaded:
{{{
 name::
   sub-name1:: some text
   sub-name2:: some text
}}}
produces:
{{{
<dl>
 <dt>name</dt>
 <dd></dd>
 <dt>sub-name1</dt>
 <dd>some text</dd>
 <dt>sub-name2</dt>
 <dd>some text</dd>
<dl>
}}}

but should actually produce:
{{{
<dl>
 <dt>name</dt>
 <dd>
  <dl>
   <dt>sub-name1</dt>
   <dd>some text</dd>
   <dt>sub-name2</dt>
   <dd>some text</dd>
  </dl>
 </dd>
<dl>
}}}

This should be valid XHTML because the `<dd>` tag may include other block tags.

The same doesn't work in other lists, e.g.:
{{{
 * list
    definition::
}}}
is handled like:
{{{
 * list
 definition::
}}}
"	martin@…
1024	Each section should have a edit button	wiki system	0.8	topic-wikiengine	enhancement	normal		new	2004-12-08T13:14:04+01:00	2016-04-08T20:20:15+02:00	"ie
http://www.splitbrain.org/dokuwiki/wiki:dokuwiki"	anonymous
1936	indented ordered and unordered lists have additional bullets and numbers	wiki system	devel	topic-wikiengine	defect	normal		new	2005-08-17T18:49:23+02:00	2017-10-03T00:00:45+02:00	"if ordered and unordered lists start indented with more than two spaces, additional bullets and numbers are generated.

''examples:''
{{{
   * foo
   * bar

   1. foo
   2. bar

      * foo
      * bar

      1. foo
      2. bar

}}}
''output:''
   * foo
   * bar

   1. foo
   2. bar

      * foo
      * bar

      1. foo
      2. bar

if a list entry is indented more than three spaces as the previous list entry, additional bullets and numbers are generated too.

''examples:''
{{{
 * foo
     * bar

 1. foo
     1. bar
}}}
''output:''
 * foo
     * bar

 1. foo
     1. bar


tested using trunk r2068 and 0.8.4, python 2.3
"	vittorio@…
3307	Wiki pragma directives	wiki system	devel	topic-wikiengine	enhancement	normal		new	2006-06-23T15:37:15+02:00	2015-05-26T20:59:21+02:00	"We could add pragma directives for the Wiki engine.

This could be used to modify the way the engine behaves, as the pragmas are seen.

=== Use Cases ===

 * Section Numbering (similar to the reST's `.. sectnum::` directive) [[br]]

 * Respect line breaks (we currently do that programmatically) [[br]]

=== Implementation ===

There could either be a specific syntax for this
(e.g. like MoinMoin [MoinMoin:HelpOnProcessingInstructions#head-960b14e3643a3ae86600578a317ef2c67273a973 pragmas]), or a ![[Pragma]]` macro.

The macro could be a special macro, like ![[BR]] is, or a regular macro 
once the formatter object will be given to macros.

The macro will simply set a formatter ""user property"",
e.g. 
{{{
  formatter[pragma_name] = pragma_value
}}}

In other parts of the engine, such properties could be explicitely retrieved
e.g. in the `_heading_formatter`:
{{{
   do_numbering = formatter['sectnum']
}}}

"	Christian Boos
4140	Merge OutlineFormatter into Formatter	wiki system	0.10.1	topic-wikiengine	defect	normal		new	2006-11-12T19:49:14+01:00	2015-05-26T20:59:21+02:00	"Hi,

Macros like the !PageOutline make use of the !OutlineFormatter to build a table of contents. But it seems awfully inefficient that you'll have to run through the page twice in order to do just that. How about having the standard Formatter build the outline[] array just like the !OutlineFormatter does, so that one could refer to it at anytime during a macro? It'd be a really simple change too, merging both behaviours into one class. Then you'd just call the macros at the end of the wiki pages wherever you wanted an outline to be generated.

I'd be glad to submit this, if you require an extra hand,
- Jorge Pereira"	jpereira@…
6630	single || in a line mistaken for table formatting	wiki system		topic-wikiengine	defect	normal		new	2008-01-10T16:04:53+01:00	2015-05-26T20:59:21+02:00	"if you write sth like
  
{{{
DQL still uses the CONCAT() and not the || syntax
}}}

in a svn comment, the changeset view looks like

{{{
  DQL still uses the CONCAT() and not the syntax
}}}

so trac adds <td> </td> for ||. thats not correct in this case because the user wants to tell sth about the || operator.

see http://trac.phpdoctrine.org/changeset/3497"	Markus.Staab
8686	Export wiki documents in HTML format	wiki system	none	topic-wikiengine	enhancement	normal		new	2009-09-23T08:28:27+02:00	2022-05-25T14:19:26+02:00	"Now there are some plugins like wikiprint/pages2docbook can export the file to docbook/pdf/html...,But it is not enough

Every project will has a userguid,we can use word or docbook.Why not trac wiki? create a wiki page as Index,when export,just search all the relative wiki pages to form a pdf/html book.

This is very useful,can trac team realize it?"	wideweide@…
9251	Unable to escape number list	wiki system		topic-wikiengine	defect	normal		new	2010-04-21T15:56:19+02:00	2015-05-26T20:59:21+02:00	"Unable to properly escape number list while trying to make a definition list which have terms starting with a number and a dot.

So this:

{{{
 42. foobar:: test
}}}

Makes a number list.

{{{
 !42. foobar:: test
}}}

Makes a definition list, but ! is visible. It should be hidden - to escape number list.

For the sake of completeness it would be also useful to specify ! before :: to disable possible definition list."	Mitar
9688	Preformatted text in definition list rendered wrongly	wiki system	0.13dev	topic-wikiengine	defect	normal		new	2010-10-13T09:59:51+02:00	2015-05-26T20:59:21+02:00	"Suppose the following C++ code snippet:
{{{
class C {
  void f();
  ...
};
}}}
Then C++ programmers sometimes want to write a list like this:
{{{
 `C::f` :: compiles, but not tested at all
 ... :: ...
}}}
Here `C::f` is meant to be a method `f` defined in a class `C`.

But this markup yields a poor result:
 `C::f` :: compiles, but not tested at all
 ... :: ...

I think ""preformatted text"" should be rendered as written whatever enclosing construct may be."	NODA, Kai <nodakai@…>
10312	Multiple sub tables are not correctly processed by the WikiProcessor	wiki system	0.12.2	topic-wikiengine	enhancement	normal		new	2011-08-11T13:08:10+02:00	2011-08-11T13:33:47+02:00	"The following table definition isn't processed correctly:
{{{

{{{
#!table style=""margin: auto""
	{{{#!tr
		{{{#!th style=""background: lightgray""
			Head Column1
		}}}
		{{{#!th style=""background: lightgray""
			Head Column2
		}}}
	}}}
	{{{#!tr
		{{{#!td
			{{{#!table
				{{{#!tr
					{{{#!th style=""background: lightgray""
						Sub head column1
					}}}
					{{{#!th style=""background: lightgray""
						Sub head column2
					}}}
				}}}
                                {{{#!tr
					{{{#!td
						Sub column1
					}}}
					{{{#!td
						Sub column2
					}}}
				}}}
			}}}
		}}}
		{{{#!td
			{{{#!table
				{{{#!tr
					{{{#!th style=""background: lightgray""
						Sub head column1
					}}}
					{{{#!th style=""background: lightgray""
						Sub head column2
					}}}
				}}}
                                {{{#!tr
					{{{#!td
						Sub column1
					}}}
					{{{#!td
						Sub column2
					}}}
				}}}
			}}}
		}}}
	}}}
}}}
}}}

I get allways the following error message:
''' !#tr must contain at most one table'''

If you remove the table definition in the last column, the code will processed correctly."	f.rochlitzer@…
10523	TitleIndex: add option 'show_title' to display first level heading	wiki system	0.12dev	topic-wikiengine	enhancement	normal		new	2012-01-12T21:36:10+01:00	2015-09-03T12:29:23+02:00	"Besides some bug fixes, #8925 proposed a nice enhancement idea for the `[[TitleIndex]]` macro:
 //Like the TOCMacro does, the TitleIndex macro could display the first level heading in addition to the page name when a `show_title` parameter is given.//

However I think it would be prudent performance-wise to **not** search for the title ""dynamically"" in all pages. Rather I think this should depend on some planned features for the Wiki (#4431 + explicit storage of the title in a //title// property, see ticket:8925#comment:9).
"	Christian Boos
10734	``` as a {{{ alternative	wiki system		topic-wikiengine	enhancement	normal		new	2012-06-23T10:32:57+02:00	2014-02-18T00:51:23+01:00	It is not that [http://github.github.com/github-flavored-markdown/ GitHub] uses them, it is that {{{```}}} are easier to type than {{{{{{}}} and `}}}`	anatoly techtonik <techtonik@…>
13187	Text after diff block is not rendered	wiki system	1.0-stable	topic-wikiengine	defect	normal		new	2019-08-02T05:33:21+02:00	2019-08-26T10:21:38+02:00	"I enter the following text in ticket comment, but diff block only is rendered. ""//This text disappears//"" is not rendered. Removing `{{{` after `==== Python Traceback ====` line, the issue goes away.

{{{
{{{#!diff
diff --git a/trac/web/main.py b/trac/web/main.py
index c75199f79..4479ac5a0 100644
--- a/trac/web/main.py
+++ b/trac/web/main.py
@@ -761,12 +760,13 @@ def send_internal_error(env, req, exc_info):
             %(interface_customization)s
             ==== Python Traceback ====
             {{{
-            %(traceback)s}}}""""""),
-            method=req.method, path_info=req.path_info,
-            req_args=pformat(req.args), sys_info=sys_info,
-            enabled_plugins=enabled_plugins,
-            interface_customization=interface_files,
-            traceback=to_unicode(traceback))
+            %(traceback)s}}}"""""")
+        return gettext(msgid,
+                       method=req.method, path_info=req.path_info,
+                       req_args=pformat(req.args), sys_info=sys_info,
+                       enabled_plugins=enabled_plugins,
+                       interface_customization=interface_files,
+                       traceback=to_unicode(traceback))

     # Generate the description once in English, once in the current locale
     description_en = get_description(lambda s, **kw: safefmt(s, kw))
}}}
This text disappears....
}}}
"	Jun Omae
11359	unintentional Camelcase links with slashes e.g. Bla/Blo	wiki system	1.0-stable	undecided	defect	minor		new	2013-11-10T20:12:33+01:00	2014-08-14T23:39:07+02:00	"Two ore more Uppercase words separated by a slash e.g. `Bla/Blo` are treated as CamelCase and therefore generate a wikipage link. This is not welcome. It should better not be hyper-linked.

== Examples ==
""Bla/Blo"", ""Tom/Thomas"" and ""Berlin/Germany"" produce unwanted wiki-links to non-existing wiki pages.

== Argumentation ==

In routine work it happens quite often that unintended (dead) hyperlinks are created when writing texts fragments e.g. `in Berlin/Germany` or `Tom/Lisa said`. [[BR]]
In my opinion it should be like this:
 - `Germany/Berlin` -> shall be not be linked,
 - `LocationGermany/Berlin` -> shall be linked
because the first one can occur in natural writing and '''natural writing shall not be wiki-interpreted'''. In my opinion `Germany/Berlin` shall not be interpreted as CamelCase.

According to CamelCase and WikiPageNames slashes are allows to make ""hierarchy"" links. Rule 5 of WikiPageNames says: 
> 5. ''The use of slash ( / ) is permitted in page names (possibly representing a hierarchy).'' 
In my opinion this rule should be changed as follows:
> 5. ''The use of slash ( / ) is permitted in page names (possibly representing a hierarchy). In this case the above rules apply to each of the name fragments.' 

== Severity and Workaround

I do not really have a big problem here, since:
 - one can simple insert spaces `Germany / Berlin` or
 - escape the link with an exclamation mark e.g. `!Camel/Case` or
 - use one of the configuration options e.g. `ignore_missing_pages = true`.

However I think that the wiki processor shall not negatively interfere with natural writing. 

== Relation and History ==
There is also an old discussion in #733 (especially comment:3). It seemed to be solved for TRAC 0.9 in 2004 but until then somehow there was an regression and the unwanted effect reappeared..

The effect of unwanted linking is reported for TRAC versions 0.12, 1.0 and 1.1(dev). Other version I cannot test other versions now, but from my memories I believe that TRAC 0.10 and/or 0.11 did not suffer from the effect."	anonymous
11641	"html5 support for ""export"" links in trac wiki"	wiki system	1.0.1	undecided	defect	normal		new	2014-06-08T10:10:56+02:00	2014-08-02T08:08:47+02:00	"I am attempting to link from my wiki to web documentation within the source (git) repository.
This works as expected if the documents are xhtml, but not if the file is html5.

For example, adding the following code to the wiki `[export:path/to/index.html]` creates a link to that file within the git repository which is displayed as expected when the html file has the following header:


{{{
<!DOCTYPE html PUBLIC ""-//W3C//DTD XHTML 1.0 Transitional//EN"" ""http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"">
<html xmlns=""http://www.w3.org/1999/xhtml"">
<head>

}}}

However, an error occurs when the html document has a html5 header:


{{{
<!DOCTYPE html>
<html lang=""en"">
  <head>

}}}

The error message (within the browser) is browser dependant, however, the error message printed in firefox: 


{{{
""XML Parsing Error: mismatched tag. Expected: </link>....""
}}}
 

suggests that trac may be attempting the parse the html5 document as xml?

Note that it is necessary to set `[browser] render_unsafe_content = yes` in order to enable rendering of html documents in this way.
"	dan.halligan@…
4536	render_unsafe_content in [4472]  could be restricted to read-only pages.	wiki system	devel	unscheduled	enhancement	minor		new	2007-01-13T20:47:03+01:00	2010-06-24T19:09:14+02:00	In my case i don't want to allow the unsafe content to be available on all pages (the scripts are used to allow documentation to have special links for firefox browsers to load pkcs11 modules). So instead of turning this feature on wiki-wide I would be happy and more secure if i could turn it on for read-only pages only (as I'm willing to make that page read-only)	martin@…
1120	Delete all changes made from given IP.	wiki system	devel	unscheduled	enhancement	normal		new	2005-01-11T01:44:05+01:00	2022-01-08T10:39:23+01:00	"Because wicki of my trac installation was lately filled with lots of spam messages i wrote quick and dirty hack which allows me to remove all changes made from given ip.

Maybe this will be helpfull to others too."	prefiks@…
4492	Automatic backlinks for tickets based on document referer	wiki system	0.10.3	unscheduled	enhancement	normal		new	2007-01-04T07:38:43+01:00	2015-05-26T20:55:39+02:00	"This is distinct from TracCrossReferences (similar to BackLinks (#611)); but solves a similar problem.

 * Every view of a ticket records the referring URL; and increments the count for number of referrals.
 * The ticket page shows the number of referrers as a 'pages and tickets which mention this ticket' widget

A simple list of allowed URL patterns or referrers can prevent spam easily.

The benefit of this approach is to organically strengthen the relationship between tickets, rather than rely on explicit macros. Garbage collection could be optionally included; so that links dissolve over time."	daniel.oconnor@…
6062	MediaWiki-style alternative wiki syntax	wiki system		unscheduled	enhancement	normal		new	2007-09-19T21:58:00+02:00	2020-12-21T04:03:51+01:00	"There are compelling reasons to support mediawiki format completely in the core trac release.  
 1. jamwiki is cloning mediawiki in Java and keeping the format identical so Java-based projects can easily integrate a full wiki.
 2. drupal_wiki is likewise supporting mediawiki format as its native format
 3. mediawiki is very widely used in intranets already including very large ones like the US inteligence services' ""Intellipedia""
 4. mediawiki is also widely used for documentation and requirements engineering by open source and share-alike (including free software and open content) projects - most of the target market for trac has to support mediawiki anyway, and in some cases has a strong motive to update large public wikis running on mediawiki
 5. of hundreds of millions of page reads from wikis every year, the overwhelming majority of those are from wikis using mediawiki format.  The public interest in supporting, teaching and implementing this format is now immense and unstoppable, even if a markedly ""better"" wiki format existed, it would not overcome this data compatibility problem. 
 6. Most importantly, almost all technical and requirements domain concepts that might need to be referred in specifications already have names in most widely used languages thanks to Wikipedia.  Working out the most neutral and least controversial names for tens of thousands of scientific, technological, business and other concepts has been the greatest contribution of the Wikipedia project.  Since those names are expressed in the characters allowed in mediawiki names, with many conventions growing out of Wikipedia usage, any deviation (any more or less permissive use of characters) would ""break"" the character set and force ""translation"" of names of concepts to determine if the concept existed in the Wikipedia namespace (or ""GFDL corpus namespace"" to be legally more exact as all Wikipedia content is under GFDL and other mediawikis copy the names under this license).

Accordingly, the benefits of keeping trac internal data and user's internal documentation in mediawiki format are profound: 
 7. any concept whatsoever that is named in a document can be quickly checked to see if it exists in Wikipedia or a list of other public wikis, and the option to link it added
 7. statistically improbable phrases can be related to more standard phrases by relatively simple programming/searching methods, e.g. consulting Amazon lists of keywords attached to books, checking for matches with text of Wikipedia articles
 8. any page managed by Trac can be instantly moved to, or can instantly incorporate updates from, or possibly embed or be embedded in, any other page in a large public wiki or mediawiki- or drupal- or jamwiki- based intranet
 9. TracWiki could become the Python equivalent of jamwiki (Java) and possibly be included in other applications as a module as is intended for jamwiki;  This would better distribute the maintenance effort and spread trac
 10. mediawiki extensions would be encouraged to integrate trac so that, for instance, bugs in mediawiki-based services would be able to contain trac links directly in talk pages and edit summaries. 
 11. anonymous trolls are more likely to complain about errors seen in trac, as all anonymous trolls already know mediawiki format so they can troll Wikipedia
 12. such trolls will no longer appear to write long whiny tickets like this.  These advantages will get more significant, not less, over time, as the number of trolls in the world increases (we may be in the Troll Age).

To converge/eliminate the existing tracWiki format would be relatively simple as most of mediawiki's text conventions (regarding italics, boldface and headings) are supported already.  The link format, relying on double square brackets, conflicts with the existing tracWiki macro format, but this is easily resolved by a method similar to methodNotFound in Smalltalk, etc.:  if a local macro by that name does not exist, the behaviour defaults to an open link.  This is then easy to replace with another macro that can default to find (and link) the appropriate article (via the methods listed) in a more public wiki, or a cascade of nested wikis of decreasing specificity.  This is similar to the technique wikinfo.org already uses to embed Wikipedia articles when wikinfo itself has no article on that topic. 

Discouraging WikiWords is of high priority as they encourage bad English and make sentences containing links unreadable and confusing to technical people (exactly why mediawiki abandoned them).
"	anonymous
6800	A plugin can not extend HTTP headers of the main trac site if it is a private trac.	wiki system	0.11b1	unscheduled	defect	normal		new	2008-02-10T19:14:00+01:00	2010-06-24T18:20:56+02:00	"I'm trying to make yahoo.com OpenID provider not complain about ""fraudulent"" sites by implementing OpenID 2.0 XRDS discovery to the th:AuthOpenIdPlugin copy @ http://ideelabor.ee/opensource/log/python-components/authopenidplugin 

Discovery requires the 'base URL' of the trac instance (example.com/trac/project1) to have a X-XRDS-Location header pointing to a XML file. I got over the problem of 'tapping' into wiki module by calling irectly the process_request method of WikiModule after I've added the extra header in the tapping request match: http://ideelabor.ee/opensource/changeset/154/python-components/authopenidplugin

A quick test with a public wiki (anonymous has WIKI_VIEW rights) and yahoo.com had success, but trying another project where anonymous users have zero rights, the wiki system raises a permissions error with req.send_error which clears all outgoing headers set before via this hack.

Question: How can I make a plugin emit an extra header on the main page of the trac instance?

Maybe req.send_error should not clear experimental (X-*) headers?



"	martin@…
6824	paragraph-links should wait for images to load	wiki system		unscheduled	enhancement	normal		new	2008-02-13T17:37:54+01:00	2010-06-24T18:47:12+02:00	"I noticed, if i have a long wikipage containing many paragraphs and several images (through imagemacro), if i then follow a paragraph-link (eg. !http://192.168.0.1/trac/wiki/WikiPage#paragraph) it first jumps to the #paragraph, and then loads the images. Since the images takes longer time to load, the screen will no longer be positioned at the intended paragraph. They are offset by the height of the images after they load. This will of course only occur if the images reside above the paragraph you're following a link to. If you hit back & forward in the browser again, the offset will be smaller since the images are cached, but still a small offset just enough to not see the paragraph.

So my suggestion is to have it jump to the paragraph after the page finished loading, or atleast after the images are loaded.
I have been a trac user for a while, and this ""bug"" has been in all versions i've worked with, and is still in 0.11dev.

Thank's!"	simon[at]solida[dot]se
9385	line-referencing wiki links	wiki system		unscheduled	enhancement	normal		new	2010-05-28T17:37:02+02:00	2010-05-30T12:23:42+02:00	"Would be nice to have an ability to build a link like this:

{{{
wiki:MyWikiPage@123:10-20,100,103#L99
}}}

The same behavior as with source code. Trac should highlight the lines in wiki pages."	team@…
9618	WIKI_VIEW_SOURCE privilege	wiki system	0.13dev	unscheduled	enhancement	normal		new	2010-09-15T03:26:21+02:00	2010-09-15T13:55:21+02:00	"I would suggest to add `WIKI_VIEW_SOURCE` privilege. Currently, if the user does not have `WIKI_EDIT` privilege it cannot see source code of wiki page. It can only download it to computer and then open it, which is cumbersome just to, for example, copy-paste something out. On the other hand everybody can see source (download it) if they have `WIKI_VIEW` privilege what is again something which is maybe not always preferred.

Similar can be also said about history."	Mitar
10334	Privilege for viewing Wiki page history	wiki system		unscheduled	enhancement	normal		new	2011-08-30T16:22:04+02:00	2017-04-16T23:22:36+02:00	"Wiki page histories sometimes provide a security concern when revisions may have contained unprotected sensitive data. TracProtected is a very handy macro, but non authenticated users can easily browse the Wiki page's history for revision with unprotected data.

While removing or pruning Wiki page histories goes against the revision concept, a privilege specific to viewing old Wiki page revisions should alleviate this concern. 

In practice is could be defaulted to allow all, but easily be a privilege given only to authenticated users when revision history security becomes a concern."	soco@…
10872	Add New Page and Link to current page	wiki system	1.0dev	unscheduled	task	normal		new	2012-09-27T13:45:33+02:00	2019-10-05T20:25:09+02:00	"Trac is a wonderful product with many great plugins. tags, menus, wanted page, git, announcer...  And I wish it could be easier to add new pages.

Can I just click a button or link to add a new page, and enter the page name, then keying the content? Also if a checkbox option exists for link the new page to the previous, it would be perfect.

If the function already exist by any plugins or macros, please let me know.
Plus, I would like to add the function/plugin to trac and release it.

But I don't know how to implement the plugin, anyone could help?
"	david.ullua@…
11731	TracLinks notations for showing a wiki diff	wiki system		unscheduled	enhancement	normal		new	2014-08-24T03:39:29+02:00	2014-11-23T15:38:54+01:00	"I often find myself adding links such as wiki:TracInstall@374?action=diff in order to reference a wiki change from a ticket comment. TracInstall@374 could be used, which renders the page with a `#info` containing a link to the diff, but that's less obvious when I really want to just shown the diff and also requires two clicks to get to the information I want to emphasize.

wiki:TracInstall@374?action=diff is not too awful, and it could be wrapped in brackets, but that results in [wiki:TracInstall@374?action=diff], and it's not obvious to the reader that the link directs to a diff.

So, I'm unsure what, if any, the ideal addition to the TracLinks syntax would be, but I'm thinking of something like `diff:TracLinks@374`, with the complementary explicit version `wiki:diff:TracLinks@374`. The `diff` part is an action, so I'm not sure whether placing it after the realm would fit with the general patterns adopted by TracLinks.

Maybe TracInstall@374 is good enough, or maybe we just need to make that link to a diff (or the entire `#info`) a little more prominent."	Ryan J Ollos
12262	CSS rules for wiki controls can conflict with wiki content	wiki system	1.0.9		defect	normal		new	2015-12-02T23:18:14+01:00	2016-02-06T11:30:51+01:00	"How to reproduce:

1. Edit any wiki page

2. Add two headings to the page, one called 'save', the other 'Save'
{{{
= save
= Save
}}}

3. Preview the page

4. Notice how the 'save' heading is indented, while 'Save' is not.

wiki.css has the rule
    #delete, #rename, #save { margin-left: 3em }
to indent the 'Submit Changes' input element among others, but headings are given the ID of their content, so there's a conflict here with the 'save' heading, and a number of other possible heading titles.

This could be fixed by adding a element selector to the wiki CSS rules
    input#save
or using a new class for wiki controls and divs and adding it to the CSS rules, or renaming the ID of the controls, or any number of other ways."	anonymous
12512	Support relative path in ImageMacro when rendering wiki page in repository browser	wiki system			enhancement	normal		new	2016-06-09T09:20:40+02:00	2016-06-09T10:37:58+02:00	"We have a number of (trac-)wiki pages that we'd like to manage in our svn repository, but have them rendered in our trac. Unfortunately, the !ImageMacro doesn't seem to support relative paths - this would be extremely useful since we have those documents in several branches, hence an absolute path is a no-go.

I've attached a patch that adds support for that so you can now refer to images like this:
{{{[[Image(../pics/Example1.png, 250px)]]}}}"	hoessler@…
13389	Wikicreole line breaks not working in cases with colons?	wiki system	1.4.2		defect	normal		new	2021-04-11T09:46:59+02:00	2021-04-11T12:58:23+02:00	"Having a weird issue with the wikicreole line break syntax.

===== Issue wiki markup
{{{
Mon-Fri 8:30am-7pm\\Sat 11am-8:30pm\\Sun 10am-5:30pm

Mon-Fri 8:30am-7:00pm\\Sat 11:00am-8:30pm\\Sun 10:00am-5:30pm

Mon-Fri 8:30am-7pm\\Sat 11am-830pm\\Sun 10am-5:30pm
}}}

===== Issue rendering

Mon-Fri 8:30am-7pm\\Sat 11am-8:30pm\\Sun 10am-5:30pm

Mon-Fri 8:30am-7:00pm\\Sat 11:00am-8:30pm\\Sun 10:00am-5:30pm

Mon-Fri 8:30am-7pm\\Sat 11am-830pm\\Sun 10am-5:30pm

These don't all render correctly. The first just the first line break renders.

In the second none of the line breaks render.

In the last one I removed the `:` in `8:30pm` and then it renders correctly. On the trac instance where I encountered this I also noticed that if I put spaces around the `\\` it'll render correct. And I can replace the `:` with `&#58;` and make it work (which is a feature of the [https://trac-hacks.org/wiki/WikiExtrasPlugin WikiExtras] plug-in).

I'm guessing I'm looking for some edge case in the wiki parser."	benjamin.a.lau@…
9619	Side-by-side editing fails if Preview significantly longer than source; needs smart, vertical locking!	wiki system	0.12-stable	1.0	defect	major	Christian Boos	reopened	2010-09-15T12:10:03+02:00	2023-01-10T14:50:43+01:00	"The side-by-side editing is rendered useless, if the Preview is significantly longer (due to large text, tables and inline images) than the source code. You might end up in a situation where the related source code to what you currently see in the Preview is 1 or 2 pages up the screen and it is currently impossible to see source code and related Preview together at once. This is a serious issue in my opinion. 

You can make a simple test by positioning a few large images using ![[Image(XYZ.jpg)]] underneath each other: The source code only takes a few lines, whereas the last image might by two screens down the window scroll bar.

A solution should look like this: The preview get dynamically positioned in such a way, that it (optionally) aligns vertically with the cursor position in the source code window, so that one really sees what one's editing."	klein@…
4279	add a plugin to comment on a page	wiki system	0.10.2	next-major-releases	enhancement	major		new	2006-11-28T11:07:37+01:00	2023-09-28T20:17:01+02:00	"best is if can be inline. see: http://www.jackslocum.com/blog/2006/10/09/my-wordpress-comments-system-built-with-yahoo-ui-and-yahooext/

or, http://gplv3.fsf.org/comments/gplv3-draft-2.html

another mode can be mysql style: http://dev.mysql.com/doc/refman/5.0/en/select.html

or, maybe combined. have a way of marking a line/block of text and then enter a comment, so when a viewer clicks the mark, it is a link to the comment down the page."	ittayd@…
2523	TODO's from Sourcecode as a ticket	wiki system	0.9.2	next-major-releases	enhancement	minor		new	2005-12-25T02:36:40+01:00	2017-09-04T10:19:09+02:00	"If you have in the Source Code:
{{{
  // TODO: Add Error Handling
}}}
This should generate a Ticket.


Maybe I write a patch for this..."	anonymous
3335	Improve the rendering of the wiki syntax for citations	wiki system	0.9.5	next-major-releases	enhancement	minor		new	2006-06-28T17:43:53+02:00	2015-05-26T20:50:57+02:00	"A little thing, but looks nicer IMHO

{{{
#!css
blockquote p { margin: 0 0 1em 0; }
blockquote.citation { 
 margin: -0.3em 0;
 padding: .5em 0 0 .5em;
 border-style: solid; 
 border-width: 1px 0 0 2px; 
 border-color: #b44;
}
}}}

"	Christian Boos
4695	Icons for InterTrac and InterWiki links	wiki system	0.10.3	next-major-releases	enhancement	minor		new	2007-02-08T20:19:07+01:00	2015-05-26T20:50:57+02:00	"provide a facility to configure Icons for InterTrac and InterWiki links.

i.e. the Wikipedia favicon for a Wikipedia InterWiki link. this Icon can stay alone if no Text there for the given link.

"	Holger Winkelmann <hw@…>
5227	provide option to insert summary in a ticket link	wiki system	devel	next-major-releases	enhancement	minor		new	2007-04-26T20:43:32+02:00	2015-05-26T20:50:57+02:00	"It would be nice to be able to create a ticket link that automatically includes the summary line for the ticket.  A possible syntax for this could be `[ticket:23:summary]` and have it do the same thing as `[ticket:23 #23: Prettier ""Access Denied"" message.]`, so it would look like [ticket:23 #23: Prettier ""Access Denied"" message.]."	Eli Carter
5498	Use #. as a wiki markup for ordered list	wiki system	devel	next-major-releases	enhancement	minor		new	2007-06-12T14:56:33+02:00	2015-05-26T20:50:57+02:00	"It would seem natural to write ordered list using the `#` character, such as:
{{{
  #. first item
  #. second item
}}}

This syntax would not replace the current syntax, i.e. using `1.`, but would be an add-on.
"	Emmanuel Blot
6863	Included wiki page makes web research irrelevant	wiki system		next-major-releases	enhancement	minor		new	2008-02-20T18:42:57+01:00	2010-09-23T14:57:08+02:00	"OK, this may seem odd, but I've started using trac 3 days ago and spent a lot of time setting up everything, learning pythonm etc.

The biggest problem I've faced while doing this was to find relevant litterature to help me in all those procedure concerning trac configuration/plugin setup/etc.

In fact, while I was google-ing key words, most of the proposed links were actually the wiki page of installed trac websites containing exactly the same content as the main site...

I wanted to point that out, as a noob into the trac country. Information is Hard to find as it is always the same. Finding websites with different explanation is try-and-error trial.

I'm not sure how this could be corrected.. Maybe a ""listener"" for robots, a (don't remember how it's spelled) ""don't follow these links"" for the wiki stuff unless page is changed by the websites users..."	david.coll.78@…
9048	Wiki history empty if end revision precedes start revision	wiki system	0.12dev	next-major-releases	defect	minor		new	2010-02-11T09:58:44+01:00	2021-01-12T09:21:21+01:00	"How To Reproduce:
 1. go to http://trac.edgewall.org/wiki/WikiStart?action=history
 2. in the first radiobutton column click on, say, version 130
 3. in the second radiobutton column click on, say, version 128
 4. Click the ""View Changes"" button
 5. Note that the resulting page shows differences between
    Version '''128''' and Version '''128'''.
    Version 130 has been completely neglected.

System Information:
Just verified on trac.edgewall.org (currently running 0.12dev-r9164).

What it should do instead? Not sure:
 * show differences between 128 and 130 (i.e. swap versions so
   that they are correctly ordered), or
 * show backwards differences, or
 * anything else?
"	luca.ceresoli@…
9601	Disallow robot navigation for edit pages	wiki system		next-major-releases	defect	minor		new	2010-09-02T19:49:31+02:00	2010-09-23T15:03:39+02:00	"Quite often search results contain links to Trac wiki pages that lead to ?action=edit URLs. These could be disallowed for crawlers.

http://www.google.com/search?q=genshi+%3Faction%3Dedit"	anatoly techtonik <techtonik@…>
10945	"horizontal scrollbar in ""editing wiki"" textareas"	wiki system		next-major-releases	enhancement	minor		new	2012-11-08T16:15:04+01:00	2015-11-18T12:51:12+01:00	"Hi there, 

Could you please add an horizontal scrollbar to ""Editing wiki"" textareas 
i.e. could you please change 
{{{<textarea id=""text"" class=""wikitext"" name=""text"" cols=""80"" rows=""20"">}}}
to 
{{{<textarea id=""text"" class=""wikitext"" name=""text"" cols=""80"" rows=""20"" wrap=""off"">}}}
Wrapping is really annoying when you have large arrays.
I know the ""off"" value of the wrap attributes is not (yet?) supported in HTML5 (http://www.w3schools.com/html5/att_textarea_wrap.asp).
But all browsers I've tried support it: Firefox(16), Opera(12), Chrome(23), Safari(5), IE(7).
And there does not seem to exist any other way to do so (css white-space:nowrap, ...).

Cheers, 
Mathieu
"	mtrocme
11816	Some comment TracLinks are incorrectly displayed as missing	wiki system		next-major-releases	defect	minor		new	2014-11-11T02:39:16+01:00	2022-09-23T13:44:11+02:00	"It can be seen in comment:3:ticket:11813 that the following two TracLinks are incorrectly displayed as missing links.
 * comment:2:ticket:956 ([/ticket/956#comment:2])
 * comment:1:ticket:1752 ([/ticket/1752#comment:1])

Recent changes to comment TracLinks were made in #10742."	Ryan J Ollos
108	OrphanedPages macro	wiki system	0.5.1	next-major-releases	enhancement	normal		new	2004-03-02T19:19:38+01:00	2015-03-02T22:31:46+01:00	"It would be good to have a list of pages that aren't linked to from anywhere.

Example:   http://moinmoin.wikiwikiweb.de/OrphanedPages"	daniel
109	MissingLinks, an index over missing wiki pages	wiki system	0.5.1	next-major-releases	enhancement	normal		new	2004-03-02T19:22:03+01:00	2018-08-04T09:54:30+02:00	"It would be good to be able to list all links that lead to non-existing pages.

Also true for tickets and changesets of course.

Example: http://moinmoin.wikiwikiweb.de/WantedPages"	daniel
1216	wiki pages caching	wiki system	devel	next-major-releases	enhancement	normal		new	2005-02-22T18:22:45+01:00	2020-06-14T05:34:50+02:00	"Most of the time wiki pages can be considered as a static content. So instead of generating and regenerating wiki pages -> html output, perhaps it would be useful to cache generated HTML output of wiki pages on the disk. Next time, page is requested checking if there have been changes - if not serve the file, otherwise - regenerate HTML page and serve newly generated file. 

Sure this raises a question, what to do with embedded python macroses (see wiki-macros).
Having such functionality, would help to reduce server load and would be very helpful especially with wiki rst (Restructured Text extension). 

This ticket is rather an attempt to find out if there is a demand for such functionality. Consider this ticket as a discusion starting point."	zilvinas
1376	Alternate Template for wiki pages	wiki system	0.8.1	next-major-releases	enhancement	normal		new	2005-03-29T22:32:03+02:00	2010-06-24T15:54:01+02:00	"Alternate templates for wiki pages could come really handy when you need to format the wiki text for the end users. For example users can click on a help button and the we can pop up a small window with documentation without any trac navbar or edit buttons. 

Also, this would allow to separate ""Project Page"" with project description wiki pages and ""Developer Page"" with all the power of trac."	amasiar@…
2293	Make rss-feeds of more parts of trac available	wiki system	0.9	next-major-releases	enhancement	normal		new	2005-11-02T10:39:16+01:00	2010-11-28T20:02:18+01:00	"Hi there,

I frequently want to have rss feeds that monitor specific parts of a trac install. Now the only part of trac witch offers rss feeds are the TracTimeline, the TracReports and TracQuerys and the TracBrowser.

What I'd want is more flexibility mostly in the wiki, so I can have rss feeds of changes on a individual website, or only websites with a comon prefix.

Now, offering rss links on every page would be not very good I think, as it would be hard to explain on which page you get an rss feed of what option - BUT on the Timeline page it would be very natural, to restrict it only one page, or only pages with a specific prefix.

And then simply offering an rss feed for the currently selected options."	Martin Häcker <spamfaenger@…>
3416	IFrame	wiki system	0.9.6	next-major-releases	defect	normal		new	2006-07-17T12:38:13+02:00	2020-04-22T08:16:36+02:00	If an iframe added to the wiki, via the HTML formatter, this is not viewed.	anonymous
5821	Wiki blame support	wiki system	devel	next-major-releases	enhancement	normal		new	2007-08-05T05:42:13+02:00	2014-08-04T05:29:58+02:00	"One feature we never got implemented into the blame branch from 2006 was blame support for wiki pages.  I now have a straw-man implementation for review.  Please give this patch a try on your 0.11-dev install and specifically let me know:

 * Does it produce ''correct'' blames on your pages?
 * Is it fast enough?
 * Should there be a new permission for annotations? some meta tags to disallow robots?
 * Should there be something more like an IBlameAnnotator with callbacks for rev links, or is this best handled through the existing IHTMLPreviewAnnotator?  I could see a lot of possibility for reuse if we eventually have versioned tickets and vc backends that don't support blames natively.
"	Tim Hatch
6623	"emitting invalid xml:space=""preserve"" attributes on wiki and ticket pages (causes failed W3C validation)"	wiki system	0.11b1	next-major-releases	defect	normal		new	2008-01-09T16:57:38+01:00	2018-07-29T03:59:54+02:00	"I'm running [http://cmrg.fifthhorseman.net/ a newly-updated trac site] on version 0.11b1, using genshi 0.4.4.

When [http://validator.w3.org/check?uri=http%3A%2F%2Fcmrg.fifthhorseman.net%2F&charset=%28detect+automatically%29&doctype=Inline&group=0 testing it against the W3C's XHTML validator], it is almost entirely compliant output, with one exception:

{{{
 Line 65, Column 49: there is no attribute ""xml:space"".
      <div class=""wikipage searchable"" xml:space=""preserve"">
}}}

The W3C itself [http://www.w3.org/TR/REC-xml/#sec-white-space says that this is legitimate XML], but that it must be ""declared if it is used"".  i'm not enough of a web standards guru to be able to tell what that means, or where to fix the problem (is it a problem with genshi?  with trac?  with the W3C validator?)

Trac itself is so close to full validation that it would be a real shame for this one thing to slip through."	Daniel Kahn Gillmor <dkg-debian.org@…>
8223	Mozilla/Firefox displaying images through html processor	wiki system	0.11.1	next-major-releases	defect	normal		new	2009-04-22T17:43:57+02:00	2019-09-06T19:51:32+02:00	"Hi,[[BR]]
I'm having trouble getting the wiki to display images.
 - render_unsafe_content is set to 'true'
 - it does this no matter with basic theme and other themes
 - I think I've tried all forward and back slash variations.
Any ideas? I'm running out.[[BR]]
See code and specs below.[[BR]]
Thanks,[[BR]]
Benoit

p.s. please be merciful as I don't have access to google groups.
----
trac: 0.11[[BR]]
server: python 2.4[[BR]]
client: WinXP SP2[[BR]]
browsers: IE7.0.57, Firefox 3.0.8[[BR]]
----
This code works in a trac 0.11 wiki page, viewed with IE7
{{{
{{{
#!html
<img alt=""image"" src=""file:///\\<server-path>\thumb.jpg""/>
}}}
}}}
The same code DOES NOT work in a trac 0.11 wiki page, viewed with Firefox 308 (only alt is shown)
{{{
{{{
#!html
<img alt=""image"" src=""file:///\\<server-path>\thumb.jpg""/>
}}}
}}}
This HTML page works in Firefox 308, off my C:\
{{{
<!DOCTYPE html PUBLIC ""-//W3C//DTD XHTML 1.0 Strict//EN"" ""http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"">
<html>
<body>
<img alt=""image"" src=""file:///\\<server-path>\thumb.jpg""/>
</body>
</html>
}}}
Oh… and this doesn't work in IE or FF (""/<server-relative>/thumb.jpg"" is diplayed on screen)
{{{
[[Image(//<server-relative>/thumb.jpg)]]
}}}"	benoit.moniere@…
8727	cannot create TracLinks to attachments with number sign in file name	wiki system	0.11.5	next-major-releases	defect	normal		new	2009-10-09T03:26:12+02:00	2015-05-26T20:50:57+02:00	"attachments with the number sign (#, also referred to as hash mark or pound sign) can be uploaded properly into trac, and the link generated in the Attachments section of the ticket works properly.

however, i cannot create TracLinks to the file.
{{{
attachment:attachment#1.txt
}}}
attachment:attachment#1.txt
{{{
attachment:'attachment#1.txt'
}}}
attachment:'attachment#1.txt'
{{{
[attachment:attachment#1.txt]
}}}
[attachment:attachment#1.txt]
{{{
[attachment:'attachment#1.txt']
}}}
[attachment:'attachment#1.txt']

this is important for us because we document everything the client sends us, including file attachments, which sometimes come named with the number sign."	jhn@…
9046	Cannot create a TracLink to heading in ticket description	wiki system	0.12dev	next-major-releases	defect	normal		new	2010-02-10T22:02:44+01:00	2014-07-29T17:02:39+02:00	"Perhaps an over-extension of the intended functionality of TracLinks, but I thought I would report it just in case it is a true defect in the intended design.

One can link to a section heading in a description: `comment:description#anchor`.

However, it doesn't seem to work to link to a section heading in the description field of another ticket: `comment:description#anchor:ticket:num`.

For example, see:
 1. [/demo-0.12/ticket/52#comment:1]
 1. [/demo-0.12/ticket/17#comment:2]

The resulting error when selecting the TracLink in (1) is:
{{{
#!html
<div class=""system-message"">
No handler matched request to /ticket/ticket
</div>
}}}"	Ryan J Ollos
2717	Create window title on wiki pages from = The title =	wiki system	none	topic-wikiengine	enhancement	minor		new	2006-02-03T12:05:56+01:00	2015-11-30T22:31:52+01:00	"This is what [http://wikkawiki.org Wikka] does: They take the text from the h1 headline which would be the first {{{= This is a headline =}}} wiki code on the page and display it as page title instead of the camel case page name.

See for example: http://wikkawiki.org/UpgradingFromWakkaWiki

Wiki-Name of the Page: {{{UpgradingFromWakkaWiki}}}[[BR]]
Displayed title: {{{Wikka: Migrating from WakkaWiki to Wikka Wiki}}}[[BR]]
which the get from this code 
{{{
===== Migrating from WakkaWiki to Wikka Wiki =====
}}}
which means h1 in Wikka syntax.

The purpose of this proposal is the create more readable window titles."	Markus Tacker <m@…>
4439	PageOutline macro produces empty <li> elements	wiki system	0.10.3	topic-wikiengine	defect	minor		new	2006-12-20T17:13:23+01:00	2015-05-26T20:59:21+02:00	"When a level 3 section is immediately followed by a level 1 section, the macro generates an empty <li> element. It happens for every n+2 level section that is immediately followed by a n level section.

It doesn't shows up in normal circumstances because empty `<li>` elements are not displayed.
But having customized the CSS to show section numbers in the TOC, those additional elements are displayed (at least with firefox or opera, but not IE).

How to reproduce the bug:

Modify the file ''templates/site_css.cs'':
{{{
/* Auto-numbering TOC's elements */
.wiki-toc ol {counter-reset: toc;}
.wiki-toc ol li:before {
        list-style-type: decimal;
        list-style-position: inside;
        content: counters(toc, ""."") "" "";
        counter-increment: toc;
}
}}}

And the create a wiki page like this:
{{{
[[PageOutline()]]

= First section =

=== First subsection ===

== Second subsection ==

=== Sub-subsection ===

= Second Section =

}}}"	Florent Angebault <fangebault@…>
10021	Rendering of URI samples	wiki system	0.12-stable	unscheduled	defect	minor		new	2011-02-10T20:54:37+01:00	2011-11-01T19:47:51+01:00	"While trying to document a sample SIP URI I found I could not simply italic the variable part of the URI.  On further experimentation I found this seams to affect any scheme:hier-part URIs.  The obvious escaping of the scheme tag did no resolve the issue.

Examples:
{{{
 * sip:N''access-code''@192.168.0.20
 * !sip:N''access-code''@192.168.0.20
 * mailto:Subscribe-''conference''@192.168.0.10
 * !mailto:Subscribe-''conference''@192.168.0.10
 * ftp://ftp.domain.com/''path''/''file''
 * !ftp://ftp.domain.com/''path''/''file''
}}}
Gives:
 * sip:N''access-code''@192.168.0.20
 * !sip:N''access-code''@192.168.0.20
 * mailto:Subscribe-''conference''@192.168.0.10
 * !mailto:Subscribe-''conference''@192.168.0.10
 * ftp://ftp.domain.com/''path''/''file''
 * !ftp://ftp.domain.com/''path''/''file''

Work-around: Use the monospace markup to avoid the processing of the scheme, example:
{{{
 * `sip:N`''access-code''`@192.168.0.20`
 * `mailto:Subscribe-`''conference''`@192.168.0.10`
 * `ftp://ftp.domain.com/`''path''`/`''file''
}}}
Gives:
 * `sip:N`''access-code''`@192.168.0.20`
 * `mailto:Subscribe-`''conference''`@192.168.0.10`
 * `ftp://ftp.domain.com/`''path''`/`''file''"	mpotter@…
615	Change default wiki syntax	wiki system	0.7.1	unscheduled	enhancement	normal		new	2004-07-12T16:21:11+02:00	2015-06-09T14:06:49+02:00	"The wiki supports several different formats like restructured text and html.

It would be nice if it would be possible to change the default syntax that is
used in the wiki. So that you could for example use restructured text without the `{{{ }}}` blocks.

"	toni
12984	Incorrect placement of line breaks inside HTML <pre> tags	wiki system			defect	trivial		new	2018-02-25T15:36:51+01:00	2022-05-09T08:47:47+02:00	"Hello,
We're using Trac 1.2.2.

When entering on a Wiki page:

{{{
#!sh
# Running a jar
java [Java options] -jar josm-tested.jar [Program arguments]

# Launch a Web Start
javaws [run-options] -J[Java option] josm.jnlp
}}}

The resulting HTML code is:
{{{
<div class=""wiki-code""><div class=""code""><pre><span class=""c1""># Running a jar
</span>java <span class=""o"">[</span>Java options<span class=""o"">]</span> -jar josm-tested.jar <span class=""o"">[</span>Program arguments<span class=""o"">]</span>

<span class=""c1""># Launch a Web Start
</span>javaws <span class=""o"">[</span>run-options<span class=""o"">]</span> -J<span class=""o"">[</span>Java option<span class=""o"">]</span> josm.jnlp
</pre></div></div>
}}}

This causes a problem when we try to display this HTML code with Swing (https://josm.openstreetmap.de/ticket/15998) probably because the line break is inside the <span> instead of being right after it.

I think the correct HTML code should be:
{{{
<div class=""wiki-code""><div class=""code""><pre><span class=""c1""># Running a jar</span>
java <span class=""o"">[</span>Java options<span class=""o"">]</span> -jar josm-tested.jar <span class=""o"">[</span>Program arguments<span class=""o"">]</span>

<span class=""c1""># Launch a Web Start</span>
javaws <span class=""o"">[</span>run-options<span class=""o"">]</span> -J<span class=""o"">[</span>Java option<span class=""o"">]</span> josm.jnlp
</pre></div></div>
}}}"	vincent.privat@…
1465	Trac could use a distributed VCS storage	wiki system	0.8.1	next-major-releases	enhancement	critical		new	2005-04-22T11:18:37+02:00	2015-05-26T20:50:57+02:00	"hi!

a friend and i are running a small publishing house, and are collaborating with trac and instant messaging - kudos to you, because it does just about all we need!

here's what trac doesn't do very well: we both use laptop computers, and are travelling quite often. in order to work on shared documents, we need to be online constantly, as conventiently most of our shared documents are in wiki format by now. it's not always possible to guarantee internet connetcivity, though...

i realise that subversion is not the ideal repository format for our needs, we really need something like monotone that works well with local repositories that can be merged with a central repository or updated from there. still, writing a whole set of tools such as trac offers on top of monotone would be quite tedious.

so, in a roundabout way what i'm asking is whether it would be possible to run trac in a 'local' mode where it reads the subversion repository information from a local copy _only_ (with limited history/changeset functionality, of course). in addition, trac should store all wiki, ticket and other data in a filesystem structure instead of a db that can also be manages via a seperate or the same subversion repository.

a ""commit now"" or ""i'm online, try to merge with the central repository"" button or something similar might be all that's left to make trac the ultimate in collaboration tools.

now being a developer myself in my day job, i realize that this could be a HUGE feature. depends on your architecture, and even if it lends itself to implement something like that, HUGE just reduces to LARGE.

still, i'd like to see it :)
"	jens@…
976	Wiki Page redirects to other Wiki pages and possibly other Trac resources	wiki system	0.11.2	next-major-releases	enhancement	minor		new	2004-11-21T12:28:33+01:00	2015-11-30T22:31:39+01:00	"There should be a way to redirect from a wiki page to another Wiki page. A ![[Redirect(target)]] macro could do that.
The `target` could actually be any Trac resource, if specified by a TracLink.

That could be handy in several situations:
 - singular/plural form of WikiPageNames: TracLink redirecting to TracLinks
 - direct alias to a source file: ChangeLog redirecting to source:/trunk/ChangeLog
 - direct alias to a ticket: TooManyDatabaseLocks redirecting to #3446

It could be useful to implement this in Trac core instead of a plugin so that one provide a generic way to detect that one was redirected, and eventually provide a ''Edit'' button that would 
trigger the edition of the originally requested page (the one
containing the ![[Redirect]] macro or the #redirect directive, 
or whatever is chosen to implement it...)


"	Christian Boos
6947	Change in colouring scheme for nested replies in the ticket	wiki system		next-major-releases	enhancement	minor		new	2008-03-06T12:00:14+01:00	2015-05-26T20:50:57+02:00	"Currently, when another reply to the ticket's description or comment is added, colours of the reply levels are ""shifted"" - thus, for example, the original post is marked with different colours in each reply. I think that colours for particular level should be preserver, and just another colour should be introduced ""on the left"" (currently new colour appears ""on the right"").

That would make finding the same sentences in different replies much easier (user will just search for the same colour)."	Przemyslaw Lapko <przemyslaw.lapko@…>
7361	"Error in Wiki Rendering if Colon "":"" is used with a word and quote mark"	wiki system	0.11rc2	next-major-releases	defect	minor		new	2008-06-20T03:02:43+02:00	2015-05-26T20:50:57+02:00	"I have found the following Wiki rendering issue.  Seems like if a word has a colon at the end followed by quote mark then the style marks are not interpreted correctly.

Probably best by example:
{{{

'''phrase word testing''' other things.

'''phrase word: testing''' other things.

'''phrase 'word' testing''' other things.

'''phrase 'word:' testing''' other things. (Fault)

'''phrase 'word:two' testing''' other things.

'''phrase 'word two:' testing''' other things. (Fault)

''phrase 'word:' testing'' other things. (Fault)
}}}

which renders as:
{{{
#!div style=""border: 1px solid #ddd; margin: 1em 1.75em; padding: .25em""

'''phrase word testing''' other things.

'''phrase word: testing''' other things.

'''phrase 'word' testing''' other things.

'''phrase 'word:' testing''' other things. (Fault)

'''phrase 'word:two' testing''' other things.

'''phrase 'word two:' testing''' other things. (Fault)

''phrase 'word:' testing'' other things. (Fault)
}}}

This is just frustrating, not a big usability issue.


I hope this is not already known - I did search and have not found a match.  I also hope this is not a valid feature I haven't found yet."	paul@…
9897	'>' cannot be properly escaped	wiki system	0.12dev	next-major-releases	defect	minor		new	2010-12-03T15:01:40+01:00	2015-05-26T20:50:57+02:00	"{{{ >:: greater than\\}}}

will yield

 >:: greater than\\

which is not what I want but:

{{{ !>:: greater than\\}}}

 !>:: greater than\\

obviously isn't right either.

I could write html code to do this as a workaround but this is really something that could be simply fixed by an escape character.  
"	anonymous
1245	Highlight changes of a wiki page since last visit	wiki system	0.8	next-major-releases	enhancement	normal		new	2005-03-03T15:32:14+01:00	2015-03-02T22:31:46+01:00	" 1. It would be very handy to be able to choose the versions we want to see the diff between. A la moinmoinwiki, see [http://moinmoin.wikiwikiweb.de/MoinMoinFeatures?action=info here] for an example.
 2. It would be nice to display the changes of a page since last visit
 3. It would be nice to have a diff mode where only changes are displayed (not the whole page source), with perhaps a preview of the rendered page below the diff.

Just ideas. :)"	kilian.cavalotti@…
1424	MediaWiki-style table syntax support	wiki system	0.8.1	next-major-releases	enhancement	normal		new	2005-04-11T21:29:47+02:00	2014-04-03T11:12:17+02:00	"Just a personal preference, but I really like mediawiki's formatting styles for lists and tables (lists, because they make more sense to me, and tables because they're more powerful than trac's implementation)..   (by tables, I mean the pipe-format, not the html or pseudo-html formats).

http://en.wikipedia.org/wiki/Help:Table#Guide_to_the_pipe_syntax"	xris@…
9055	Auto numbering in wiki tables	wiki system	0.12dev	next-major-releases	enhancement	normal		new	2010-02-12T14:38:04+01:00	2017-04-20T06:05:11+02:00	"It would be useful to have the ability to auto-number table rows.

Something like:
{{{
||= ID =||= Col =||
|| 1. || content of row 1 ||
|| 1. || content of row 2 ||
..
}}}

would result:
||= ID =||= Col =||
|| 1. || content of row 1 ||
|| 2. || content of row 2 ||"	itamarost@…
9216	changeset hook for wiki pages	wiki system		next-major-releases	enhancement	normal		new	2010-04-11T14:54:06+02:00	2015-05-26T20:50:57+02:00	I configured a changeset post-commit hook from SVN to Trac, and now every time I add a new changeset to SVN with a properly formatted comment, Trac automatically adds a message to the corresponding ticket. Would be nice to have the same functionality for wiki pages. When I make a change to some wiki page, and format comment properly, Trac ticket gets a message, automatically. Thanks.	team@…
9296	Wiki autocompletion for TracLinks	wiki system	0.11.4	next-major-releases	enhancement	normal		new	2010-05-05T11:05:54+02:00	2018-03-13T22:18:17+01:00	"I would request wiki autocompletion for TracLinks. So when user writes [ and then starts writing some link target wiki editor should try to suggest completion.

For example, we use a lot hierarchical wiki pages (with /) and it would be great that we could start typing top page and then press tab key to autocomplete to the end of common prefix."	Mitar