> > However if this was really that important, we could add a plugin hook
> > from within edit/, which signalised page creation to a few plugins(?)
>
> This does not work nearly as well, one of the significant benefits is to
> have the auth main auth call authenticate for creation.
Great! Why didn't you say that earlier?! ;)
I think this was a very nice feature to have, but we shouldn't
pollute the global plugin scope with it. Eventually it was the
best solution to make the ewiki_auth() call change "edit" into
"create" (only internally for the auth plugin stack) by adding
one of the possible detection strategies.
This way the main plugins still would only pass "edit" around,
but the auth plugins would see "create" if so.
If we could not add this in ewiki_auth(), then probably inside
of edit/, by slightly modifying the _auth call? Sounds too simple
to not to do it.
> >
> > I've recently had the idea of a PageTemplateList plugin (aedit), where
> > it doesn't look like much overhead of not having a special "create"
> > action. - The check for {version} currently seems to do the trick.
>
> That's a great plugin that I probably will use, but the plugin I was
> considering was a search-based plugin to prevent people from creating new
> pages that duplicate existing pages.
The template thing is in CVS.
Your idea was about a content-duplication-prevention plugin? I'm not
sure if the SEARCH call would help here, sounds difficult. But also
sometimes it is necessary to move content from one page to another,
so temporarily parts of a page are dublettes in a Wiki.
mario