xoops-development — For those who are interested in XOOPS development

[Xoops-development] xoops.org stats

[R. M. v. D. <mv...@ca...>]

Hello,

I was just wondering if someone could quickly let me know a few stats of
the xoops.org site.  I am trying to help someone who is getting an 'out of
memory' error with an 8M limit (php.ini) while loading a user
administration page (just over 700 users).

This seems odd for such a small number of users, so I am just wondering
what the xoops.org setup is (same 8M limit?), and how many users there
are.  I assume there are no bugs on the 'Edit User' page from System
Administration??

While I'm at it... any of you guys know a good way from PHP to show the
amount of memory being used by a script?  I couldn't find any functions,
but maybe I'm just blind. :-)

Thanks very much,

Mike

Re: [Xoops-development] new version XoopsObjectHandler

[Martin K. <Mar...@bl...>]

"K. Ono" <on...@xo...> writes on 
Fri, 06 Jun 2003 05:22:59 +0200 (METDST):

> Hi,
> 
> Did you have problem using the criteria class?


Not in a real use. I have had a look at the class(es) itself/themselves and browsed a few occurences where it is in use. So perhaps I am missing something.

What I wanted to do is:

Set a limit (or start and limit) by itself (no where clause). I didn't see a way to achieve this, so I did fetch() this way.

I also wasn't sure if I could add multiple sort columns (with separate sort order). Or how to use multiple group by columns. I need some time to play with the class.

Regards,
Masi 

Re: [Xoops-development] new version XoopsObjectHandler

[K. O. <on...@xo...>]

Hi,

Did you have problem using the criteria class?

Thanks and regards,
K. Ono

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

    /**
     * load objects from database
     *
     * Note: doesn't use Criteria because that class needs a WHERE clause
     *
     * @param int    $limit
     * @param int    $start
     * @param bool   $id_as_key   should the ID be used as the array key?
     * @param string $sql_clause  arbitrary where/order by clause (overrides
default sorting)
     * @return array array of references to objects
     */
    function &fetch($limit=0, $start=0, $id_as_key=false, $sql_clause=null)
{
 $objects = array();
 $limit = $start = 0;
 $sql = 'SELECT * FROM '.$this->table;
 if ($sql_clause) {
     $sql .= ' '.$sql_clause;
 }
 else {
     if ($this->sort) {
  // could do caching of ORDER BY clause
  $sql .= ' ORDER BY ';
  $scnt = count($this->sort);
  for ($i=0; $i < $scnt; $i++) {
      $sql .= $this->sort[$i].' '.$this->sortOrder[$i];
      if ($i+1 < $scnt)
   $sql .= ', ';
  }
     }
 }
 $result = $this->db->query($sql, $limit, $start);
 if (!$result) {
     return $objects;
 }
 while ($myrow = $this->db->fetchArray($result)) {
     $object = new $this->class();
     $object->assignVars($myrow);
     if (!$id_as_key) {
  $objects[] =& $object;
            } else {
                $objects[$myrow[$this->id]] =& $object;
            }
     unset($object);
 }
 return $objects;
    }

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

Re: [Xoops-development] ideas for XoopsObject

[K. O. <on...@xo...>]

Hi,

Looks good.. I will merge these on CVS.

Thanks and regards,
K. Ono

----- Original Message -----
From: "Martin Kutschker" <Mar...@bl...>
To: <xoo...@li...>
Sent: Friday, June 06, 2003 12:51 AM
Subject: [Xoops-development] ideas for XoopsObject


> <p>More convenience...</p>
>
> <pre>
> class XoopsObject {
>
> ...
>
> var $tplVars = array();
>
> ...
>
> /**
> * Set variable names for Smarty template assignation (see assignTpl)
> *
> * Note: should be set in the constructor of the class
> *
> * @param mixed $vars array of variable names
> */
> function setTplVars(&$vars) {
> foreach ($vars as $var) {
> $this->tplVars[] = $var;
> }
> }
>
> /**
> * Assign variables to Smarty template in a batch(see setTplVars)
> *
> * @param object &$tpl reference to a {@link Smarty} object
> * @see Smarty
> */
> function assignTpl(&$tpl) {
> foreach ($this->tplVars as $var) {
> $tpl->assign($var, $this->getVar($var));
> }
> }
>
> /**
> * Assign values to multiple variables in a batch
> *
> * Meant for a CGI contenxt:
> * - prefixed CGI args are considered save
> * - avoids polluting of namespace with CGI args
> *
> * Note: 'xo' stands for 'XOOPS object', it's shorter than eg 'xoops_' :-)
> *
> * @access private
> * @param array $var_arr associative array of values to assign
> * @param string $pref prefix (only keys starting with the prefix will be
set)
> */
> function setFormVars($var_arr=null, $pref='xo_', $not_gpc=false) {
> $len = strlen($pref);
> foreach ($var_arr as $key => $value) {
> if ($pref == substr($key,0,$len)) {
> $this->setVar(substr($key,$len), $value, $not_gpc);
> }
> }
> }
> }
> </pre>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
> thread debugger on the planet. Designed with thread debugging features
> you've never dreamed of, try TotalView 6 free at www.etnus.com.
> _______________________________________________
> Xoops-development mailing list
> Xoo...@li...
> https://lists.sourceforge.net/lists/listinfo/xoops-development
>

[Xoops-development] ideas for XoopsObject

[Martin K. <Mar...@bl...>]

<p>More convenience...</p>

<pre>
class XoopsObject {

...

var $tplVars = array();

...

/**
* Set variable names for Smarty template assignation (see assignTpl)
*
* Note: should be set in the constructor of the class
*
* @param mixed $vars array of variable names
*/
function setTplVars(&$vars) {
foreach ($vars as $var) {
$this->tplVars[] = $var;
}
}

/**
* Assign variables to Smarty template in a batch(see setTplVars)
*
* @param object &$tpl reference to a {@link Smarty} object
* @see Smarty
*/
function assignTpl(&$tpl) {
foreach ($this->tplVars as $var) {
$tpl->assign($var, $this->getVar($var));
}
}

/**
* Assign values to multiple variables in a batch
*
* Meant for a CGI contenxt:
* - prefixed CGI args are considered save
* - avoids polluting of namespace with CGI args
*
* Note: 'xo' stands for 'XOOPS object', it's shorter than eg 'xoops_' :-)
*
* @access private
* @param array $var_arr associative array of values to assign
* @param string $pref prefix (only keys starting with the prefix will be set)
*/
function setFormVars($var_arr=null, $pref='xo_', $not_gpc=false) {
$len = strlen($pref);
foreach ($var_arr as $key => $value) {
if ($pref == substr($key,0,$len)) {
$this->setVar(substr($key,$len), $value, $not_gpc);
}
}
}
}
</pre> 

Re: [Xoops-development] Re: ping

[Martin K. <Mar...@bl...>]

"K. Ono" <on...@xo...> writes on 
Wed, 04 Jun 2003 02:23:18 +0200 (METDST):

> 
> I have not received the object handler wrapper codes yet though, so
> maybe this is what we should discuss in detail here? ;-)


I have posted some updates in the forum. But I guess it'd be better to repost a full version here (in a different mail).


> Currently, there is no detailed roadmap other than the one on the wiki
> site (though that doesn't look like a good one), and the development
> has virtually stopped due to the lack of time for developers to code,
> but we will accept patches and give out commit access to active
> contributors as needed.


Ok, then I continue posting as my own time permits. Though some of my ideas would rather fit into rather into 2.1 than the current code. Could we have a new CVS repository for 2.1? Perhaps without any modules, so new ideas like "super-sections" can be ported bit by bit?

Masi 

Re: [Xoops-development] Re: wiki.xoops.org problem

[R. M. v. D. <mv...@ca...>]

On Thu, 5 Jun 2003, K. Ono wrote:
>
> Thanks. Or maybe I should just add the Rewrite* rules under the virtualhost
> directive
> for wiki.xoops.org. ;-)

I guess that would probably be easiest :).  I had a look at the wakka code
and it would require a number of changes... on my first quick attempt, I
wasn't able to get it working for all wiki actions...

Mike

Re: [Xoops-development] Re: wiki.xoops.org problem

[K. O. <on...@xo...>]

Hi,

Thanks. Or maybe I should just add the Rewrite* rules under the virtualhost
directive
for wiki.xoops.org. ;-)

Thanks and regards,
k. Ono

----- Original Message -----
From: "R. Michael van Dam" <mv...@ca...>
To: <xoo...@li...>
Sent: Wednesday, June 04, 2003 10:53 AM
Subject: Re: [Xoops-development] Re: wiki.xoops.org problem


