| Age | Commit message (Collapse) | Author |
|---|
|
that given link points based on the page doing the linking. Note that this
could make such PageSpecs match different things than before, if you
relied on the old behavior of them only matching the raw link text.
* This required changing the match_* interface, adding a third parameter.
* Allow link() PageSpecs to match relative, as is allowed with globs.a
* Add postform option to inline plugin.
* Add an bug tracker to the softwaresite example.
|
|
|
|
|
|
|
|
|
|
|
|
plugins's support for inserting html link and meta tags. Now such content
is passed through the htmlscrubber like everything else.
* Unfortunatly, that means that some valid uses of those tags are no longer
usable, and special case methods needed to be added for including
stylesheets, and for doing openid delegation. If you use either of these
in your wiki, it will need to be modified. See the meta plugin docs
for details.
|
|
|
|
level, and provide an example.
|
|
|
|
|
|
|
|
|
|
|
|
inside a blockquote, since that makes the > show up as part of the syntax.
|
|
|
|
|
|
|
|
|
|
|
|
inline, already escaped there
|
|
is an actual security hole as it allows insertion of html into the title
element of a page, which is not processed by the htmlscrubber.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
hg.
|
|
|
|
|
|
same time, and let the second person resolve the conflict.
|
|
output the verbose build log to stdout, rather than to the syslog.
|
|
|
|
|
|
with the same name already exists, and generally simplify the edit code.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
