Skip to content

don't disable cache #3

@dr4Ke

Description

@dr4Ke

This will need changes in the dokuwiki core code. I sent an email on the dokuwiki mailing list containing :

II. ISSUE

The cache feature of dokuwiki stores a preparsed version of the page.
As I didn't find a way to store all values in this page, the edit
buttons are inconsistent when using cache.
The issue is that I can't change the way the edit sections values are
stored in the cache. Then, for now, I disable it completely for my
plugin to really work as expected.

I can't think of a way to do what I want without, either :
. disabling cache
. catch the event RENDERER_CONTENT_POSTPROCESS and rewrite comments with useful values
. change dokuwiki code

The first two options are bad as they introduce more processing each
time the page is viewed. The third can be done in two ways :
o implement two new events that could modify the way startSectionEdit
and finishSectionEdit works. The editsections plugin will use these
hooks to rewrite useful values before storing the page in cache.
o implement a standard option into dokuwiki to choose section editing behavior :
. one section, edit button at end of section (current behavior)
. one section, edit button at the beginning of each section
. nested sections, edit button at the beginning of each section

III. QUESTIONS

Is there a way to implement this plugin without touching dokuwiki core ?

If not, which way would be better : new hooks or implementing section
editing behavior in the core ? I can provide patches for one or both
ways.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions