AW: [Phpwiki-talk] phpWiki and postnuke at Daimonin

[Daimonin M. <in...@da...>]

Hm, i thought the postnuke phpwiki port is known?

http://stuff.kling.nu/

I use that module/port. I have not done any code or port for it -
i just use it and fixed 1-2 minor issues.

It seems i missed to explain the (beside security) only
and really only important point: That i can use *one*=20
permission system - the group/permission system of postnuke
to control the wiki.

Its the most important point. I would *never* install a 2nd
permission system using module. I want and i must use the
central permission system of postnuke to control the wiki
user & pages. This phpwiki postnuke port allow just that.

In fact i would even change the cms or write a own small doc
system when i had no choice instead of use the standalone permission
of phpwiki.

Daimonin has gotten around 3500 registered users in 6 weeks, we will =
have=20
soon 10.000 and more. With the many people having access to different
parts...
I described the reason in my first mail. (if i would use a different=20
CMS i would do the same, postnuke is just the cms is use).=20

I had to syncronize some different groups and permission groups which
access different modules & areas of the website (we talk about gallery,
forum, wiki...).
I need to see who has which right in one view. I must be able to change=20
it with one click. And other people with lesser permission in the=20
site should be able to build groups and assign their own people with
permissions.

All what i can say is, that we had bad experience with different modules
having
different permission. Very bad. With the central system, all works like =
a
charm
and it works fast and clean.

Sorry when it sounds like a rant, but its really the important point.

So, as i understand the phpwiki code, the permission system itself is
not that different as the one from postnuke. It should be possible
to relink the permission queries to postnuke and use their loged =
in/logout
system. The postnuke port does exactly that.

And what i can tell is, that if that is done, both system together works
wonderful.

> -----Urspr=FCngliche Nachricht-----
> Von: php...@li...=20
> [mailto:php...@li...] Im Auftrag=20
> von Joel Uckelman
> Gesendet: Mittwoch, 30. M=E4rz 2005 04:59
> An: php...@li...
> Betreff: Re: [Phpwiki-talk] phpWiki and postnuke at Daimonin=20
>=20
> Thus spake "Michael Toennies":
> > Hello
> >=20
> > We are the daimonin mmorpg project:
> > http://www.daimonin.net
> >=20
> > We use phpWiki as our main documentation & information=20
> central of our=20
> > postnuke site. I have to say that we are very happy with=20
> that solution=20
> > and its a great success.
> > Thank you guys!
> >=20
> > The only negative point is, that we can't use the original=20
> phpWiki but=20
> > a modified version which used the postnuke user permission=20
> interface.
> >=20
> > When you look at the site and you understand what we do you=20
> will see=20
> > how incredible useful the permission system is. We give access to=20
> > several parts of the website include site sub-admins, gallery album=20
> > owners, file system upload permission, forum permission, forum=20
> > moderator permission and at last write access to the wiki.
> >=20
> > Thats only (and really only, our old website had it not, so we know=20
> > where we talk about) possible with one central permission and group=20
> > system which gave us the Postnuke CMS.
> >=20
> > As a game (with much underage users), we need a stable & secure=20
> > permission system. A free wiki access is no option. In the=20
> old website=20
> > we had deleting and vandalism of pages every few hours.
> >=20
> > With the new webpage, we had not a single issue.
> >=20
> > When you look at the phpWiki of our site, you will notice=20
> how good it=20
> > fits in the CMS and how useful it is.
> >=20
> > What i fear is, that someone find a exploit in the hacked phpWiki.
> > Its not active in development anymore and it has still issues.
> >=20
> > Has the phpWiki community ever thought about to add a=20
> native postnuke=20
> > interface? Postnuke lakes a native wiki. It has a very easy to use=20
> > interface which allows it to bind in modules. Also, the=20
> changes would=20
> > be normally not so hard - just a redirect to the postnuke=20
> permission=20
> > system. Nearly all other parts from phpWiki fits in fine.
> >=20
> > It would be a win/win solution for both projects. Postnuke=20
> would get a=20
> > stable, tested & working wiki. phpWiki would get a=20
> incredible boost in=20
> > users and, i can ensure it as a open source project leader=20
> for years=20
> > now, alot more developer.
> >=20
> > Both project would gain ALOT for a little work.
> >=20
> > They would stay independed as projects but would gain through the=20
> > Synergy effect of the interface both a big boost.
> >=20
> > Michael Toennies
> > Daimonin MMORPG
>=20
> So, what you're doing is querying postnuke for user=20
> permissions? Is that the extend of your modifications?
>=20
> I haven't looked at our permissions system in a while---maybe=20
> it already is this way---but it would make some sense to have=20
> permissions queries work similarly to the way DB queries do.=20
> That is, have an abstract permissions interface which calls=20
> the appropriate permissions backend. That way, you guys could=20
> write a postnuke permissions backend and there would be no=20
> need for further changes to the code.
>=20
>=20
>=20
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide Read honest &=20
> candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk