phpwiki-talk

[Phpwiki-talk] Returned mail: HI

[<MAI...@pr...>]

User's mailbox is full: <pe...@sb...>
Unable to deliver mail.

[Phpwiki-talk] IncludeSiteMap (recursive IncludePage)

[Micki K. <mic...@co...>]

Hi folks.

Quite a while back I submitted a plugin called 'IncludeSiteMap', 
designed from the 'IncludePage' and 'SiteMap' plugins, by me and 
Cuthbert Cat.

Now that we're planning an upgrade to 1.3.8x, I'm wondering if anyone 
else has used it, or seen the value of a dynamic IncludePage to 
create books like this.

Please say yes - this is a huge feature and I'd bel glad to explain more, etc.!

Thanks,
Micki


-- 

Micki
mailto:mic...@co...

[Phpwiki-talk] Multiple 'page=' for Backlinks, SiteMap

[Micki K. <mic...@co...>]

Hi folks!

I haven't seen it mentioned, and I was wondering... we use WikiBadges 
for numerous Categorization needs (like CategoryApproved, 
CategoryDocumentation, etc.), and was wondering if it were possible 
to return BackLinks (and correspondingly, SiteMap) for pages meeting 
TWO criteria (i.e. an 'ApprovedDocumentation' page would contain
<?plugin SiteMap page=CategoryApproved,CategoryDocumentation ?>

Right now, we have to use a 'fulltextsearch', which doesn't let you 
exclude, and whose results are much different than BackLinks.

Multiple BackLinks/SiteMap criteria seems like a major organizational 
coup - any feedback or ideas?

Thanks,
Micki

-- 

Micki
mailto:mic...@co...

[Phpwiki-talk] Domain & Hosting only 1.99$

[indiaR <in...@ac...>]

Dear Sir/Madam,

Webhosting and Domain Registration only 1.99$
Reseller domain registration and Hosting available!
@ WWW.COMREGISTER.COM






Remove: Reply back with REMOVE

Re: [work] [Phpwiki-talk] re: DOCTYPE PROBLEM

[tei <42...@in...>]

Stanislaw Berka escribió:

> That's the same problem I reported 2-3 weeks ago.  I analyzed it and 
> asked for help but haven't got any response.  I'm attaching my analysis 
> below again for convenience.  Please, help!
> 
> ===  start: problem analysis repeated from earlier message
> When opening the PhpWiki page for the first time with Mozilla (ver. 
> 1.2.1) or Netscape, the following problem is reported at the top of the 
> page by Wiki (IE shows no page at all - only error message; see below 
> for error):
> 
>  >>>
> <div class="error"><p>lib/Request.php:136: Warning[2]: ob_start(): 
> output handler 'ob_gzhandler' cannot be used after 'URL-Rewriter'</p>
> </div>
>  >>>

> 
> I have no idea how to apply this "advice". I know Java but PHP is still 
> a mystery for me and also it might be more a configuration problem 
> rather than a code bug. Any pointers? Please, help.
>

Hummm... I think can be fixed with a edit at index.php or similar, 
deactivating compresion (sending has gz) or something.. I remenber a 
question about that at the phpwiki.sourceforge.net wiki

Re-searching:
http://phpwiki.sourceforge.net/phpwiki/FullTextSearch?s=ob_gzhandler

looks like prettywiki has help:
http://phpwiki.sourceforge.net/phpwiki/PrettyWiki

Also know bugs:
http://phpwiki.sourceforge.net/phpwiki/KnownBugs

And FAQ:
http://phpwiki.sourceforge.net/phpwiki/FrequentlyAskedQuestions

The solutions ends has...
Disable the compression in the index.php



// By default PhpWiki will try to have PHP compress its output
// before sending it to the browser (if you have a recent enough
// version of PHP and the browser supports it.)
// Define COMPRESS_OUTPUT to false to prevent output compression.
// Define COMPRESS_OUTPUT to true to force output compression,
// even if we think your version of PHP does this in a buggy
// fashion.
// Leave it undefined to leave the choice up to PhpWiki.
//define('COMPRESS_OUTPUT', false);

become:



// By default PhpWiki will try to have PHP compress its output
// before sending it to the browser (if you have a recent enough
// version of PHP and the browser supports it.)
// Define COMPRESS_OUTPUT to false to prevent output compression.
// Define COMPRESS_OUTPUT to true to force output compression,
// even if we think your version of PHP does this in a buggy
// fashion.
// Leave it undefined to leave the choice up to PhpWiki.
define('COMPRESS_OUTPUT', false);



...
I suspect (not tested).


> 
> If I use IE 6.0 instead of Mozilla/Netscape, the message is even more 
> cryptic:
>  >>> Error reported by IE:
> The XML page cannot be displayed
> Cannot view XML input using XSL style sheet. Please correct the error 
> and then click the Refresh button, or try again later.
> 
> -------------------------------------------------------------------------------- 
> 
> 
> Cannot have a DOCTYPE declaration outside of a prolog. Error processing 
> resource 'http://www.saintclarechurch.org/phpwiki/index.php'. Line 4, 
> Position 11
> 
> 
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
> ----------^
>  >>> End Error
> 
> ===  and
> 


arghhh!!!!

:(

Finding at the phpwiki, nor lucky :(

retryinng...
retryiinnng...
retrrrrryuiiiinngggg.....
retruuuuiiii1111nnnnarrgggghhhhhhhhhhhh!!!!!!!....

/me died



> tei wrote:
> 
>> Forget my last mail, the error reapear. :(
>>
>> -----------------
>>
>> The XML page cannot be displayed
>> Cannot view XML input using XSL style sheet. Please correct the error 
>> and then click the Refresh button, or try again later.
>>
>>
>> -------------------------------------------------------------------------------- 
>>
>>
>> Cannot have a DOCTYPE declaration outside of a prolog. Error 
>> processing resource 'http://telejano.berlios.de/wiki3/'. Line 4, 
>> Position 11
>>
>> <!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
>> ----------^
>>
> 

Re: [work] [Phpwiki-talk] re: DOCTYPE PROBLEM

[Stanislaw B. <sb...@po...>]

That's the same problem I reported 2-3 weeks ago.  I analyzed it and 
asked for help but haven't got any response.  I'm attaching my analysis 
below again for convenience.  Please, help!

===  start: problem analysis repeated from earlier message
When opening the PhpWiki page for the first time with Mozilla (ver. 
1.2.1) or Netscape, the following problem is reported at the top of the 
page by Wiki (IE shows no page at all - only error message; see below 
for error):

 >>>
<div class="error"><p>lib/Request.php:136: Warning[2]: ob_start(): 
output handler 'ob_gzhandler' cannot be used after 'URL-Rewriter'</p>
</div>
 >>>

Here's what I have found on Google:
+++
Error: "ob_start(): output handler 'ob_gzhandler' cannot be used after
'URL-Rewriter'"
Reason: You call ob_start('ob_gzhandler'); after session_start hs been 
called and trans_sid is used.
Solution: Call ob_start('ob_gzhandler'); before session_start().
+++

I have no idea how to apply this "advice". I know Java but PHP is still 
a mystery for me and also it might be more a configuration problem 
rather than a code bug. Any pointers? Please, help.

IE: 6.0 on WinME
OS: Red Hat Linux
PHP: 4.3.4
MySQL: 4.0.15-stand
PhpWiki: 1.3.4

If I use IE 6.0 instead of Mozilla/Netscape, the message is even more 
cryptic:
 >>> Error reported by IE:
The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error 
and then click the Refresh button, or try again later.

--------------------------------------------------------------------------------

Cannot have a DOCTYPE declaration outside of a prolog. Error processing 
resource 'http://www.saintclarechurch.org/phpwiki/index.php'. Line 4, 
Position 11


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
----------^
 >>> End Error

===  and

tei wrote:

> Forget my last mail, the error reapear. :(
>
> -----------------
>
> The XML page cannot be displayed
> Cannot view XML input using XSL style sheet. Please correct the error 
> and then click the Refresh button, or try again later.
>
>
> --------------------------------------------------------------------------------
>
> Cannot have a DOCTYPE declaration outside of a prolog. Error 
> processing resource 'http://telejano.berlios.de/wiki3/'. Line 4, 
> Position 11
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
> ----------^
>

[Phpwiki-talk] test site didn't update properly

[Steve W. <sw...@pa...>]

Just a note that for the last two nights the cron job that updates the 
test site (http://phpwiki.sf.net/test/) got a connection timeout from 
the CVS server; it does go on to reload the database tables, which is 
kind of pointless.

I still intend to move the shell scripts to somewhere in the web tree, 
so others can see them; I think I'll add a short circuit operator (&&) 
so that if the CVS update fails the database will not be wiped. 
Further, I should go back and see if I can't get the cron jobs to email 
the nightly output to phpwiki-talk or a similar list.

~swain

Re: [Phpwiki-talk] No new user in http://www.exit0.us/index.php/RecentVisitors

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

Norberto Meijome schrieb:
> touche, I'll RTFM ...my bad for not looking deep enough ( i assumed the 
> docs would be part of the distrib)

it's as docs/README.phpwiki-auth also in the distrib. but only in the 
nightly cvs snapshots, since v1.3.8 is not released yet :)

> great work !!!
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] No new user in http://www.exit0.us/index.php/RecentVisitors

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

Norberto Meijome schrieb:
> Hi Reini et al,
> I've seen several references to passwords (and other preferences) being 
> kept in a user's homepage...but so far I haven't found any documentation 
> on it.

No?
There it is, for a long time now:
   http://phpwiki.sourceforge.net/phpwiki/UserAuthentication
I updated it a week ago to the new scheme, but the old docs for prefs in 
homepage (which didn't change) are also there.

To see it internally see the DebugInfo on any users homepage.
Change any UserPreferences and then you see the metadata, exactly the 
"pref" field, in the page changed.

BTW: I keep a blog of my ongoing development at the demo wiki:
   http://phpwiki.sourceforge.net/demo/ReiniUrban/Kalender

> a) is there any docs on this...if so, would you mind pointing me in the 
> right direction?
> b) If there is no such doc...would you mind explaining to all ? I'm 
> happy to translate it all into end-user words if needed
> c) how does (if at all) this feature relate / link to the new user / 
> group / per page auth features you said you are working on?
> 
> Running 1.3.4 on FreeBSD / Apache/ mod_php / MySQL, 1.3.7 on win 2k /  
> Apache/ mod_php / MySQL and soon 1.3.7 on Linux & Solaris
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] LDAP

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

Paul Henry schrieb:

> Having trouble setting up LDAP to work in 1.3.7. I have WikiUserNew set
> to off. With the following settings, I cannot seem to authenticate user
> "PaulHenry" against the ldap server.
> 
> These are my index.php settings...
> 
> if (!defined('ALLOW_ANON_USER')) define('ALLOW_ANON_USER', true);
> if (!defined('ALLOW_ANON_EDIT')) define('ALLOW_ANON_EDIT', false);
> if (!defined('REQUIRE_SIGNIN_BEFORE_EDIT'))
> define('REQUIRE_SIGNIN_BEFORE_EDIT', ! ALLOW_ANON_EDIT);
> if (!defined('ALLOW_BOGO_LOGIN')) define('ALLOW_BOGO_LOGIN', false);
> 
> if (!defined('ALLOW_USER_PASSWORDS')) define('ALLOW_USER_PASSWORDS',
> true);

the following is ignored in ENABLE_USER_NEW = false

> if (defined('ALLOW_USER_PASSWORDS')) {
>     if (!isset($USER_AUTH_ORDER))
>         $USER_AUTH_ORDER =
>             array(
> //                "BogoLogin",
> //                "PersonalPage",
> //                "HttpAuth",
> //                "Db",
>                   "LDAP",  // define LDAP_AUTH_HOST and LDAP_AUTH_SEARCH
> //                "IMAP",  // define IMAP_AUTH_HOST
> //                "File"   // define AUTH_USER_FILE and opt.
> AUTH_USER_FILE_STORABLE
>                   ) ;
> 
>     if (!defined('PASSWORD_LENGTH_MINIMUM'))
> define('PASSWORD_LENGTH_MINIMUM', 4);
> 
>     if (!defined('USER_AUTH_POLICY'))
>         //define('USER_AUTH_POLICY','first-only');
>         //define('USER_AUTH_POLICY','old');
>         define('USER_AUTH_POLICY','strict');
>         //define('USER_AUTH_POLICY','stacked');
> }

these three are the only important settings.

> // LDAP auth
> if (!defined('LDAP_AUTH_HOST'))   define('LDAP_AUTH_HOST', '127.0.0.1');
> // Give the right LDAP root search information in the next statement.
> if (!defined('LDAP_AUTH_SEARCH')) define('LDAP_AUTH_SEARCH',
> "dc=nodomain");
> 
> if (!defined('ALLOW_LDAP_LOGIN')) define('ALLOW_LDAP_LOGIN', true and
> function_exists('ldap_connect'));
> 
> 
> Here's the ldap dump:
> 
> bullwinkle:/etc/ldap# ldapsearch -x
> # extended LDIF
> #
> # LDAPv3
> # base <> with scope sub
> # filter: (objectclass=*)
> # requesting: ALL
> #
> 
> # nodomain
> dn: dc=nodomain
> objectClass: top
> objectClass: dcObject
> objectClass: organization
> o: nodomain
> dc: nodomain
> 
> # admin, nodomain
> dn: cn=admin,dc=nodomain
> objectClass: simpleSecurityObject
> objectClass: organizationalRole
> cn: admin
> description: LDAP administrator
> userPassword: <removed>
> 
> # PaulHenry, nodomain
> dn: cn=PaulHenry,dc=nodomain
> objectClass: person
> cn: PaulHenry
> sn: Henry
> userPassword:: dGVzdA==
> 
> Suggestions?

not in this moment, since I (in fact my colleague) just setup our own 
samba ldap system, which I will use to get known to LDAP and to finish 
the WikiGroup LDAP class.
we use "uid=userid" as search string for WikiUser, which is fine.

your setup looks fine to me. PaulHenry is in dc=nodomain.
but we use it this way:

ldapsearch -x -h AUTH_LDAP_HOST -b dc=nodomain uid=PaulHenry

Note that the full ldap url might be needed in php "ldap://localhost"
like ldapsearch -x -H AUTH_LDAP_HOST -b dc=nodomain uid=PaulHenry

BTW: LDAP is great together with samba to have a common auth system for 
linux and windows servers. single user and password for all. also group 
and machine management.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] speling mistake in lib/removepage.php

[Paul H. <he...@ma...>]

line 46: 
$html = HTML(HTML::h2(fmt("Removed page '%s' succesfully.",
$pagename)));

change to:
$html = HTML(HTML::h2(fmt("Removed page '%s' successfully.",
$pagename)));

Re: [Phpwiki-talk] No new user in http://www.exit0.us/index.php/RecentVisitors

[Norberto M. <nu...@me...>]

Hi Reini et al,
I've seen several references to passwords (and other preferences) being 
kept in a user's homepage...but so far I haven't found any documentation 
on it.

a) is there any docs on this...if so, would you mind pointing me in the 
right direction?
b) If there is no such doc...would you mind explaining to all ? I'm 
happy to translate it all into end-user words if needed
c) how does (if at all) this feature relate / link to the new user / 
group / per page auth features you said you are working on?

Running 1.3.4 on FreeBSD / Apache/ mod_php / MySQL, 1.3.7 on win 2k /  
Apache/ mod_php / MySQL and soon 1.3.7 on Linux & Solaris

Thanks!!
Beto
Reini Urban wrote:

> AltGrendel schrieb:
>
>> On Tue, 2004-01-27 at 17:10, Chr. von Stuckrad wrote:
>>
>>> Eighter I'm pretty dumb tonight or something
>>> is wrong with creating a new user in the Wiki?
>>>
>>> Wanting to comment on an error in the new script
>>> for debugging regexps,
>>> I tried to edit with a NEW Name ('stucki') and
>>> a password (to be created I thought), and all
>>> I get is:
>>>
>>> PHP Warnings
>>> lib/WikiUser.php:229: Warning[512]: Unable to connect to LDAP server 
>>> localhost
>>>
>>> Somethig broken?
>>> Curious,    Stucki
>>
>>
>> Shouldn't be. As the administrator of the exit0.us wiki, I think I can
>> safely state that there is no password authentication enabled.
>> I have noticed that there are some users that are having problems
>> creating home pages. Is there a minimum character limit on the name of a
>> user's page? For example, it won't let you create a page for Bob(3
>> characters) but it will for Robert(6 characters).
>
>
> No, no char limit on the username. from 1.3.8 on one can set a 
> password char limit.
>
>> I'm not tying to hijack this thread because I've had other users
>> complain of the same basic thing. They try to create a user page but get
>> an "Invalid UserID or password" message. I've tried to check the
>> archives for this but haven't found anything.
>
>
> Old Auth Scheme (1.3.4 - 1.3.8) and new auth scheme (auth_policy = old):
>
> On REQUIRE_SIGNIN_BEFORE_EDIT = true:
> When the given username - password is invalid or not found, it tries 
> the next methods (imap, ldap, ...).
> If no matching user-passwd pair is found, "Invalid UserID or password" 
> is returned.
>
> So it looks like you enabled bogo login (ALLOW_BOGO_LOGIN = true), 
> which means that your users must login with a valid WikiWord. Robert 
> and Bob are no valid WikiWords.
>
> I suggest to set REQUIRE_SIGNIN_BEFORE_EDIT = false, so that any 
> username is accepted with or withour password. Then the password is 
> only checked if the user has a homepage, where the password is 
> actually stored.


-- 
Norberto Meijome | numard at meijome dot net
"Everything is interesting if you go into it deeply enough." - Richard Feynman

[Phpwiki-talk] LDAP

[Paul H. <he...@ma...>]

Having trouble setting up LDAP to work in 1.3.7. I have WikiUserNew set
to off. With the following settings, I cannot seem to authenticate user
"PaulHenry" against the ldap server.

These are my index.php settings...

if (!defined('ALLOW_ANON_USER')) define('ALLOW_ANON_USER', true);
if (!defined('ALLOW_ANON_EDIT')) define('ALLOW_ANON_EDIT', false);
if (!defined('REQUIRE_SIGNIN_BEFORE_EDIT'))
define('REQUIRE_SIGNIN_BEFORE_EDIT', ! ALLOW_ANON_EDIT);
if (!defined('ALLOW_BOGO_LOGIN')) define('ALLOW_BOGO_LOGIN', false);

if (!defined('ALLOW_USER_PASSWORDS')) define('ALLOW_USER_PASSWORDS',
true);
if (defined('ALLOW_USER_PASSWORDS')) {
    if (!isset($USER_AUTH_ORDER))
        $USER_AUTH_ORDER =
            array(
//                "BogoLogin",
//                "PersonalPage",
//                "HttpAuth",
//                "Db",
                  "LDAP",  // define LDAP_AUTH_HOST and LDAP_AUTH_SEARCH
//                "IMAP",  // define IMAP_AUTH_HOST
//                "File"   // define AUTH_USER_FILE and opt.
AUTH_USER_FILE_STORABLE
                  ) ;

    if (!defined('PASSWORD_LENGTH_MINIMUM'))
define('PASSWORD_LENGTH_MINIMUM', 4);

    if (!defined('USER_AUTH_POLICY'))
        //define('USER_AUTH_POLICY','first-only');
        //define('USER_AUTH_POLICY','old');
        define('USER_AUTH_POLICY','strict');
        //define('USER_AUTH_POLICY','stacked');
}

// LDAP auth
if (!defined('LDAP_AUTH_HOST'))   define('LDAP_AUTH_HOST', '127.0.0.1');
// Give the right LDAP root search information in the next statement.
if (!defined('LDAP_AUTH_SEARCH')) define('LDAP_AUTH_SEARCH',
"dc=nodomain");

if (!defined('ALLOW_LDAP_LOGIN')) define('ALLOW_LDAP_LOGIN', true and
function_exists('ldap_connect'));


Here's the ldap dump:

bullwinkle:/etc/ldap# ldapsearch -x
# extended LDIF
#
# LDAPv3
# base <> with scope sub
# filter: (objectclass=*)
# requesting: ALL
#

# nodomain
dn: dc=nodomain
objectClass: top
objectClass: dcObject
objectClass: organization
o: nodomain
dc: nodomain

# admin, nodomain
dn: cn=admin,dc=nodomain
objectClass: simpleSecurityObject
objectClass: organizationalRole
cn: admin
description: LDAP administrator
userPassword: <removed>

# PaulHenry, nodomain
dn: cn=PaulHenry,dc=nodomain
objectClass: person
cn: PaulHenry
sn: Henry
userPassword:: dGVzdA==

Suggestions?

Re: [Phpwiki-talk] daily demo cvs update?

[Steve W. <sw...@pa...>]

I have three cron jobs: make the nightly build, update the demo site, and
rebuild the test site. The scripts live in my home directory but perhaps
these should be moved to the web site directory so others in the project
can see them.

-bash-2.05b$ cat demosite.sh
#!/bin/bash

# update the demo site
cd $HOME/www/htdocs/demo
/usr/bin/cvs -d:pserver:anonymous@cvs1:/cvsroot/phpwiki update -d -P
$HOME/bin/cvs2cl.pl
exit 0

-bash-2.05b$ cat testsite.sh
#!/bin/bash

cd $HOME/www/htdocs/test
/usr/bin/cvs -d:pserver:anonymous@cvs1:/cvsroot/phpwiki update -dP
/usr/bin/mysql -h pr-db1 -uphpwiki -p******** phpwiki < schemas/mysql.sql

This morning there was a collision in mysql.sql, which I fixed on the test
site.

~swain


On Sun, 25 Jan 2004, Reini Urban wrote:

> How is our daily cvs up to the demo site done?
> I see no CVS subdirs, so I cannot fix index.php beforehand.
> Or is it disabled anyway?
> --
> Reini Urban
> http://xarch.tu-graz.ac.at/home/rurban/
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>
>

----
                  http://www.panix.com/~swain/
    "It has all the faults of a photograph." -- David Hockney
----

[Phpwiki-talk] DOCTYPE PROBLEM

[tei <42...@in...>]

I think this has ben already see in this list before (can be somewhat 
very common here) but is new for me.

I have a old Wiki with a few visits every day: telejano.berlios.de
For some reason the latest Internet Explorer conflict with some code at 
phpwiki,... the doctype line.  I have read the code and found that:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
   "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">

at the file:

./themes/default/templates/html.tmpl

This conflict with IE 6.0.280

If you change to this:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
   "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">


...everything work.

[Phpwiki-talk] re: DOCTYPE PROBLEM

[tei <42...@in...>]

Forget my last mail, the error reapear. :(

-----------------

The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error 
and then click the Refresh button, or try again later.


--------------------------------------------------------------------------------

Cannot have a DOCTYPE declaration outside of a prolog. Error processing 
resource 'http://telejano.berlios.de/wiki3/'. Line 4, Position 11

<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
----------^

Re: [Phpwiki-talk] Date and time format in Themes?

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

Oliver Betz schrieb:
> wouldn't it be nice to have the settings for date and time formats in 
> the configuration file?
> 
> At the moment some themes (MacOSX, Portland, SpaceWiki) set the 
> format via $Theme->setDateFormat, some not.
> 
> I wouldn't like to change the themes to get the right (ISO8601, SCNR) 
> date.

We had this before and didn't like it. Just change your theme or create 
a new one, based on the existing one.
I also would like to have "%x %X" as strftime format template, which is 
based on the servers locale.

See Theme.php:
Note:  Windows' implemetation of strftime does not include certain
format specifiers, such as %e (for date without leading zeros).  In
general, see:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_strftime.2c_.wcsftime.asp
As a result, we have to use %d, and strip out leading zeros ourselves.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] No new user in http://www.exit0.us/index.php/RecentVisitors

[AltGrendel <alt...@ex...>]

On Fri, 2004-01-30 at 10:57, AltGrendel wrote:
> On Fri, 2004-01-30 at 10:29, Reini Urban wrote:
> 
> <Snip>
> 
> > 
> > Old Auth Scheme (1.3.4 - 1.3.8) and new auth scheme (auth_policy = old):
> > 
> > On REQUIRE_SIGNIN_BEFORE_EDIT = true:
> > When the given username - password is invalid or not found, it tries the 
> > next methods (imap, ldap, ...).
> > If no matching user-passwd pair is found, "Invalid UserID or password" 
> > is returned.
> > 
> > So it looks like you enabled bogo login (ALLOW_BOGO_LOGIN = true), which 
> > means that your users must login with a valid WikiWord. Robert and Bob 
> > are no valid WikiWords.
> > 
> > I suggest to set REQUIRE_SIGNIN_BEFORE_EDIT = false, so that any 
> > username is accepted with or withour password. Then the password is only 
> > checked if the user has a homepage, where the password is actually stored.
> 
> Here is that section of the original index.php(comments removed):
> 
> if (!defined('ALLOW_USER_LOGIN')) define('ALLOW_USER_LOGIN', 'false');
> if (!defined('ALLOW_HTTP_AUTH_LOGIN')) define('ALLOW_HTTP_AUTH_LOGIN', 'false');
> if (!defined('ALLOW_BOGO_LOGIN')) define('ALLOW_BOGO_LOGIN', 'true');
> 
> if (!defined('REQUIRE_SIGNIN_BEFORE_EDIT'))
> define('REQUIRE_SIGNIN_BEFORE_EDIT', 'false');
> 
> -------------------------------------------
> I believe that this is correct according to what you're saying. Is there
> some other section or file that could be controlling this? And do you
> think an upgrade to 1.3.8b fix this?

I Found the answer to my question, it's 

(?<![[:alnum:]])(?:[[:upper:]][[:lower:]]+){2,}(?![[:alnum:]])

So as you indicated, it would have to be Bob12 to be a valid wiki word,
and of course Bob would not be valid.

Interesting.

-- 
AltGrendel <alt...@ex...>

Re: [Phpwiki-talk] Are we ready for a 1.4 beta 1?

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

Could you please change your checkout script to do a
chmod -R g+w afterwards.
Maybe you should also do a cvs up -C in the subdirs only to get a clean 
cvs copy. lib/main.php was broken because of a failed patch.

Or I would prefer to have a clean index.php also and use test as php 
script below the test dir, rename the test dir to <any-dir>,
test calls <any-dir>/index.php, so we can overrule the default settings 
more easily. and we could test PrettyWiki urls (USE_PATH_INFO=true) as 
before.

Steve Wainstead schrieb:
> On Jan 27, 2004, at 4:33 AM, Reini Urban wrote:
> 
>     Steve Wainstead schrieb:
> 
>         Sounds good. We should probably recommend 1.3.7 for the time
>         being if people want a stable featureful Wiki, however, and
>         1.3.8 and thereafter are in a state of flux.
>         I'll roll out 1.3.8 tonight or tomorrow.
> 
>     Couldn't you just wait a week until I'm finished with testing?
> 
> Sure! Just ask :o)

fine. looks much better now, but there are so many options to test.

> Currently, the nightly build is broken:
> 
> lib/DB_Session.php:31: Fatal[256]: Your WikiDB does not seem to be using 
> a Pear DB backend
> 
> lib/config.php:404: Notice[1024]: The admin password cannot be empty. 
> Please update your /index.php
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] Problem: Call to undefined function: trigger_warning()

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

Reini Urban schrieb:
> Anyone seen this before:
>   Fatal error: Call to undefined function: trigger_warning() in 
> /home/groups/p/ph/phpwiki/htdocs/test/lib/WikiUserNew.php on line 579

sorry, found my error.
I still don't understand the problem above, but it's not reproducable 
anymore, since I fixed the offending code.

pref_select and pref_update work okay now.

> Reproduce:
>   http://phpwiki.sourceforge.net/test/index.php
>   Enter a value at "Sign in" and press enter.
> 
> Strange strange strange. Probably a error in this php 4.1.2.
> But how to workaround?
> 
> First I saw that on the sf.net php $dbh->_backend->prepare (for the 
> PearDB backend) does not work. I thought, well oh well, maybe is the 
> backend class as reference not allowed. (lib/WikiDB/SQL.php:17)

$dbh->_backend->_dbh->prepare was the right object chain.

> but then even the standard function trigger_warning() is lost.
> I use php 4.2.2 in my windows test machine and there it works ok.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] Problem: Call to undefined function: trigger_warning()

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

Anyone seen this before:
   Fatal error: Call to undefined function: trigger_warning() in 
/home/groups/p/ph/phpwiki/htdocs/test/lib/WikiUserNew.php on line 579

Reproduce:
   http://phpwiki.sourceforge.net/test/index.php
   Enter a value at "Sign in" and press enter.

Strange strange strange. Probably a error in this php 4.1.2.
But how to workaround?

First I saw that on the sf.net php $dbh->_backend->prepare (for the 
PearDB backend) does not work. I thought, well oh well, maybe is the 
backend class as reference not allowed. (lib/WikiDB/SQL.php:17)

but then even the standard function trigger_warning() is lost.
I use php 4.2.2 in my windows test machine and there it works ok.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] No new user in http://www.exit0.us/index.php/RecentVisitors

[AltGrendel <alt...@ex...>]

On Fri, 2004-01-30 at 10:29, Reini Urban wrote:

<Snip>

> 
> Old Auth Scheme (1.3.4 - 1.3.8) and new auth scheme (auth_policy = old):
> 
> On REQUIRE_SIGNIN_BEFORE_EDIT = true:
> When the given username - password is invalid or not found, it tries the 
> next methods (imap, ldap, ...).
> If no matching user-passwd pair is found, "Invalid UserID or password" 
> is returned.
> 
> So it looks like you enabled bogo login (ALLOW_BOGO_LOGIN = true), which 
> means that your users must login with a valid WikiWord. Robert and Bob 
> are no valid WikiWords.
> 
> I suggest to set REQUIRE_SIGNIN_BEFORE_EDIT = false, so that any 
> username is accepted with or withour password. Then the password is only 
> checked if the user has a homepage, where the password is actually stored.

Here is that section of the original index.php(comments removed):

if (!defined('ALLOW_USER_LOGIN')) define('ALLOW_USER_LOGIN', 'false');
                                                                                                                         if (!defined('ALLOW_HTTP_AUTH_LOGIN')) define('ALLOW_HTTP_AUTH_LOGIN', 'false');
                                                                                                                         if (!defined('ALLOW_BOGO_LOGIN')) define('ALLOW_BOGO_LOGIN', 'true');

