[ewiki] Re: ewiki_eventually_initialize()

Hey,

> 1.  If the current EWIKI_INDEX does not exist this plugin runs to 'fix' the
> problem, but cannot.  Because this plugin forces the action to view
> ewiki_page_view() is now running on an empty page.  This bypasses the normal
> empty page check and behaves strangely.

This was already fixed with the last bugfix release?  (R1.01c2)

> 2.  When ewiki_eventually_initialize() runs it can create new pages if you
> have updated EWiki and grabbed new init_pages.  This may or may not be
> acceptable.

It won't happen, unless you have a really really empty FrontPage (the
_PAGE_INDEX). But even this isn't true anymore, if you once created the
FrontPage, the _initialize() function will never activate again (unless
you first delete the FrontPage using one of the database tools).

> How about making ewiki_eventually_initialize() run only in unprotected mode?

I think we should favour making the init function a plugout. A real setup
wizard (just some feedback about active settings) would be cool. PhpWiki
failed greatly on creating one that actually worked, so I delay this, until
there's enough time to do this.

> Mozilla defaulted to saving the files as tar.gz.tar with the old type.

Sounds just like a Mozilla problem; and I'd say it's acceptable in this
case, even because I knewed another browser that has more problems if it
received "application/x-gzip" - unpacking the tarball in that case.
Eventually using "application/x-gtar" instead of "/x-tar" makes Mozilla
behave saner?

> Just an early report that I'm seeing a bug in the new binary hook, I added
> $ewiki_plugins["action_binary"]["info"] = "ewiki_page_info"; to my config
> file and now all actions are allowed to run on the page.  I have to leave

Haven't seen this happen. Have you forgotten to logout (if you were admin
during page flag setting).


mario

Other related posts: