Force metadata rendering in older DokuWiki versions

With this change the include plugins forces metadata rendering when it
redirects the user after saving a page to another page because otherwise
th

Force metadata rendering in older DokuWiki versions

With this change the include plugins forces metadata rendering when it
redirects the user after saving a page to another page because otherwise
the metadata is only rendered when the page is displayed directly in
DokuWiki versions older than 2010-11-23. A version check ensures this
code is only executed in older DokuWiki versions.

show more ...

Extend and correct the documentation of the section edit button handler

Add section edit button handling

This commit fixes section edit buttons. Now section edit buttons of
included pages don't interfere with buttons of the parent page anymore
and all section edits of t

Add section edit button handling

This commit fixes section edit buttons. Now section edit buttons of
included pages don't interfere with buttons of the parent page anymore
and all section edits of the included page are closed at the end of the
included page. Furthermore the id and revision of section edit buttons
of included pages are correct so they should actually work. A
redirect_id like in other edit buttons ensures that the user is
redirected to the correct page after the edit.

show more ...

Merge branch 'master' into render_instructions_rewrite

Conflicts:
syntax/meta.php

vim-modelines: Remove no longer allowed enc=utf-8

Restructuring, first version of new cache handling

This commit replaces user dependent include keys by just one cache for
each page. This means the cache needs to be regenerated more often when
e.g.

Restructuring, first version of new cache handling

This commit replaces user dependent include keys by just one cache for
each page. This means the cache needs to be regenerated more often when
e.g. the edit permissions are different. As this is just a renderer
cache this shouldn't be a big problem. The main reason for this is that
the metadata won't be correctly updated when a different cache file is
used for every user.

In the metadata all include instructions are stored so when the cache is
checked the list of pages that actually should be included can be
reconstructed and then compared to the list of pages that has been
included when the page/metadata has been rendered.

The order of the includes and the respective parent pages are taken into
consideration so something like the inclusion of two user-dependent
pages that include each other won't break this cache handling. I'm not
sure if all scenarios are handled by this cache correctly, but I
can't think of a scenario where the page should be rendered but
neither the order nor the parent id nor one of the included pages has
been changed. When one included page is replaced by another one because
of these placeholders all sub-includes of that page will still be
checked but as then the cache will be purged anyway this doesn't matter.

I've decided against just storing one level of include instructions in
the metadata of every page and for storing everything in the root as
reading a lot of files should imho be avoided. The metadata that is read
might be outdated, but outdated metadata can only be a result of a
change in one of the included pages which is handled by the
file dependencies.

show more ...

Set start level of includes to 0

New attempt of a rewrite using instructions during rendering

This patch makes the include plugin no longer do all the work in the
instructions but instead during rendering the instructions of the ch

New attempt of a rewrite using instructions during rendering

This patch makes the include plugin no longer do all the work in the
instructions but instead during rendering the instructions of the child
pages are converted and executed in the renderer of the page itself.
This means all advantages of working at instruction level are preserved,
but tricky caching problems are avoided. This is still not working
completely:

- The cache doesn't work at all, if your metadata is fresh the renderer
cache won't be used at all
- No tests have been done if ACL support is actually working (but it
should)
- Problems with the box plugin that have been fixed might reappear
- The support for different levels hasn't been tested that thoroughly
- The blog plugin will be broken with this version, perhaps
compatibility fixes will be added again later
- The metadata cache isn't refreshed when it should, at least in the
current git version of DokuWiki

show more ...

added some debug logic

only use plugin.info.txt

added missing resolve_pageid() call

cleanID() prior to acl checks

don't close open sections in some cases (box plugin)

removed weird (wrong?) ID check

switched to new plugin.info.txt layout

me vs. include - a new beginning

please kill me

another attempt to fix the metadata issue

hopefully fixed caching related ACL issues

hopefully fixed all ACL dependant caching issues

added VERSION file to cache depends for nicer upgrades

resolve relative page ids correctly using the correct scope

apply macros in cache handler

fixed cache key generation for all possible ACL modes

release preparations

darcs-hash:20090511194151-23886-4be0acba725c52de54bc7413982cdb97c9b23c4f.gz