phpwiki-talk

Re: [Phpwiki-talk] PhpWiki Administration Problems

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

Ian Meginnis schrieb:
> I recently installed PhpWiki to my website server, which is hosted by
> hytech hosting, but I am unable to administrate/setup the wiki.  When
> I go the phpwiki/admin.php file, I get a dialog box asking for a
> username and password.  I created a default administrator username and
> password when I initially installed the wiki, but these do not work
> when I user them to login.  I have uninstalled and reinstalled the
> files multiple times, but I receive the same message each time: "You
> entered an invalid login or password".
> 
> Is there another way that I can login to administrate the wiki or
> create the administrator username and password again?

[phpwiki-1.2.x]

edit the file admin.php and enter a private username password 
combination there.

also edit lib/config.php for your database setup if you want to.


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

Re: [Phpwiki-talk] PhpWiki Administration Problems

[Ian M. <ian...@gm...>]

I have looked in the wiki folder for a folder named config, but I
can't find it.  I have also looked in the other folders for a file
named config.ini, but I can't seem to find that either.  In my phpwiki
folder, there are these folders: admin, images, lib, locale, pgsrc,
README_FILES, schemas, templates.  There are also these files:
admin.php, fantversion.php, index.php.

I have uninstalled and reinstalled the files to the server multiple
times so I don't know what the problem is.

I would appreciate more help.  Thanks.

-Ian

On 6/30/06, William Leader <le...@k2...> wrote:
> Ian,
>
> If you can upload and download files on the web server you should be
> able to download the config.ini file in wiki/config/config.ini. The
> administrator username and password is set in this file. Make your
> changes and save it back to the server and you should be ready to go.
>
> -Will
>
> Ian Meginnis wrote:
> > Is there another way that I can login to administrate the wiki or
> > create the administrator username and password again?
> >
> > Thanks for the help.
> >
> >
> >
>
>
> 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
>

Re: [Phpwiki-talk] PhpWiki Administration Problems

[William L. <le...@k2...>]

Ian,

If you can upload and download files on the web server you should be 
able to download the config.ini file in wiki/config/config.ini. The 
administrator username and password is set in this file. Make your 
changes and save it back to the server and you should be ready to go.

-Will

Ian Meginnis wrote:
> Is there another way that I can login to administrate the wiki or
> create the administrator username and password again?
>
> Thanks for the help.
>
>
>   

[Phpwiki-talk] PhpWiki Administration Problems

[Ian M. <ian...@gm...>]

I recently installed PhpWiki to my website server, which is hosted by
hytech hosting, but I am unable to administrate/setup the wiki.  When
I go the phpwiki/admin.php file, I get a dialog box asking for a
username and password.  I created a default administrator username and
password when I initially installed the wiki, but these do not work
when I user them to login.  I have uninstalled and reinstalled the
files multiple times, but I receive the same message each time: "You
entered an invalid login or password".

Is there another way that I can login to administrate the wiki or
create the administrator username and password again?

Thanks for the help.

Re: [Phpwiki-talk] Configuring LDAP to connect to Active Directory

[William L. <le...@k2...>]

After lots more digging, here is where I am at. The code is calling the 
_PassUser constructor. Inside the constructor, right around line 880 or 
so there is the block of code that only runs when USER_AUTH_POLICY = 
first-only

$class = $this->nextClass();
return new $class($UserName,$this->_prefs);

Whats interesting is that if we follow the code back up and examine the 
result, it is a _PassUser, but a   _LDAPPassUser was expected. So I got 
to thinking that something must not be right with the line:

return new $class($UserName,$this->_prefs);

That runs when Auth Policy is first-only, and but there is different 
code that runs when USER_AUTH_POLICY = old, which should behave the same 
way as long as USER_AUTH_ORDER = "LDAP" right? So one quick change to 
the config.ini and I can now log in. My guess is that the code that runs 
for the old Auth Policy explcitly calls _LDAPPassUser's constructor.

So return new $class($UserName,$this->_prefs); does not behave the same 
as return new _LDAPPassUser($UserName,$this->_prefs);

things still weren't quite right. I had to adjust around a few more 
seeming unrelated settings before things were completely working the way 
I want them to. After some review of my config.ini here are the values 
that needed to be changed to make it work:

USER_AUTH_ORDER = "LDAP"
USER_AUTH_POLICY = old
CATEGORY_GROUP_PAGE = "CategoryGroup"
;not sure if CATEGORY_GROUP_PAGE was really needed.
LDAP_AUTH_HOST = "ldap://127.0.0.1:389"
LDAP_BASE_DN = "DC=PDI,DC=com"
LDAP_SET_OPTION = "LDAP_OPT_PROTOCOL_VERSION=3:LDAP_OPT_REFERRALS=0"
LDAP_AUTH_USER = "CN=ldapclient,CN=Users,DC=PDI,DC=com"
LDAP_AUTH_PASSWORD = secret
LDAP_SEARCH_FIELD = sAMAccountName
LDAP_OU_USERS = "OU=Users"
LDAP_OU_GROUP = "OU=Users"
AUTH_SESS_USER = "userid"
AUTH_SESS_LEVEL = 2

Some observations:
I had tried setting ENABLE_PAGEPERM on, but this doesn't appear to work 
yet with LDAP. The comments mention something about  a gidnumber, but it 
seems silly for me to have to add some attribute like that. When an 
Active Directory Group has a Members attribute with a list of members in 
it. If I can find the time to do it, I may try to hack up GroupLdap's 
Membership functions to do things the active directory way, It depends 
on how much free time I have.
 
Active Directory appears to be case sensitive on the LDAP stuff. I had 
to make all the DC, OU, CN, etc, uppercase before the connections to 
LDAP would work. I'm not 100% sure this is true, can anyone who knows 
more about AD and LDAP confirm this?

Currently any account in the Active Directory can log in. This isn't 
what I want, but it will have to do for now. Since the Group code isn't 
working, its probably related to that. If anyone has gotten their php 
wiki setup so that only members of a certain group can login, I would 
like to hear from them.

-Will

William Leader wrote:
> I have been able to make further progress by changing these two settings:
>
> LDAP_BASE_DN = "DC=PDI,DC=com"
> LDAP_AUTH_USER = "CN=ldapclient,CN=Users,DC=PDI,DC=com"
>
> Now when I try to log in as any user that is in the active directory I get:
> USER_AUTH_ORDER: => LDAP => Forbidden,
>
> But if I use anything that doesn't exist in the active directory I get:
> USER_AUTH_ORDER: => LDAP (nosuchuser) => Forbidden,
>
> So at the very least I do know that it is connecting and properly 
> checking if the users exist. However I am still not able to log in with 
> a valid user name and password
>   

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

Re: [Phpwiki-talk] [Fwd: SourceForge.net Support: Project database service load from project: phpwiki]

[jean-nicolas G. <jng...@gm...>]

2006/6/29, Reini Urban <ru...@x-...>:
> 2006/6/29, Jean-Nicolas GEREONE <jea...@st...>:
> >
> > > Unfortunately David had no time to investigate this further, no logs.
> > >
> > > I re-enabled now the main wiki and the demo wiki with default
> > > dba - db4, and will check it during the day.
> > > Maybe the new ajax (Wikiwyg) editor went crazy?
> > >
> > >
> > Really ?
> >
> > However there is just one server call to switch from Wikitext mode to
> > Wysiwyg mode.
> >
> > The conversion is done by the file "lib/WikiToHtml.php" and the function
> > is just :
> >
> > require_once("lib/BlockParser.php");
> > $xmlcontent = TransformText($this->_wikitext, 2.0,
> > $this->_request->getArg('pagename'));
> > $this->_html = $xmlcontent->AsXML();
> >
> > Do you think it could be a problem ?
>
> This not, but maybe some loop in a constant interaction between the two.
> Or some xml-rpc loop with the othe ajax code.
> Or their proxy went crazy again.
>
> I'm a little bit suspicious of your changes because it only started
> last weekend.
> but we'll see.
>

Ok, I will try to focus on this.

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

[Phpwiki-talk] authentication doesn't persist

[Antonio B. <an...@ve...>]

Hi, I'm having problems with authentication in phpwiki 1.3.12p2: and also
with the CVS versione at the moment I'm writing.
Navigation works, but authentication does not persist: on the first
request after a successfull authentication, all goes well and the user is
signed and authenticated. But on the following requests I am only signed
but not authenticated (even for ADMIN_USER).

