RE: [Phpwiki-talk] Ready for 1.3.8 ? Heads up

[electron <ele...@mg...>]

1.3.8 may be a week or less away, however, I doubt one could say 1.4.0 =
is
2-3 weeks away.

Enter the realist(tm):

Before 1.4.0, it is critically important that the only time dbtype is
checked is when wikidb is initialized. This may mean having to add some =
user
based functions to wikidb or moving wiki authentication to a separate =
layer.

Essentially, if I write an extension for wikidb (phADODB, which =
pnPhpWiki
uses to tap into postnuke), by checking elsewhere for dbtype I just lost
functionality!

An installer is useful because the whole point of our userbase is to be =
user
friendly. This includes the admins. You shouldn't need a $40 an hour
consultant to install phpwiki.

Defines suck. Defines are everywhere where they don't need to be. =
Index.php
is hugely bloated, complex and not documented well.

Finally, Documentation, Doc, and Doc!

There is no rush to get to 1.4.0. 1.4.0 should be a complete, pretty, =
easy
to install and easy to administer wiki miniCMS.=20

1.3.8 Should proceed to 1.3.9 and implement a roadmap to 1.4.0.

-Jtp.




> On Mon, Feb 23, 2004 at 09:02:56PM -0600, Dan F wrote:
>>Reini Urban wrote:
>>>Are we ready for the intermediate 1.3.8 release?
>>
>>Let me join malcolmr in saying:
>>1. PhpWiki has great potential.
>>2. Releasing something stable is good.
>>
>>Also, I would really like to use some of the things in 1.3.8, e.g.=20
>>strong user authentication.
>>
>>I know people asking you to release without doing any work can be=20
>>irritating, but you have to take it in the spirit given: you have an=20
>>attentive user base.

The only remaining problem before releasing 1.3.8 is a gettext or=20
update_locale problem for foreign languages.
All other issues (besides running as CGI) has been resolved now.

The strange thing is that on most of my test setups everything works=20
okay, just on PhpWikiDemo it fails sometimes, sometimes it works.
Which lets me assume that it could be a preferences setting.

What is planned for the next releases up to 1.4.0
-------------------------------------------------
Page permissions editable:
   * enable and simplify WikiAdminSetAcl, and probably WikiAdminChmod.
     let the user harden the ACL's of some pages.
     Default: loose permissions as before
Page permissions enforced:
   * check in all actions, plugins and listers for access permissions.
     (listers almost done)
WikiDB:
   * update to the latest ADODB library (but not the session class)
   * switch to FETCH_ROW
   * check for the dirty ADODB mysql hacks
    (INSERT ... SELECT)
   * test SQLite and PHP 5.0.x
Plugins:
   * WikiForum (almost the same as AddComments and WikiBlog)
   * Amazon, Google API's (using SOAP)
   * RateThisPage (user-specific and overall)
More Themes:
   * nuke (a tiny-font three-column theme),
   * crao (buttons as icons which need no translation, and
     more sidebar tricks)
Localization updates:
   * with the new _WikiTranslation and TranslateText features
     hopefully some holes will get filled.
action=3Dupgrade for database upgrades, pgsrc diffs and with =
verification.
   (currently only pgsrc upgrade on missing pages)

I'm not sure the requested installer and WikiAuth split-up into seperate =

files. Seperate UserPreferences classes are more important IMHO.

All this is not too much work. I think of about 2-3 weeks from
1.3.8 to 1.4.0
--=20
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/