phplib-users — A list for users of phplib to talk / discuss phplib

[Phplib-users] test

[Marko K. <Mar...@mc...>]

Hi,

sorry for this nonsense message. But it's only a test whether the list
works since in the old list on geocrawler I saw man complains about this.
And yet there doesn't seem to be an entry on this list to exists. So this
might be the first in the row, otherwise something is really broken.

Sorry.

Marko

[Phplib-users] Re: Default access and a log-in box

[Michael F. <mai...@ya...>]

Maybe optimistically, I'm trying for case B!

> you want to show a login form in a common page that, when submitted,
> comes back to that same page

The top of the page, and the log-in box (modified loginform.ihtml) show up,
but nothing below that. As you suggested, the mistake seems to be in calling
$auth->auth_loginform rather than echoing it ...

Anyway, now the archives are back, I'll follow the earlier thread and try
and work out exactly what should be going on.

Thanks

Michael




----- Original Message -----
From: "giancarlo pinerolo" <gia...@na...>
To: <php...@li...>
Sent: Monday, August 20, 2001 9:33 PM
Subject: [Phplib-users] Re: Default access and a log-in box


> > I'm trying to include a log-in box within a normal page so that users =
> > can register and access further information and functions.=20
> >
> > I've managed default access but once I include the log-in box, it =
> > protects the content further down the page. I'm sure I've over-looked =
> > the obvious, but if anyone could suggest an example to learn from ...
>
> What do you mean by 'it protects the content further down the page'?
> Does only a part of the page show up? or the loginform.ihtml page?
>
> There are two cases:
> a) you want to show a login form in a common page that, when submitted,
> drives to another page
> b) you want to show a login form in a common page that, when submitted,
> comes back to that same page
>
>
> for case a) you don't need any feature in the containing page, not even
> session. You need at least session and auth in the 'after login' page
> for case b) you need session+default auth in the containing page, (which
> is also the after login page)
>
> case a) is a lot simpler. you set a form in pagea with action=pageb.php
> and the two input fields username and password, in pageb.php you do:
>
>     <?
>       page_open(array("sess" => "Example_Session",
>       "auth" => "Example_Auth",   // you need this
>       "perm" => "Example_Perm", "user" => "Example_User"));
>
>     if (!$auth->auth["uid"]=$auth->auth_validatelogin())
>             {
>             $auth->login_if("doit");
>             }
>     ?>
>     WELCOME USER
>     <?
>     page_close();
>
>
> case b) is more compliacted.
> as pagea.php, in this case acts as both the sending and receiving page,
> you need default auth here. and redirect to itself. I'll like this
> popular hack to be canonicized somehow. as the back button and
> cancel-login button hacks.
> get some ideas from
> http://www.geocrawler.com/archives/3/195/2001/7/300/6167151/
> but set the action to $PHP_SELF and echo the form instead of calling
> $auth->auth_loginform
>
> I can't tell you more about case b) , see if case a) fits for you first.
>
> Giancarlo
>
>
> _______________________________________________
> Phplib-users mailing list
> Php...@li...
> http://lists.sourceforge.net/lists/listinfo/phplib-users
>


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

Re: [Phplib-users] Help! New Error to me ... SOLVED

[Richard A. <rh...@ju...>]

At 5:56 PM -0700 20/8/01, Bob Bowker wrote:

>My dummy ... I ran phpinfo() and discovered that this particular install
>had allow_call_time_pass_reference set to OFF by default.  Changed that to
>"1" in .htaccess, and all's well ...

Aah I see, I thought this bug was a bit easy to fix :)
Looks like all the calls to serialize have to have the
ampersands removed from the str arg.

I'll repost this bug to the SF tracker and sort it out
next time I'm working on session.inc.

The code should still run cleanly even with
allow_call_time_pass_reference turned off.

 ...R.

Re: [Phplib-users] Help! New Error to me ... SOLVED

[Bob B. <bo...@iN...>]

Hi --

My dummy ... I ran phpinfo() and discovered that this particular install 
had allow_call_time_pass_reference set to OFF by default.  Changed that to 
"1" in .htaccess, and all's well ...

Sorry for the false alarm ...

Bob.