I had a look at the client cookie named PhpWiki_WIKI_ID and I'm wondering
why it expires immediately instead of expiring at quit time or after a
while. I know there is:

COOKIE_EXPIRATION_DAYS = 365

into config.ini but it doesn't seem to be honored.

thanks a lot for helping

PS:
Some more details about my installation follows, if needed:

I'm using the default config.ini, just a copy of config-dist.ini, except
for the following simple differences:

# diff config.ini config-dist.ini
157c157
< ADMIN_USER = admin
---
> ;ADMIN_USER =
161c161
< ADMIN_PASSWD = "my encrypted password"
---
> ;ADMIN_PASSWD =
322c322
< CACHE_CONTROL = NO_CACHE
---
> CACHE_CONTROL = LOOSE
378c378
< DATABASE_TYPE = SQL
---
> DATABASE_TYPE = dba
406c406
< DATABASE_DSN = "mysql://www:mydbpwd\1@unix(/tmp/mysql.sock)/phpwiki_CVS"
---
> DATABASE_DSN = "mysql://guest@unix(/var/lib/mysql/mysql.sock)/test"

I have apache-2.2.2, Php 5.1.4 and MySQL 5.0.22. Here is what I changed
into php.ini:

# diff php.ini php.ini-recommended
314c314
< memory_limit = 16M      ; Maximum amount of memory a script may consume
(8MB)
---
> memory_limit = 8M      ; Maximum amount of memory a script may consume
(8MB)
579c579
< upload_tmp_dir = /tmp
---
> ;upload_tmp_dir =
949c949
< session.save_path = "/tmp"
---
> ;session.save_path = "/tmp"

I've also uncommented this into index.php:

//   define('VIRTUAL_PATH', $_SERVER['SCRIPT_NAME']);

because otherwise I only get blank pages.

Re: [Phpwiki-talk] [Fwd: SourceForge.net Support: Project database service load from project: phpwiki]

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

2006/6/29, Jean-Nicolas GEREONE <jea...@st...>:
>
> > Unfortunately David had no time to investigate this further, no logs.
> >
> > I re-enabled now the main wiki and the demo wiki with default
> > dba - db4, and will check it during the day.
> > Maybe the new ajax (Wikiwyg) editor went crazy?
> >
> >
> Really ?
>
> However there is just one server call to switch from Wikitext mode to
> Wysiwyg mode.
>
> The conversion is done by the file "lib/WikiToHtml.php" and the function
> is just :
>
> require_once("lib/BlockParser.php");
> $xmlcontent = TransformText($this->_wikitext, 2.0,
> $this->_request->getArg('pagename'));
> $this->_html = $xmlcontent->AsXML();
>
> Do you think it could be a problem ?

This not, but maybe some loop in a constant interaction between the two.
Or some xml-rpc loop with the othe ajax code.
Or their proxy went crazy again.

I'm a little bit suspicious of your changes because it only started
last weekend.
but we'll see.

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] Configuring LDAP to connect to Active Directory

[William L. <le...@k2...>]

I have been able to make further progress by changing these two settings:

LDAP_BASE_DN = "DC=PDI,DC=com"
LDAP_AUTH_USER = "CN=ldapclient,CN=Users,DC=PDI,DC=com"

Now when I try to log in as any user that is in the active directory I get:
USER_AUTH_ORDER: => LDAP => Forbidden,

But if I use anything that doesn't exist in the active directory I get:
USER_AUTH_ORDER: => LDAP (nosuchuser) => Forbidden,

So at the very least I do know that it is connecting and properly 
checking if the users exist. However I am still not able to log in with 
a valid user name and password

William Leader wrote:
> I have been able to make some progress on the problem. I started by 
> reverting the config.ini file and configuring it again. This time is was 
> able to get a Call to undefined function: ldap_connect() in LDAP.php 
> line 16. This is good because it never did that before so. It seems that 
> I was missing something in my config.ini to start with. So to get past 
> this problem, I had to uncomment extension=php_ldap.dll in my php.ini. 
> So now it seems that it is really trying to use LDAP, but I am still not 
> completely there. With the debug set to 65 in config.ini, I can now get 
> something like this when logging in:
>
> DEBUG: ALLOW_ANON_EDIT = false, ALLOW_BOGO_LOGIN = false, 
> ALLOW_USER_PASSWORDS = true, ENABLE_PAGEPERM = true, USER_AUTH_ORDER: => 
> LDAP (nosuchuser) => Forbidden, USER_AUTH_POLICY: first-only, 
> PASSWORD_LENGTH_MINIMUM: 0
>
> Correct me if I am wrong, but that tells me that the LDAP code was 
> unable to verify that the supplied user name doesn't exist. I am basing 
> this assumption from the part that reads "USER_AUTH_ORDER: => LDAP 
> (nosuchuser) => Forbidden" meaning LDAP reported that no such user 
> exists, and since LDAP is the only allowed option on my wiki, failing 
> that the only choice remaining was Forbidden user.
>
> Upon double checking the config.ini, I found that the configurator.php 
> script commented out the LDAP settings. I uncommented and changed what I 
> think is correct, based on the hints in the config.ini:
>
> *LDAP_AUTH_HOST = "ldap://12.161.32.40:389"
> ;**12.161.32.40** is the address of the Active Directory server as it is 
> seen from the webserver.
> ;it does run on port 389, because I have been able to configure other 
> programs to connect on that port.
>
> LDAP_BASE_DN = "ou=Users,o=WikiUsers,dc=pdi.com"
> ;I don't know enough about LDAP to know if this is right.
> ;the origional config had o=developement
> ;not being sure what that was I guessed that it is supposed to be the group.
> ;WikiUsers is the group on Active Directory that contains the users that 
> should have access to the wiki.
> ;pdi.com is the name of the domain.
>
> LDAP_SET_OPTION = "LDAP_OPT_PROTOCOL_VERSION=3:LDAP_OPT_REFERRALS=0"
> ;I've heard somewhere active directory needs these, so I just 
> uncommented this line.
>
> LDAP_AUTH_USER = "CN=ldapclient,ou=Users,o=WikiUsers,dc=pdi.com"
> ;I also know that active directory needs a user to log in as to query 
> the directory
> ;ldapclient is a user in my domain created just for that purpose, the 
> rest of the line
> ;was similar to Base_DN so this was also modified in the same way as base_DN
>
> LDAP_AUTH_PASSWORD = secret
> ;the password was changed to match what is in active directory.
>
> LDAP_SEARCH_FIELD = sAMAccountName
> ;i've also heard somewhere that active directory needs this line to 
> search by the old style username (will instead of wi...@pd...)
>
> LDAP_OU_USERS = ou=Users
> LDAP_OU_GROUP = ou=Groups
> ;i don't know what these last two do. so I just uncommented them.
>
> *With all these changes I now get an error when loggin into the wiki:
>
> lib\WikiUser\LDAP.php:28: Warning[2]: ldap_bind() [<a 
> href='function.ldap-bind'>function.ldap-bind</a>]: Unable to bind to 
> server: Invalid credentials
> lib\WikiUser\LDAP.php:37: Warning[512]: Unable to bind LDAP server 
> ldap://12.161.32.40:389 using 
> CN=ldapclient,ou=Users,o=WikiUsers,dc=pdi.com secret
>
> And this is where I am stuck.
>
> -Will
>
> 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
>
>
>   

Re: [Phpwiki-talk] Configuring LDAP to connect to Active Directory

[William L. <le...@k2...>]

I have been able to make some progress on the problem. I started by 
reverting the config.ini file and configuring it again. This time is was 
able to get a Call to undefined function: ldap_connect() in LDAP.php 
line 16. This is good because it never did that before so. It seems that 
I was missing something in my config.ini to start with. So to get past 
this problem, I had to uncomment extension=php_ldap.dll in my php.ini. 
So now it seems that it is really trying to use LDAP, but I am still not 
completely there. With the debug set to 65 in config.ini, I can now get 
something like this when logging in:

DEBUG: ALLOW_ANON_EDIT = false, ALLOW_BOGO_LOGIN = false, 
ALLOW_USER_PASSWORDS = true, ENABLE_PAGEPERM = true, USER_AUTH_ORDER: => 
LDAP (nosuchuser) => Forbidden, USER_AUTH_POLICY: first-only, 
PASSWORD_LENGTH_MINIMUM: 0

