This is a static dump of issues in the old "Flyspray" bugtracker for DokuWiki. Bugs and feature requests
are now tracked at the issue tracker at Github.
Not a bug
FS#670 Don't use caching when going back to current version
I've written the ditaa-Plugin, that generates a flowchart from ascii-art. Now, this plugin creates a normal .png-file for a localmedia-link.
When going to an older version of the page, the page is regenerated and the old flowchart is displayed.
Now, when I try to return to the current version of the page, this page doesn't seem to be regenerated, because it still displays the old flowchart. So it seems, that dokuwiki doesn't call the plugin again when returning to the current version.
I think, this needs some fixing.
It's me again. I've created this task before registering.. ;-)
Now I'm registered.
Hmm this looks like a design problem of the plugin. Old revisions are not cached so going back to an old revision will call your plugin and the image is recreated. The current revision _is_ cached so your plugin isn't called again.
The simplest way to fix this is to use an imagename which is dependent on the input. Eg. use the MD5 sum of the input data. This means a new image is created for each changed input which coulld be too much for you.
Another way could be to build your own image handler which creates the image on the fly with caching only the most recent version. You then would call it from the src attribute of the image tag. The tricky part would be to give it the needed input data. You could either give it base64 encoded as get parameter or maybe the handler could extract it from the page it self.
Another very simple method would be checking if the global $REV parameter is set (indicating an old revision) and not to (re)generate the image in this case. This could mean the images do not match the old text.