Age | Commit message (Collapse) | Author |
|
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.
|
|
feeds if available. (rss doesn't allow such info on a per-post basis)
* meta: Allow copyright/license metadata to contain arbitrary markup.
|
|
|
|
directives.
* aggregate: Yet another state saving fix (sigh).
* aggregate: Add hack to support feeds with invalidly escaped html entities.
|
|
and 'p/'.
|
|
|
|
returned (and not run in some cases) rather than the plugins directly
forcing a user to log in.
* opendiscussion: allow editing of the toplevel discussion page,
and, indirectly, allow creating new discussion pages.
|
|
|
|
user goes back from the signin screen and does something else.
* Improve behavior when trying to sign in with no cookies.
|
|
* table: Fix dependency tracking for external data files. Closes: #458387
|
|
matter, but after recent changes, state is not always loaded, and saving
would kill it.
|
|
|
|
* decode_form_utf8 only fixed the utf-8 encoding for fields that were
registered at the time it was called, which was before the
formbuilder_setup hook. Fields added by the hook didn't get decoded.
But it can't be put after the hook either, since plugins using the hook
need to be able to use form values. To fix this dilemma, it's been changed
to a decode_cgi_utf8, which is called on the cgi query object, before the
form is set up, and decodes *all* cgi parameters.
|
|
* Retry dropping uid and gid, possibly this will help with the "Resource
temporarily unavailable" failures I've experienced under xen.
|
|
|
|
the needsbuild hook. This resulted in feeds not being removed when pages
were updated, and probably other bugs.
* aggregate: Avoid uninitialised value warning when removing a feed that
has an expired guid.
|
|
in a subdirectory. Patch by Larry Clapp.
|
|
that match only the page using the directive, adding 'included()'
and supporting negated pagespecs and added whitespace.
|
|
|
|
|
|
|
|
|
|
|
|
sets the taint flag on untainted variables, by disabling taint checking
in the deb. This sucks.
|
|
|
|
by default.
|
|
|
|
contain multiple copies of the same link)
|
|
* map: Don't inline images.
|
|
links required meta to be run during scan, which complicated its data
storage, since it had to clear data stored during the scan pass to avoid
duplicating it during the normal preprocessing pass.
* If you used "meta link", you should switch to either "meta openid" (for
openid delegations), or tags (for internal, invisible links). I assume
that nobody really used "meta link" for external, non-openid links, since
the htmlscrubber ate those. (Tell me differently and I'll consider bringing
back that support.)
* meta: Improved data storage.
* meta: Drop the hackish filter hook that was used to clear
stored data before preprocessing, this hack was ugly, and broken (cf:
liw's disappearing openids).
* aggregate: Convert filter hook to a needsbuild hook.
|
|
creating a new page that's entirely empty.
|
|
|
|
|
|
inserting them into the html template. This ensures that markdown
acts on them, even if the value is expanded inside a block-level html
element in the html template. Closes: #454058
* Use a div in the note template rather than a span.
|
|
|
|
cached value.
* Preserve input file modification times in output files.
|
|
|
|
so that more than one plugin can use this hook.
I believe this is a safe change, since only passwordauth uses this hook.
(If some other plugin already used it, it would have broken passwordauth!)
|