if (!defined('REQUIRE_SIGNIN_BEFORE_EDIT'))
define('REQUIRE_SIGNIN_BEFORE_EDIT', 'false');

-------------------------------------------
I believe that this is correct according to what you're saying. Is there
some other section or file that could be controlling this? And do you
think an upgrade to 1.3.8b fix this?

-- 
AltGrendel <alt...@ex...>

Re: [Phpwiki-talk] No new user in http://www.exit0.us/index.php/RecentVisitors

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

AltGrendel schrieb:
> On Tue, 2004-01-27 at 17:10, Chr. von Stuckrad wrote:
>>Eighter I'm pretty dumb tonight or something
>>is wrong with creating a new user in the Wiki?
>>
>>Wanting to comment on an error in the new script
>>for debugging regexps,
>>I tried to edit with a NEW Name ('stucki') and
>>a password (to be created I thought), and all
>>I get is:
>>
>>PHP Warnings
>>lib/WikiUser.php:229: Warning[512]: Unable to connect to LDAP server localhost
>>
>>Somethig broken?
>>Curious,    Stucki
> 
> Shouldn't be. As the administrator of the exit0.us wiki, I think I can
> safely state that there is no password authentication enabled. 
> 
> I have noticed that there are some users that are having problems
> creating home pages. Is there a minimum character limit on the name of a
> user's page? For example, it won't let you create a page for Bob(3
> characters) but it will for Robert(6 characters).

No, no char limit on the username. from 1.3.8 on one can set a password 
char limit.

> I'm not tying to hijack this thread because I've had other users
> complain of the same basic thing. They try to create a user page but get
> an "Invalid UserID or password" message. I've tried to check the
> archives for this but haven't found anything.

Old Auth Scheme (1.3.4 - 1.3.8) and new auth scheme (auth_policy = old):

On REQUIRE_SIGNIN_BEFORE_EDIT = true:
When the given username - password is invalid or not found, it tries the 
next methods (imap, ldap, ...).
If no matching user-passwd pair is found, "Invalid UserID or password" 
is returned.

So it looks like you enabled bogo login (ALLOW_BOGO_LOGIN = true), which 
means that your users must login with a valid WikiWord. Robert and Bob 
are no valid WikiWords.

I suggest to set REQUIRE_SIGNIN_BEFORE_EDIT = false, so that any 
username is accepted with or withour password. Then the password is only 
checked if the user has a homepage, where the password is actually stored.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] Are we ready for a 1.4 beta 1?

[Steve W. <sw...@pa...>]

On Jan 27, 2004, at 4:33 AM, Reini Urban wrote:

> Steve Wainstead schrieb:
>> Sounds good. We should probably recommend 1.3.7 for the time being if 
>> people want a stable featureful Wiki, however, and 1.3.8 and 
>> thereafter are in a state of flux.
>> I'll roll out 1.3.8 tonight or tomorrow.
>
> Couldn't you just wait a week until I'm finished with testing?

Sure! Just ask :o)

Currently, the nightly build is broken:

lib/DB_Session.php:31: Fatal[256]: Your WikiDB does not seem to be 
using a Pear DB backend

lib/config.php:404: Notice[1024]: The admin password cannot be empty. 
Please update your /index.php

Re: [Phpwiki-talk] No new user in http://www.exit0.us/index.php/RecentVisitors

[AltGrendel <alt...@ex...>]

On Tue, 2004-01-27 at 17:10, Chr. von Stuckrad wrote:
> Hi!
> 
> Eighter I'm pretty dumb tonight or something
> is wrong with creating a new user in the Wiki?
> 
> Wanting to comment on an error in the new script
> for debugging regexps,
> I tried to edit with a NEW Name ('stucki') and
> a password (to be created I thought), and all
> I get is:
> 
> PHP Warnings
> lib/WikiUser.php:229: Warning[512]: Unable to connect to LDAP server localhost
> 
> Somethig broken?
> 
> Curious,    Stucki

Shouldn't be. As the administrator of the exit0.us wiki, I think I can
safely state that there is no password authentication enabled. 

I have noticed that there are some users that are having problems
creating home pages. Is there a minimum character limit on the name of a
user's page? For example, it won't let you create a page for Bob(3
characters) but it will for Robert(6 characters).

I'm not tying to hijack this thread because I've had other users
complain of the same basic thing. They try to create a user page but get
an "Invalid UserID or password" message. I've tried to check the
archives for this but haven't found anything.


-- 
AltGrendel <alt...@ex...>