phpwiki-talk

[Phpwiki-talk] Best source for PhpWiki documentation (e.g., admin)?

[gpetty <gp...@ao...>]

I've just installed PhpWiki on my Linux computer, and I'm finding it
difficult to track down really clear and comprehensive documentation on its
use and administration.  In particular, I've read the comments in the config
file and still don't understand exactly how to set up user administration,
edit and view permissions the way I want them.  Is there a set of examples
posted somewhere showing different common configurations?

In particular, I'd ideally like to be able to do the following:

1) Require e-mail registration for all users who wish to edit and/or have
the ability to manually add users/passwords.
2) If possible, make certain sub-hierarchies viewable only by users coming
from a particular domain.

I'm not terribly knowledgeable about php, databases, or wiki implementation,
so I'd prefer solutions that don't require hacking.



-- 
View this message in context: http://www.nabble.com/Best-source-for-PhpWiki-documentation-%28e.g.%2C-admin%29--tf1862796.html#a5088542
Sent from the phpwiki-talk forum at Nabble.com.

Re: [Phpwiki-talk] Best source for PhpWiki documentation (e.g., admin)?

[Reini U. <ru...@x-...>]

gpetty schrieb:
> 
> I've just installed PhpWiki on my Linux computer, and I'm finding it
> difficult to track down really clear and comprehensive documentation on its
> use and administration.  In particular, I've read the comments in the config
> file and still don't understand exactly how to set up user administration,
> edit and view permissions the way I want them.  Is there a set of examples
> posted somewhere showing different common configurations?
> 
> In particular, I'd ideally like to be able to do the following:
> 
> 1) Require e-mail registration for all users who wish to edit 

we dont have that feature yet.

> have the ability to manually add users/passwords.

that's easily done with most external auth methods.

> 2) If possible, make certain sub-hierarchies viewable only by users coming
> from a particular domain.

hmm, not easily possible.

> I'm not terribly knowledgeable about php, databases, or wiki implementation,
> so I'd prefer solutions that don't require hacking.

sorry, for these features you'll have to hack a little bit.

-- 
Reini Urban
http://phpwiki.org/  http://murbreak.at/
http://helsinki.at/  http://spacemovie.mur.at/

Re: [Phpwiki-talk] Best source for PhpWiki documentation (e.g., admin)?

[Oliver B. <li...@gm...>]

Reini Urban wrote:

[...]

> > have the ability to manually add users/passwords.
> 
> that's easily done with most external auth methods.

define "easily". Which amount of knowledge is needed, and which kind 
of access to the hosting server?

IMO, a web based user administration would be "easy".

That's one of the reasons why I strongly consider to use DokuWiki in 
the future. Self registering (confirmation by mail), web based user 
administration, ACLs are all implemented.

I'm only too busy to test it thoroughly for missing features and 
weaknesses.

Oliver
-- 
Oliver Betz, Muenchen

Re: [Phpwiki-talk] Best source for PhpWiki documentation (e.g., admin)?

[Reini U. <ru...@x-...>]

Oliver Betz schrieb:
> Reini Urban wrote:
> 
> [...]
> 
>>> have the ability to manually add users/passwords.
>> that's easily done with most external auth methods.
> 
> define "easily". Which amount of knowledge is needed, and which kind 
> of access to the hosting server?

depends on the method you want to use.

maintaining htpasswd files are easy for one, hard for others.
maintaining SQL pref or user/group table entries files are easy for one, 
hard for others.
maintaining LDAP entries are easy for one, hard for others.
...

> IMO, a web based user administration would be "easy".

true. but this is not really a hot topic.

> That's one of the reasons why I strongly consider to use DokuWiki in 
> the future. Self registering (confirmation by mail), web based user 
> administration, ACLs are all implemented.

registration by email will be added to the next major release. it's just 
not that important as ModeratedPage

> I'm only too busy to test it thoroughly for missing features and 
> weaknesses.

DokuWiki is fine. The best is their user-visible stylesheets/templates. 
Ours are too convoluted.
-- 
Reini Urban
http://phpwiki.org/  http://murbreak.at/
http://helsinki.at/  http://spacemovie.mur.at/

Re: [Phpwiki-talk] Best source for PhpWiki documentation (e.g., admin)?

[Oliver B. <li...@gm...>]

Reini Urban wrote:

[easy user/password administration]

> > define "easily". Which amount of knowledge is needed, and which kind
> > of access to the hosting server?
> 
> depends on the method you want to use.
> 
> maintaining htpasswd files are easy for one, hard for others.

Although I don't consider it being "hard", it's at least inconvenient 
to encrypt the password and paste it in the text file. Maybe there 
are better methods.

For my current Wikis it's o.k., but I wouldn't like to do it if I had 
to manage more changes.

> maintaining SQL pref or user/group table entries files are easy for
> one, hard for others.

How are these accessed - PHPMyAdmin? Then it's like above.

> maintaining LDAP entries are easy for one, hard
> for others. ...

Never done.

> > IMO, a web based user administration would be "easy".
> 
> true. but this is not really a hot topic.

