Re: [phpslash-users] new docs..

[nathan r. h. <nh...@ar...>]

On Wed, 4 Oct 2000, Russell McOrmond wrote:

> On Wed, 4 Oct 2000, nathan r. hruby wrote:
> 
> > It wouldn't be a conflict, but it wouldn't carry over either unless both
> > apps were using the same session object definition (for phpslash it's
> > called slashSess) Generally, it's bad to just share session databases
> > unless you know that eash app won't obliterate the others session-ified
> > variables.
> 
>   Could this be noted in the docs, to encourage people to set up another
> database if at all possible?
> 

Can do.

> > The preview function doesn't work quite right yet.  Does stuff pop up
> > after you enter the info and then go back and modify it?
> 
>   Please let us know areas we should be hammering on, and areas that
> aren't quite ready yet.  I installed and started testing specifically
> because I thought you were nearing a release and needed some testing.
> 

We are, that's why we need testing.  The rss block preview is a known bug
and is listed in the bugs database.  Since the blocks code is totally new
from the ground up it's going to take a little more shaking than normal.
Sorry.  

The current plan is to quash the current bugs and release an rc2 which
should shake out php3 compatibility issues and then hopefully release the
final fajita.

We are aware that not every one can / wants to switch u[p to php4, and we
will for the short term try to produce compatible code.  After the Fajita
series is out the door we will revisit this issue.  that should also allow
enough time to see if people are switching up and see what happens with
the licence.  However, compat code is not the highest priority, (I don't
have the horse power to run two httpds) so it's in the hands of the folks
using php3 to report the problems.

>   I'm wanting to have a PHP 3.0.16 based system as one of the 'tested
> platforms' before the next release.
> 

I agree.  And I additonaly thank you for bringing compat issues up and
making us aware of the current bugs. 

> > looks cool to me (the pages).  Your problem sounds like the templates are
> > set to not pull out unused variables, check the template create call and
> > see what it says (Ithink the options are keep, comment and delete)
> 
>   This would be an install-issue then that we'll want to resolve. I
> haven't changed the templates from the CVS version.  Just for information,
> so far I have changed:
> 

I'll check the CVS and see what's up.

> config.php3:
>   require("prepend.php3");
>   $basedir = "/home/russell/russell/php/phpslash-ft/public_html";
>   $rootdir = "http://russell.flora.org/php/phpslash-ft/public_html";
>   var $Host = "db.int.flora.ottawa.on.ca";
>      -as well as the User/Password
> 
> public_html/Block_render_rss.class:
>        //xml_set_object($this->xml, &$this);
>    - If someone can let me know what xml_set_object is intended to do
> (It's not documented in PHP, not in PHPLib nor in any of the other files
> in PHPSlash), I can then look into writing a replacement.
> 
> 

xml_set_object() is a php4 only kind thing.  It's listed in the online
docs here: http://www.php.net/manual/function.xml-set-object.php
The desciption is way odd.. 

Also there is some discussion (or, has been) on the php-general list on
this very subject.  The problem is that you can't pass object methods to
an xml parser (something about the way object refrences exsist.. not
really sure the details) try this:
http://marc.theaimsgroup.com/?l=php-general&m=93906656612258&w=2
and this 
http://marc.theaimsgroup.com/?l=php-general&m=91622566130226&w=2
for tips on building compatibilty code.  Note that this will mean a hefty
rewrite of Block_render_rss.class, but shouldn't be too crfty to
implement, (Just add a check for type and automagically require the
correct class in config.php3)

And here's the function from php-4.0.1pl1/ext/xml/xml.c (Also needs to be
defined in php-4.0.1pl1/ext/xml/php_xml.h  I think that they did alot of
work on the xml stuff in php4, so backporting this to php3 may prove
tricky.

/* {{{ proto int xml_set_object(int pind, object &obj) 
   Set up object which should be used for callbacks */
PHP_FUNCTION(xml_set_object)
{
        xml_parser *parser;
        zval **pind, **mythis;

        if (ZEND_NUM_ARGS() != 2 ||
                zend_get_parameters_ex(2, &pind, &mythis) == FAILURE) {
                WRONG_PARAM_COUNT;
        }

        if ((*mythis)->type != IS_OBJECT) {
                php_error(E_WARNING,"arg 2 has wrong type");
                RETURN_FALSE;
        }

        if (! ParameterPassedByReference(ht,2)) {
                php_error(E_WARNING,"arg 2 not passed by reference");
                RETURN_FALSE;
        }

        ZEND_FETCH_RESOURCE(parser,xml_parser *,pind, -1, "XML Parser", le_xml_parser);

        if (parser->object) {
/*
                zval_del_ref(&parser->object);
*/
        }
        
        parser->object = *mythis;
/*
        zval_add_ref(&parser->object);
*/

        RETVAL_TRUE;
}
/* }}} */


>   For PHP3/PHP4 issues, I am wondering if we can create a
> 'compatability.php3' file which has implimentations (or stubs, if we can't
> duplicate functionality) for the PHP4 functions that are called and thus
> allow the rest of the code to run un-modified.  Those like me running PHP3
> would then just include this additional library.

Sounds like a good idea (Ajay?) I think that it won't happen for rc2 but
should happen for final, though I'd prefer to get workarounds in so we
don't have to stub out some functionality.

-n

-- 
........
nathan hruby
Webmaster: UGA Department of Drama and Theatre
Project Maintainer: phpSlash, Carousel
nh...@ar...
........