Hi,Thanks for the detailed reply. I think the tie to file system data may be the problem I'm hitting against, as ideally I would also have been able to have these plugins stick things in the site index, have pages listed in the ACL manager etc, which appears to be populated by a simple walk of the data directory.
I guess the overheads in giving events on all filesystem interactions would be huge (e.g. allowing the plugin to emulate the existence of a a file), and that approach would only make sense if those emulated files were all read-only.
I.e. by jumping in at DOKUWIKI_STARTED and changing the action and 'exists' flag? Would there be any issues later if the action had changed 'exists' to true when the data file didn't actually exist?You're underestimating the power of action plugins. There is nothing to stop an action plugin inspecting the original query string and displaying content (per acls & via dokuwiki parsert) based on that query string.
Yes, but if the page was being treated as a standard page in almost all respects (just content coming from a script rather than a file), wouldn't the plugin work as per normal?- Parts of the script output could be directed through the standard parser allowing use of things like the discussion plugin on the virtual page.Can do this too. Not sure about the discussion plugin bit, its pretty complex and a plugin - that means the responsibility is on the plugin maintainer not DokuWiki. I don't see that having a new plugin type would make that any easier.
Thanks again, just still struggling to see how I can achieve what I'd like. Pete -- DokuWiki mailing list - more info at http://www.dokuwiki.org/mailinglist