At 09:48 AM 8/21/01 +1000, you wrote:
>At 4:24 PM -0700 20/8/01, Bob Bowker wrote:
>
> >Warning: Call-time pass-by-reference has been deprecated
>
>This has been fixed in the CVS tree. The change is to add a '&' to
>the function declaration of serialize in session.inc:
>
>change
>   function serialize($prefix, $str) {
>to
>   function serialize($prefix, &$str) {
>
>  ...R.
>
>_______________________________________________
>Phplib-users mailing list
>Php...@li...
>http://lists.sourceforge.net/lists/listinfo/phplib-users

Re: [Phplib-users] Help! New Error to me ...

[Bob B. <bo...@iN...>]

Hi --

I just grabbed session.inc from the CVS and using that ver 1.10, the same 5 
errors come up, just in different line numbers ...?!?

Bob.

At 09:48 AM 8/21/01 +1000, you wrote:
>At 4:24 PM -0700 20/8/01, Bob Bowker wrote:
>
> >Warning: Call-time pass-by-reference has been deprecated
>
>This has been fixed in the CVS tree. The change is to add a '&' to
>the function declaration of serialize in session.inc:
>
>change
>   function serialize($prefix, $str) {
>to
>   function serialize($prefix, &$str) {
>
>  ...R.
>
>_______________________________________________
>Phplib-users mailing list
>Php...@li...
>http://lists.sourceforge.net/lists/listinfo/phplib-users

Re: [Phplib-users] Help! New Error to me ...

[Bob B. <bo...@iN...>]

Richard --

Tried that, no joy: the error I quoted is still reported in 5 places ... 
using session.inc v 1.5 2000/07/12 18:22:35.  Does the pass-by-reference 
need to be changed anywhere else ...?

Thanks --

Bob.

At 09:48 AM 8/21/01 +1000, Richard Archer wrote:
>At 4:24 PM -0700 20/8/01, Bob Bowker wrote:
>
> >Warning: Call-time pass-by-reference has been deprecated
>
>This has been fixed in the CVS tree. The change is to add a '&' to
>the function declaration of serialize in session.inc:
>
>change
>   function serialize($prefix, $str) {
>to
>   function serialize($prefix, &$str) {
>
>  ...R.
>
>_______________________________________________
>Phplib-users mailing list
>Php...@li...
>http://lists.sourceforge.net/lists/listinfo/phplib-users

Re: [Phplib-users] Help! New Error to me ...

[Richard A. <rh...@ju...>]

At 4:24 PM -0700 20/8/01, Bob Bowker wrote:

>Warning: Call-time pass-by-reference has been deprecated

This has been fixed in the CVS tree. The change is to add a '&' to
the function declaration of serialize in session.inc:

change
  function serialize($prefix, $str) {
to
  function serialize($prefix, &$str) {

 ...R.

[Phplib-users] Help! New Error to me ...

[Bob B. <bo...@iN...>]

Hi --

We have phpLib 7.2c (amended) or 7.2d running on several servers with 
everything from PHP 3.12 through the latest 4.x ...

On a new setup with PHP 4.0.3pl1 (to be upgraded soon, I'm working on 
that!), I'm getting the following error, which I've never seen before, and 
I can't track down successfully so far ... any suggestions or help will be 
appreciated.

Thanks --

Bob.

Warning: Call-time pass-by-reference has been deprecated - argument passed 
by value; If you would like to pass it by reference, modify the declaration 
of [runtime function name](). If you would like to enable call-time 
pass-by-reference, you can set allow_call_time_pass_reference to true in 
your INI file. However, future versions may not support this any longer. in 
/home/sites/site19/php/session.inc on line 262

[Phplib-users] no phplib-users archives on SF

[giancarlo p. <gia...@na...>]

There is no archive on Sourceforge for the new list phplib-users.

Gian

[Phplib-users] Re: Default access and a log-in box

[giancarlo p. <gia...@na...>]

> I'm trying to include a log-in box within a normal page so that users =
> can register and access further information and functions.=20
> 
> I've managed default access but once I include the log-in box, it =
> protects the content further down the page. I'm sure I've over-looked =
> the obvious, but if anyone could suggest an example to learn from ...

What do you mean by 'it protects the content further down the page'?
Does only a part of the page show up? or the loginform.ihtml page?

There are two cases: 
a) you want to show a login form in a common page that, when submitted,
drives to another page
b) you want to show a login form in a common page that, when submitted,
comes back to that same page


for case a) you don't need any feature in the containing page, not even
session. You need at least session and auth in the 'after login' page 
for case b) you need session+default auth in the containing page, (which
is also the after login page)

case a) is a lot simpler. you set a form in pagea with action=pageb.php
and the two input fields username and password, in pageb.php you do:

    <?
      page_open(array("sess" => "Example_Session",
      "auth" => "Example_Auth",   // you need this
      "perm" => "Example_Perm", "user" => "Example_User"));

    if (!$auth->auth["uid"]=$auth->auth_validatelogin())
            {
            $auth->login_if("doit");
            }
    ?>
    WELCOME USER
    <?
    page_close();


case b) is more compliacted. 
as pagea.php, in this case acts as both the sending and receiving page,
you need default auth here. and redirect to itself. I'll like this
popular hack to be canonicized somehow. as the back button and
cancel-login button hacks. 
get some ideas from
http://www.geocrawler.com/archives/3/195/2001/7/300/6167151/
but set the action to $PHP_SELF and echo the form instead of calling
$auth->auth_loginform

I can't tell you more about case b) , see if case a) fits for you first.

Giancarlo

[Phplib-users] Default access and a log-in box

[Michael F. <mai...@ya...>]

Hi all,

I'm struggling and I'd be extremely grateful for some help!=20

I'm trying to include a log-in box within a normal page so that users =
can register and access further information and functions.=20

I've managed default access but once I include the log-in box, it =
protects the content further down the page. I'm sure I've over-looked =
the obvious, but if anyone could suggest an example to learn from ...

Many thanks


Michael Ford

Re: [Phplib-users] Session,Auth,Perm

[Ben C. <php...@be...>]

To protect an entire page you probably want $perm->check() instead of $perm->have_perm().

On Mon, Aug 20, 2001 at 09:59:57AM -0500, White, Bob wrote:
> Hi All,
> I can't seem to get session, auth and perm to work right. 
>  
>  I have at the top of my page:
> 
> <?php 
>   page_open(array("sess"=>"ieweb_Session",
>                   "auth"=>"ieweb_Auth",
>                   "perm"=>"ieweb_Perm"));
>   if ($perm->have_perm("admin")):
> 
>  <!-- Code that I want to protect -->
> 
> endif;
> page_close();
> ?>
> 
> I get a login screen, I try to login under a user that has only "user"
> rights and it still lets me in.  The local.inc is as delivered except
> modified for my ieweb... subclasses.
> 
> Help!  Please,
> 
> Bob White
> 
> 
> _______________________________________________
> Phplib-users mailing list
> Php...@li...
> http://lists.sourceforge.net/lists/listinfo/phplib-users

[Phplib-users] Session,Auth,Perm

[White, B. <rc...@sb...>]

Hi All,
I can't seem to get session, auth and perm to work right. 
 
 I have at the top of my page:

<?php 
  page_open(array("sess"=>"ieweb_Session",
                  "auth"=>"ieweb_Auth",
                  "perm"=>"ieweb_Perm"));
  if ($perm->have_perm("admin")):

 <!-- Code that I want to protect -->

endif;
page_close();
?>

I get a login screen, I try to login under a user that has only "user"
rights and it still lets me in.  The local.inc is as delivered except
modified for my ieweb... subclasses.

Help!  Please,

Bob White

[Phplib-users] menu.inc "pseudo" feature

[Richard A. <rh...@ju...>]

Hi,

Does anyone know how the "pseudo" feature of menu.inc is intended to be used?

I'm guessing it allows the creation of menu items that don't have an
associated page -- like headings in the menu. But it doesn't seem to be
documented anywhere.

I'm making some changes to menu.inc at present, and I want to test out
that "pseudo" is still working as expected.

 ...Richard.

Re: [Phplib-users] CVS: php-lib/php/db/mysql/db_sql.inc

[Richard A. <rh...@ju...>]

At 4:09 PM +0200 19/8/01, Guillaume Desclaux wrote:

>In php-lib/php/db/mysql/db_sql.inc

Hi Guillaume,

I have reposted your two bug reports to the SourceForge bug tracker.

Watch out for the development tree though. It's quite broken in a
number of areas, and likely to stay that way for quite a while.

At the moment the members of the core phplib development team
(including myself) are working through bugs reported against the
php-lib-stable tree. Bugs in the -devel tree will be looked at with
lower priority.

The next release of PHPLIB will be based on the 7.2d code (i.e. the
php-lib-stable CVS tree not the devel tree).

 ...Richard.

[Phplib-users] CVS: php-lib/php/db/mysql/db_sql.inc

[Guillaume D. <gde...@pr...>]

Hi

In php-lib/php/db/mysql/db_sql.inc 

  /* public: shorthand notation */
  function nf() {
    return $this->num_rows();
  }

  function np() {
    print $this->num_rows();
  }

  function f($Name) {
    return $this->Record[$Name];
  }

  function p($Name) {
    print $this->Record[$Name];
  }  

are missing...

Guillaume

[Phplib-users] Bugs php-lib/php/...

[Guillaume D. <gde...@pr...>]

Hi,

Bugs in : php-lib/php/db/mysql/db_sql.inc

in line 186 :
      $q  = sprintf('select p_nextid from %s where p_seq_name = '%s'',
should be replace by :
      $q  = sprintf("select p_nextid from %s where p_seq_name = '%s'",

in line 195 :
        $q = sprintf('insert into %s ( p_seq_name, p_nextid )
values('%s', %s)',
should be replace by :
        $q = sprintf("insert into %s ( p_seq_name, p_nextid )
values('%s', %s)",


in line 204 :
      $q = sprintf('update %s set p_nextid = '%s' where p_seq_name =
'%s'',
should be replace by :
      $q = sprintf("update %s set p_nextid = '%s' where p_seq_name =
'%s'",


Moreover :

  /* private: error handling */
  function halt($msg) {
    $this->Error = @mysql_error($this->Link_ID);
    $this->Errno = @mysql_errno($this->Link_ID);
    if ($this->Halt_On_Error == "no")
      return;

    $this->haltmsg($msg);

    if ($this->Halt_On_Error != "report")
      die("Session halted.");
  }

  function haltmsg($msg) {
    printf("</td></tr></table><b>Database error:</b> %s<br>\n", $msg);
    printf("<b>MySQL Error</b>: %s (%s)<br>\n",
      $this->Errno,
      $this->Error);
  }

is missing in this file...


Bugs in : php-lib/php/local4.inc

in line 73 :
  var $mode           = "user"
should be :
  var $mode           = "user";

Moreover in php-lib/php/ local4..inc and local.inc :

class Example_Default_Auth extends Example_Auth {
  var $classname = "Example_Default_Auth";

  var $nobody    = true;
}

is missing...

I hope that it helps you to upgrade the CVS repository.

Bye

Guillaume

[Phplib-users] PHP4

[Guillaume D. <gde...@pr...>]

> Files in phplib4/ also work, but they are not supported by the core
team
> and haven't been changed for 8 months (actually, they had been moved
> to the php-lib/unsup/ dir).

They had been moved to the php-lib/unsup/ dir but they are still
existing in php-lib/php/phplib-4...
To avoid confusion, they should be deleted, don't you think ?

I've also seen that there is reference to the class "DB_Generic_Sql" in
php-lib/php/db/db_sql.inc and in php-lib/php/db/mysql/db_sql.inc... but
I cannot see where this generic class is defined...

Guillaume

Re: [Phplib-users] Test whether db table exists using DB_SQL

[Jesse S. <ph...@sw...>]

Did anyone look at the current db_sql code?  There is a function called
table_names that already does exactly what you are talking about...

> From: Peter Bowyer <re...@f2...>
> Date: Fri, 17 Aug 2001 13:59:05 +0100
> To: phplib List <php...@li...>
> Subject: Re: [Phplib-users] Test whether db table exists using DB_SQL
> 
> At 10:21 PM 8/16/01 +0200, you wrote:
>> Why not create a small 'meta' table that contains a flag that you set on
>> the creation of the target table?
>> If the flag doesn't exist you have to create your table, otherwise the
>> table already exists.
>> 
>> Maybe this approach is too simplistic, but at least it will work in every
>> DB environment.
> 
> Great idea!  Thanks a lot!!
> 
> Cheers!
> Peter.
> 
> 
> --oOo--
> Narrow Gauge on the web - photos, directory and forums!
> http://www.narrow-gauge.co.uk
> --oOo--
> Peter's web page - Scottish narrow gauge in 009
> http://members.aol.com/reywob/
> --oOo--
> 
> 
> _______________________________________________
> Phplib-users mailing list
> Php...@li...
> http://lists.sourceforge.net/lists/listinfo/phplib-users

Re: [Phplib-users] Test whether db table exists using DB_SQL

[Peter B. <re...@f2...>]

At 10:21 PM 8/16/01 +0200, you wrote:
>Why not create a small 'meta' table that contains a flag that you set on 
>the creation of the target table?
>If the flag doesn't exist you have to create your table, otherwise the 
>table already exists.
>
>Maybe this approach is too simplistic, but at least it will work in every 
>DB environment.

Great idea!  Thanks a lot!!

Cheers!
Peter.


--oOo--
Narrow Gauge on the web - photos, directory and forums!
http://www.narrow-gauge.co.uk
--oOo--
Peter's web page - Scottish narrow gauge in 009
http://members.aol.com/reywob/
--oOo--

Re: [Phplib-users] Re:Challenge_Auth problem

[Layne W. <la...@if...>]

I have used various versions of IE on my Mac at home with phplib 7.2c sites
using crc authentication. I do not recall any problems.

Which version of IE and which version of MacOS are you using?

> The login fails. Even if a use Simple-Auth without md5. It seems to
> work on every browser on every OS except IE on Mac.
> So it can't be a Javascript problem because there is no Javascript.
> Strangely enough the "register new user" part I wrote works perfectly
> even with Mac-IE.
> And it seems also like the browser would send the data in the right
> way. Is it possible that the MacIE adds somes sort of (I don't know
> the english word), something like /r or /n, etc.?

That is highly unlikely, although there are a few abnormalities in
(especially) version 4.5.

1. Are you using the latest PHPLib or have you made the changes to the cache
settings that have appeared on this list several times?

2. Have you checked your browser preferences? Try reseting them to the
defaults (i.e. remove your preference file to a safe location and restart
the browser).


Layne Weathers
Ifworld Inc

[Phplib-users] Re:Challenge_Auth problem

[Guenther T. <th...@eq...>]

Hi Richard,

you wrote:

>>There seems to be no difference. Even if I leave the Java-Script and
>>the md5-part away and try to send the password in clear, IE on Mac
>>still doesn't work.

> What is it actually doing... sending the password in the clear?
> Or just failing all together?

The login fails. Even if a use Simple-Auth without md5. It seems to
work on every browser on every OS except IE on Mac.
So it can't be a Javascript problem because there is no Javascript.
Strangely enough the "register new user" part I wrote works perfectly
even with Mac-IE.
And it seems also like the browser would send the data in the right
way. Is it possible that the MacIE adds somes sort of (I don't know
the english word), something like /r or /n, etc.?

Guenther

[Phplib-users] Re: Challenge_Auth problem

[Richard A. <rh...@ju...>]

At 6:15 PM +0200 16/8/01, Guenther Theilen wrote:

>There seems to be no difference. Even if I leave the Java-Script and
>the md5-part away and try to send the password in clear, IE on Mac
>still doesn't work.

What is it actually doing... sending the password in the clear?
Or just failing all together?

 ...Richard.

Re: [Phplib-users] Test whether db table exists using DB_SQL

[Peter T. <pte...@te...>]

Peter,

Why not create a small 'meta' table that contains a flag that you set on 
the creation of the target table?
If the flag doesn't exist you have to create your table, otherwise the 
table already exists.

Maybe this approach is too simplistic, but at least it will work in every 
DB environment.

Cheers,
Peter


At 10:14 16-08-2001, Peter Bowyer wrote:
>At 05:48 PM 8/16/01 +1000, you wrote:
>> >I thought that this SQL was specific to MySQL :-(
>>
>>You're right... at least it won't work on MSSql/ODBC:
>>
>>Warning: SQL error: [Microsoft][ODBC SQL Server Driver][SQL Server]
>>Could not find stored procedure 'show'., SQL state 37000 in
>>SQLExecDirect in D:\www\test\html\test.php on line 24
>>
>>Bummer!
>>
>>I guess you just have to perform the query and see if you encounter
>>an error.
>
>I tried that, but I couldn't suppress an error message :-(
>Actually I found that changing var $Halt_On_Error in db_mysql.inc to "no" 
>cured the problem - however, this variable isn't implemented in the other 
>database drivers, and I only have access to MySQL so cannot test it on the 
>other databases at the present time :-(
>
>Can you confirm how the other drivers react if there is no table present?
>
>Thanks,
>Peter.
>
>--
>In the beginning was the word,
>and the word was Content-type: text/plain.
>
>
>_______________________________________________
>Phplib-users mailing list
>Php...@li...
>http://lists.sourceforge.net/lists/listinfo/phplib-users


------------------------------------------------------------------
TERIS Information Services BV
Peter Termaten             Phone: +31 20 494 2503
Rode Kruisstraat 22E    Fax:     +31 20 494 2504
1025 KN  Amsterdam       Mobile: +31 653 65 8686
                           www.teris.nl
------------------------------------------------------------------

[Phplib-users] Re: Challenge_Auth problem

[Guenther T. <th...@eq...>]

Hi Richard,

you wrote:

> I've been working on the md5 stuff recently. Give these files a try and
> let me know how they go.

There seems to be no difference. Even if I leave the Java-Script and
the md5-part away and try to send the password in clear, IE on Mac
still doesn't work.
Very strange.

Guenther