My view on the philosiphy of wiki, is that you are not supposed to control
the users... let versioning handle vandalism problems. Also, I am
considering creating a branching wiki, with moderation and subscription
system. (more below)
That said
(easiest hack... probably not the "right" way)
I would consider adding a field to the edit page that asks for a password.
I would have the password hard coded in the recieving script, and compare
the submited password with the other password, and accept or reject the
changes based on comparing those strings.
To have it switch between everybody editable and su edititable, you could
have a check box field, and if checked, and the password is valid, it
becomes locked, the unchecked and password valid unlocked.
To store locked or unlocked data, you could probably add another field to
the database... or hack somethign togerther with a flat file... or, have a
special string start the wiki page that forces it to be locked. (you can
omit, or set the checkbox with this string) Then... session data...
/security..
You would have to re read the stored file to check to see if it is actually
locked or not, you would not be able to upload the form to the user.. and
have them change the locked keyword that starts the page, and have the lock
check be based on user submited information.
Check out www.faqts.com they have a moderation system... but not
subscription... I'm compiling ideas for it, and am slowly learning
programming to actually do the subscription method.
* (More)
I was considering adding a moderation and subscription system... if a
person wants to control the layout of a page, he could enter a username and
password, then moderate the changes.
Another user would be able to apply a users moderation settings.
I was thinking about having my home page being a wiki, that anybody would be
able to edit, but their edits affect a secondary page... If I approved of
the changes, I would "subscribe" to that persons changes and make it show up
as the home page.
Let everybody change the data as they want, make sure that all voices are
available, have users select their filters and have non filtered versions a
click away.
If you can help me implement this, let me know... I am trying to create my
own "micro wiki" witch will be a versioning flatfile single page to start
with... I haven't figured out how to configure a database yet, and all of
the wikis that I have installed have not had clear references for
prerequisite programs... I'd insert the references myself... but I still
haven't found them.
----- Original Message -----
From: "Rick Parker" <ri...@wi...>
To: <php...@li...>
Sent: Saturday, June 29, 2002 8:32 PM
Subject: [Phpwiki-talk] users
> How do I control the users?
>
> I would like to have certain people maintaining their own pages, but
> others only get "read" and admin is of course "all-powerful".
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> No, I will not fix your computer.
> http://thinkgeek.com/sf
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>
|