You don't know how many (potential) users consider this to be a hot 
topic. Many people don't want to run completely open Wikis because of 
vandalism, SPAM, legal problems etc.

[DokuWiki]
> 
> DokuWiki is fine. The best is their user-visible

nice to hear, thanks!

Oliver
-- 
Oliver Betz, Muenchen

Re: [Phpwiki-talk] Best source for PhpWiki documentation (e.g., admin)?

[Reini U. <ru...@x-...>]

2006/6/29, Oliver Betz <li...@gm...>:
> Reini Urban wrote:
> [easy user/password administration]
> > > define "easily". Which amount of knowledge is needed, and which kind
> > > of access to the hosting server?
> >
> > depends on the method you want to use.
> >
> > maintaining htpasswd files are easy for one, hard for others.
>
> Although I don't consider it being "hard", it's at least inconvenient
> to encrypt the password and paste it in the text file. Maybe there
> are better methods.

there's a binary which does the changes:

D:\apachefriends\xampp\apache\bin>htpasswd
Usage:
        htpasswd [-cmdpsD] passwordfile username
        htpasswd -b[cmdpsD] passwordfile username password

        htpasswd -n[mdps] username
        htpasswd -nb[mdps] username password
 -c  Create a new file.
 -n  Don't update file; display results on stdout.
 -m  Force MD5 encryption of the password (default).
 -d  Force CRYPT encryption of the password.
 -p  Do not encrypt the password (plaintext).
 -s  Force SHA encryption of the password.
 -b  Use the password from the command line rather than prompting for it.
 -D  Delete the specified user.
On Windows, NetWare and TPF systems the '-m' flag is used by default.
On all other systems, the '-p' flag will probably not work.

> For my current Wikis it's o.k., but I wouldn't like to do it if I had
> to manage more changes.
>
> > maintaining SQL pref or user/group table entries files are easy for
> > one, hard for others.
>
> How are these accessed - PHPMyAdmin? Then it's like above.

As you wish. mysql or phpMyAdmin or any other sql shell

> > maintaining LDAP entries are easy for one, hard
> > for others. ...
>
> Never done.
>
> > > IMO, a web based user administration would be "easy".
> >
> > true. but this is not really a hot topic.
>
> You don't know how many (potential) users consider this to be a hot
> topic. Many people don't want to run completely open Wikis because of
> vandalism, SPAM, legal problems etc.
>
> [DokuWiki]
> >
> > DokuWiki is fine. The best is their user-visible
>
> nice to hear, thanks!
>
> Oliver
> --
> Oliver Betz, Muenchen
>
>
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>


-- 
Reini Urban
http://phpwiki.org/              http://murbreak.at/
http://spacemovie.mur.at/   http://helsinki.at/

Re: [Phpwiki-talk] Best source for PhpWiki documentation (e.g., admin)?

[Grant W. P. <gp...@ao...>]

On Thu, 29 Jun 2006, Oliver Betz wrote:

> You don't know how many (potential) users consider this to be a hot
> topic. Many people don't want to run completely open Wikis because of
> vandalism, SPAM, legal problems etc.

This is exactly true for me.  Because I don't have time to learn how to set 
up and use external authorization methods (I'm a professor, not a 
programmer), I'm now strongly considering alternative wikis, such as 
DocuWiki.

Also, although phpwiki seems like a very nice and reasonably powerful 
implementation overall, I have to admit some frustration with the number of 
apparently serious bugs that I've run into in just the first couple days of 
experimenting with the latest version of phpWiki.  I've already mentioned a 
couple of them on this mail list:

1) The upload plugin doesn't work, because it incorrectly saves an uploaded 
file 'test.png' to uploadstest.png rather than uploads/test.png

2) Enabling "captcha" doesn't work for some reason -- the image doesn't 
display -- so it effectively disables edits when enabled.

3) We had to create an alias for apache to use in order for TeX2png to 
work, because it wasn't finding the relative path images/tex

I have not yet tried any other wiki, so I don't know whether I would have 
run into similar kinds of glitches.

Returning to the subject of documentation, it would be nice if there were 
trouble-shooting advice for new installations -- "If this doesn't work, 
then check this", etc.

Also, a set of example config files illustrating different methods (both 
internal and external) of implementing authentication on typical servers, 
along with a brief discussion of their pros and cons, would be extremely 
useful.

________________________________________
Prof. Grant W. Petty
Atmospheric and Oceanic Sciences
1225 W. Dayton Street
University of Wisconsin-Madison
Madison, WI  53706

gp...@ao...
Tel: (608) 263-3265
Fax: (608) 262-0166

Re: [Phpwiki-talk] Best source for PhpWiki documentation (e.g., admin)?

[Oliver B. <li...@gm...>]

Reini Urban wrote:

> > Although I don't consider it being "hard", it's at least
> > inconvenient to encrypt the password and paste it in the text file.
> > Maybe there are better methods.
> 
> there's a binary which does the changes:
> 
> D:\apachefriends\xampp\apache\bin>htpasswd

indeed, thanks for the reminder!

Oliver
-- 
Oliver Betz, Muenchen