| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Some browsers interpret about: URIs like a limited version of data:
URIs. In particular, some versions of Internet Explorer interpret
arbitrary HTML content in about: URIs.
|
|
|
|
|
|
* Add htmlscrubber test suite.
|
|
Conflicts:
debian/changelog
templates/change.tmpl
|
|
|
|
|
|
|
|
There are several cases (recentchanges files, aggregated files)
where some source files are not in revision control.
|
|
|
|
|
|
used if you want a wiki that doesn't default to generating rss or atom
feeds, but that does allow them to be turned on for specific blogs.
|
|
just avoid actually writing the files. This is necessary because ikiwiki
saves state after a preview (in case it actually *did* write files),
and if will_render isn't called its security checks will get upset
when the page is saved. Thanks to Edward Betts for his help tracking this
tricky bug down.
|
|
- On commits, replace "mtn sync" bidirectional with "mtn push" single
direction. No need to pull changes when doing a commit. mtn sync
is still called in rcs_update.
- Support for viewing differences via patches using viewmtn.
|
|
Now aggregation will not lock the wiki. Any changes made during aggregaton are
merged in with the changed state accumulated while aggregating. A separate
lock file prevents multiple concurrent aggregators. Garbage collection
of orphaned guids is much improved. loadstate() is only called once
per process, so tricky support for reloading wiki state is not needed.
(Tested fairly thuroughly.)
|
|
they're in has changed.
|
|
by thunking to the CGI, which can redirect to the page, or allow it to be
created if it doesn't exist.
|
|
approach.
|
|
Oops. Convert it from a cgi to a sessioncgi hook, which will work
much better.
|
|
* This allows locking the wiki before loading state, which avoids some
tricky locking code when saving a web edit.
|
|
the aggregating page to be rebuilt. Fix this.
|
|
since this leads to too many problems with web caching, especially with
inlined pages. Properly solving this would involve tracking every page
that contributes to a page's content and using the youngest of them all,
as well as special cases for things like the version plugin, and it's just
too complex to do.
|
|
|
|
|
|
|
|
|
|
misc fixes
|
|
license, and copyright. This can be used to create custom RecentChanges.
* meta: To support the pagespec functions, metadata about pages has to be
retained as pagestate.
* Fix encoding bug when pagestate values contained spaces.
|
|
This makes it a lot quicker to deal with lots of recentchanges pages
appearing and disappearing. It avoids needing to clutter up pagespecs with
exclusions for those pages, by making normal pagespecs not match them.
|
|
|
|
the svnrepo and notify settings, though both will be ignored if left in
setup files.
|
|
|
|
function.
|
|
set for the first and last inlined page. Useful for templates that build
tables and the like.
|
|
Add a prefix_directives option to the setup file to turn this syntax
on; currently defaults to false, for backward compatibility. Support
optional '!' prefix even with prefix_directives off, and use that in
the underlay to support either setting of prefix_directives. Add NEWS
entry with migration information.
|
|
|
|
Add missing debian/changelog entry for previous commit
37b4fadcee4e500a1ac68ce9fcd8d6d942628cf6, "Add trailing comma to
commented-out umask in sample ikiwiki.setup".
|
|
the code, since that process can change internal state as needed, and
it will automatically be cleaned up for the parent process, which proceeds
to render the changes.
|
|
|
|
|
|
--bare. Change ikiwiki-makerepo to use a method that should work with
those older versions too.
|
|
|
|
|
|
|
|
|
|
remove the enclosing paragraph and newline markdown wraps it in.
This allows removing several hacks around this markdown behavior from
other plugins that htmlize fragements of pages.
|
|
* template: Htmlize template variables, but also provide a raw version
via `<TMPL_VAR raw_variable>`.
|
|
|
|
meta link.
* Fix support for the case where metadata appears after an inline directive.
This was broken in version 2.16.
|