>
> Hi,
>
> I've tried the module and had a little trouble getting it to run.  I have
> lots of experience with the standalone phpwiki though...
>
> Phpwiki has some nice features.  It is quite a bit slower than wakka, but
> I'd say more powerful and extendible.  It doesn't have a good system for
> access control though (but maybe not needed).
>
> One problem is that the markup is different... so would require a certain
> amount of re-editing pages (or a conversion script).
>
> I can have a look at wakka... maybe there is a simple fix to the 'history'
> problem.
>
> Regards,
> Mike
>
>
>
> On Wed, 4 Jun 2003, K. Ono wrote:
>
> > Hi,
> >
> > I guess you are right. It seems that wakkawiki relies on .htaccess to do
the
> > rewrite
> > of requested URI?
> > The xoops.org server has .htaccess disabled for better performance, so I
> > guess
> > that is where the problem is.
> >
> > Has anyone used the phpWiki module by danielblues? If it works fine,
maybe
> > we should install the mod on www.xoops.org and move the contents on the
wiki
> > site to the module.
> >
> > Thanks and regards,
> > K. Ono
> >
> >
> >
> > > My apologies for mailing to the whole dev list...  Who is reponsible
for
> > >  maintenance of the wiki?
> > >
> > >  There is currently a problem that you cannot edit an old version of a
> > page
> > >  (e.g. to rollback to a previous version after a page is
> > >  broken/vandalized).
> > >
> > >  For example, from the history page, when you click on one of the old
> > >  versions,
> > >
> > >
> > >
> >
http://wiki.xoops.org/wakka.php?wakka=HomePage/show?time=2003-05-30+06%3A52%
> > > 3A21
> > >
> > >  you get the error message: "Unknown method "page/show?time=2003-05-30
> > >  06:52:21.php".
> > >
> > >  Just a stab in the dark: is this perhaps a mod_rewrite problem?
> > >
> > >  I think this is an essential feature for restoring wiki pages. (Since
the
> > >  'diff' page only gives you HTML and doesn't give you the markup, you
> > can't
> > >  really cut and paste the desired text from there.)  Anyways, just
wanted
> > >  to bring this to the relevant person's attention in case they are not
yet
> > >  aware of the problem.
> > >
> > >  Regards,
> > >  Mike
> > >
> > >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
> > thread debugger on the planet. Designed with thread debugging features
> > you've never dreamed of, try TotalView 6 free at www.etnus.com.
> > _______________________________________________
> > Xoops-development mailing list
> > Xoo...@li...
> > https://lists.sourceforge.net/lists/listinfo/xoops-development
> >
> >
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
> thread debugger on the planet. Designed with thread debugging features
> you've never dreamed of, try TotalView 6 free at www.etnus.com.
> _______________________________________________
> Xoops-development mailing list
> Xoo...@li...
> https://lists.sourceforge.net/lists/listinfo/xoops-development
>

Re: [Xoops-development] Re: wiki.xoops.org problem

[R. M. v. D. <mv...@ca...>]

Hi,

I've tried the module and had a little trouble getting it to run.  I have
lots of experience with the standalone phpwiki though...

Phpwiki has some nice features.  It is quite a bit slower than wakka, but
I'd say more powerful and extendible.  It doesn't have a good system for
access control though (but maybe not needed).

One problem is that the markup is different... so would require a certain
amount of re-editing pages (or a conversion script).

I can have a look at wakka... maybe there is a simple fix to the 'history'
problem.

Regards,
Mike



On Wed, 4 Jun 2003, K. Ono wrote:

> Hi,
>
> I guess you are right. It seems that wakkawiki relies on .htaccess to do the
> rewrite
> of requested URI?
> The xoops.org server has .htaccess disabled for better performance, so I
> guess
> that is where the problem is.
>
> Has anyone used the phpWiki module by danielblues? If it works fine, maybe
> we should install the mod on www.xoops.org and move the contents on the wiki
> site to the module.
>
> Thanks and regards,
> K. Ono
>
>
>
> > My apologies for mailing to the whole dev list...  Who is reponsible for
> >  maintenance of the wiki?
> >
> >  There is currently a problem that you cannot edit an old version of a
> page
> >  (e.g. to rollback to a previous version after a page is
> >  broken/vandalized).
> >
> >  For example, from the history page, when you click on one of the old
> >  versions,
> >
> >
> >
> http://wiki.xoops.org/wakka.php?wakka=HomePage/show?time=2003-05-30+06%3A52%
> > 3A21
> >
> >  you get the error message: "Unknown method "page/show?time=2003-05-30
> >  06:52:21.php".
> >
> >  Just a stab in the dark: is this perhaps a mod_rewrite problem?
> >
> >  I think this is an essential feature for restoring wiki pages. (Since the
> >  'diff' page only gives you HTML and doesn't give you the markup, you
> can't
> >  really cut and paste the desired text from there.)  Anyways, just wanted
> >  to bring this to the relevant person's attention in case they are not yet
> >  aware of the problem.
> >
> >  Regards,
> >  Mike
> >
> >
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
> thread debugger on the planet. Designed with thread debugging features
> you've never dreamed of, try TotalView 6 free at www.etnus.com.
> _______________________________________________
> Xoops-development mailing list
> Xoo...@li...
> https://lists.sourceforge.net/lists/listinfo/xoops-development
>
>