Correct me if I am wrong, but that tells me that the LDAP code was 
unable to verify that the supplied user name doesn't exist. I am basing 
this assumption from the part that reads "USER_AUTH_ORDER: => LDAP 
(nosuchuser) => Forbidden" meaning LDAP reported that no such user 
exists, and since LDAP is the only allowed option on my wiki, failing 
that the only choice remaining was Forbidden user.

Upon double checking the config.ini, I found that the configurator.php 
script commented out the LDAP settings. I uncommented and changed what I 
think is correct, based on the hints in the config.ini:

*LDAP_AUTH_HOST = "ldap://12.161.32.40:389"
;**12.161.32.40** is the address of the Active Directory server as it is 
seen from the webserver.
;it does run on port 389, because I have been able to configure other 
programs to connect on that port.

LDAP_BASE_DN = "ou=Users,o=WikiUsers,dc=pdi.com"
;I don't know enough about LDAP to know if this is right.
;the origional config had o=developement
;not being sure what that was I guessed that it is supposed to be the group.
;WikiUsers is the group on Active Directory that contains the users that 
should have access to the wiki.
;pdi.com is the name of the domain.

LDAP_SET_OPTION = "LDAP_OPT_PROTOCOL_VERSION=3:LDAP_OPT_REFERRALS=0"
;I've heard somewhere active directory needs these, so I just 
uncommented this line.

LDAP_AUTH_USER = "CN=ldapclient,ou=Users,o=WikiUsers,dc=pdi.com"
;I also know that active directory needs a user to log in as to query 
the directory
;ldapclient is a user in my domain created just for that purpose, the 
rest of the line
;was similar to Base_DN so this was also modified in the same way as base_DN

LDAP_AUTH_PASSWORD = secret
;the password was changed to match what is in active directory.

LDAP_SEARCH_FIELD = sAMAccountName
;i've also heard somewhere that active directory needs this line to 
search by the old style username (will instead of wi...@pd...)

LDAP_OU_USERS = ou=Users
LDAP_OU_GROUP = ou=Groups
;i don't know what these last two do. so I just uncommented them.

*With all these changes I now get an error when loggin into the wiki:

lib\WikiUser\LDAP.php:28: Warning[2]: ldap_bind() [<a 
href='function.ldap-bind'>function.ldap-bind</a>]: Unable to bind to 
server: Invalid credentials
lib\WikiUser\LDAP.php:37: Warning[512]: Unable to bind LDAP server 
ldap://12.161.32.40:389 using 
CN=ldapclient,ou=Users,o=WikiUsers,dc=pdi.com secret

And this is where I am stuck.

-Will

Re: [Phpwiki-talk] [Fwd: SourceForge.net Support: Project database service load from project: phpwiki]

[jean-nicolas G. <jng...@gm...>]

> Unfortunately David had no time to investigate this further, no logs.
>
> I re-enabled now the main wiki and the demo wiki with default
> dba - db4, and will check it during the day.
> Maybe the new ajax (Wikiwyg) editor went crazy?

Maybe too many users want to test this new feature :D

Re: [Phpwiki-talk] [Fwd: SourceForge.net Support: Project database service load from project: phpwiki]

[Jean-Nicolas G. <jea...@st...>]

> Unfortunately David had no time to investigate this further, no logs.
>
> I re-enabled now the main wiki and the demo wiki with default
> dba - db4, and will check it during the day.
> Maybe the new ajax (Wikiwyg) editor went crazy?
>
>   
Really ?

However there is just one server call to switch from Wikitext mode to 
Wysiwyg mode.

The conversion is done by the file "lib/WikiToHtml.php" and the function 
is just :

require_once("lib/BlockParser.php");
$xmlcontent = TransformText($this->_wikitext, 2.0, 
$this->_request->getArg('pagename'));
$this->_html = $xmlcontent->AsXML();


Do you think it could be a problem ?


Jean-Nicolas.

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-...>]

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] [Fwd: SourceForge.net Support: Project database service load from project: phpwiki]

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

Manuel Vacelet schrieb:
> 2006/6/28, Reini Urban <ru...@x-...>:
>> Manuel Vacelet schrieb:
>>> 2006/6/27, Reini Urban <ru...@x-...>:
>>>> So you know what's going on...
>>> Woo !
>>> I hope you will keep us informed.
>>>
>>> And I hope this is not a phpwiki issue :/
>>>
>>> -- Manuel
>> It is a mysql issue with phpwiki.
> 
> So bad :/
> You have more info ? (which kind of queries, when, ...)

Unfortunately David had no time to investigate this further, no logs.

I re-enabled now the main wiki and the demo wiki with default
dba - db4, and will check it during the day.
Maybe the new ajax (Wikiwyg) editor went crazy?

>> At first I will disable mysql at all and only run dba.
>> But then I really want to know why, so I try to reproduce at home.
> 
> SF admins succeed to give you some infos (which pages acceeded, ...) ?
> 
> -- Manuel, who runs lot's of phpwiki based on the top of mysql without
> any problems yet ;)
-- 
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

[Phpwiki-talk] Captcha problem

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

What does it mean when the captcha image fails to show up; only the 
alternate text 'captcha' is displayed?  I assume it involves a failure by 
'?action=captcha' to successfully generate an image, but why?

The follow is the relevant source from the displayed page:

   <img src="?action=captcha&id=1151522916" alt="captcha" /><br/>
   <label for="edit:captcha_input">Type word above: </label><input 
type="text" class="wikitext" id="edit:captcha_input" 
name="edit[captcha_input]" size="10" maxlength="256" /></div>

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] Configuring LDAP to connect to Active Directory

[William L. <le...@k2...>]

the version is 1.3.12p2.
I have tried changing  USER_AUTH_POLICY= first-only as you suggested but 
it doesn't seem to help.

I have noticed that the constructor for GroupLDAP only runs when the 
session is first established. As far as I can tell this is the only 
place where new _LDAPPassUser gets called. But this is before I enter a 
user name and password. When I do enter a username and password. 
GroupLDAP's constructor never runs, and new _LDAPPassUser is therefore 
not called.... basically the only time I have observed _LDAPPassUser be 
created is before I have the opportunity to supply a username and password.

It frustrates me because I have seen posts by other users saying they 
have active directory working on their wiki( I think it might have been 
you Manuel), so I know it is supposed to be possible, and I find it hard 
to believe that something here got broken in a recent release.

Would it be too much to ask if anyone could provide a working example of 
a complete config.ini that connects to active directory?

-Will

Manuel Vacelet wrote:
> Which version of phpwiki are you running ?
>
> Does it change sth if you put
> USER_AUTH_POLICY= first-only
>
> -- Manuel
>   

Re: [Phpwiki-talk] [Fwd: SourceForge.net Support: Project database service load from project: phpwiki]

[Manuel V. <man...@gm...>]

2006/6/28, Reini Urban <ru...@x-...>:
> Manuel Vacelet schrieb:
> > 2006/6/27, Reini Urban <ru...@x-...>:
> >> So you know what's going on...
> >
> > Woo !
> > I hope you will keep us informed.
> >
> > And I hope this is not a phpwiki issue :/
> >
> > -- Manuel
>
> It is a mysql issue with phpwiki.

So bad :/
You have more info ? (which kind of queries, when, ...)

> At first I will disable mysql at all and only run dba.
> But then I really want to know why, so I try to reproduce at home.

SF admins succeed to give you some infos (which pages acceeded, ...) ?

-- Manuel, who runs lot's of phpwiki based on the top of mysql without
any problems yet ;)

[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] [Fwd: SourceForge.net Support: Project database service load from project: phpwiki]

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

Manuel Vacelet schrieb:
> 2006/6/27, Reini Urban <ru...@x-...>:
>> So you know what's going on...
> 
> Woo !
> I hope you will keep us informed.
> 
> And I hope this is not a phpwiki issue :/
> 
> -- Manuel

It is a mysql issue with phpwiki.

At first I will disable mysql at all and only run dba.
But then I really want to know why, so I try to reproduce at home.
-- 
Reini Urban
http://phpwiki.org/  http://murbreak.at/
http://helsinki.at/  http://spacemovie.mur.at/