[Xoops-development] Re: wiki.xoops.org problem

[K. O. <on...@xo...>]

Hi,

I guess you are right. It seems that wakkawiki relies on .htaccess to do the
rewrite
of requested URI?
The xoops.org server has .htaccess disabled for better performance, so I
guess
that is where the problem is.

Has anyone used the phpWiki module by danielblues? If it works fine, maybe
we should install the mod on www.xoops.org and move the contents on the wiki
site to the module.

Thanks and regards,
K. Ono



> My apologies for mailing to the whole dev list...  Who is reponsible for
>  maintenance of the wiki?
>
>  There is currently a problem that you cannot edit an old version of a
page
>  (e.g. to rollback to a previous version after a page is
>  broken/vandalized).
>
>  For example, from the history page, when you click on one of the old
>  versions,
>
>
>
http://wiki.xoops.org/wakka.php?wakka=HomePage/show?time=2003-05-30+06%3A52%
> 3A21
>
>  you get the error message: "Unknown method "page/show?time=2003-05-30
>  06:52:21.php".
>
>  Just a stab in the dark: is this perhaps a mod_rewrite problem?
>
>  I think this is an essential feature for restoring wiki pages. (Since the
>  'diff' page only gives you HTML and doesn't give you the markup, you
can't
>  really cut and paste the desired text from there.)  Anyways, just wanted
>  to bring this to the relevant person's attention in case they are not yet
>  aware of the problem.
>
>  Regards,
>  Mike
>
>

[Xoops-development] Re: ping

[K. O. <on...@xo...>]

Hi,

I am sorry for the late response. I didn't know that the ML Administrator
doesn't get signed up automatically to the ML. ;-p

I've seen your patches and posts at the forums, and some of them I have
merged
with the codes on CVS, some of them I haven't had the time to take a look in
detail..
I have not received the object handler wrapper codes yet though, so maybe
this is
what we should discuss in detail here? ;-)

Currently, there is no detailed roadmap other than the one on the wiki site
(though that doesn't look like a good one), and the development has
virtually stopped due to the lack of time for developers to code, but we
will accept patches and give out commit access to active contributors as
needed.

Thanks and regards,
K. Ono

----- Original Message -----
From: "K. Ono" <on...@xo...>
To: <on...@xo...>
Sent: Wednesday, June 04, 2003 8:01 AM
Subject: ping


> Hi!
>
>  I subsrcibed a while ago and thought I'd lurk a bit. Is something wrong
or
> is this a very
> low-traffic list? Fact is I got no mail since my subscription on May 15.
>
>  It might have been noticed I am playing busy body at the XOOPS site. I
have
> already posted
> or filed some enhancements (or what I percieve them to be) of the XOOPS
> code. My goals are
> convenience for module authors and a code clean up (more OO, less
includes).
>
>  Is there still anyone out there? Anyone interesting in getting work done
in
> that direction?
>
>  If yes, I'd be glad if anyone could point out the general directions and
> plans for 2.1 and
> beyond.
>
>  Thanx and regards,
>  Masi
>
>

[Xoops-development] wiki.xoops.org problem

[Michael v. D. <mv...@th...>]

My apologies for mailing to the whole dev list...  Who is reponsible for 
maintenance of the wiki?

There is currently a problem that you cannot edit an old version of a page 
(e.g. to rollback to a previous version after a page is 
broken/vandalized).

For example, from the history page, when you click on one of the old 
versions,

http://wiki.xoops.org/wakka.php?wakka=HomePage/show?time=2003-05-30+06%3A52%3A21

you get the error message: "Unknown method "page/show?time=2003-05-30 
06:52:21.php".

Just a stab in the dark: is this perhaps a mod_rewrite problem?

I think this is an essential feature for restoring wiki pages. (Since the 
'diff' page only gives you HTML and doesn't give you the markup, you can't 
really cut and paste the desired text from there.)  Anyways, just wanted 
to bring this to the relevant person's attention in case they are not yet 
aware of the problem. 

Regards,
Mike

[Xoops-development] ping

[Martin K. <Mar...@bl...>]

Hi!

I subsrcibed a while ago and thought I'd lurk a bit. Is something wrong or is this a very low-traffic list? Fact is I got no mail since my subscription on May 15.

It might have been noticed I am playing busy body at the XOOPS site. I have already posted or filed some enhancements (or what I percieve them to be) of the XOOPS code. My goals are convenience for module authors and a code clean up (more OO, less includes).

Is there still anyone out there? Anyone interesting in getting work done in that direction?

If yes, I'd be glad if anyone could point out the general directions and plans for 2.1 and beyond.

Thanx and regards,
Masi