xoops-trackers Mailing List for XOOPS Web Application System

Bugs item #1440616, was opened at 2006-02-28 14:09
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430840&aid=1440616&group_id=41586

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Core -  install/upgrade
Group: XOOPS 2.4.x
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: blank page after upgrade

Initial Comment:
After upgrading my site from 2.2.3 to version 2.2.4
I did not see any homesite anymore. Internet explorer 
just show me a blank page

i copied all files from the upgrade directory html to 
the coresponding directories at my site.

My site is now up again, the only thing i had to do 
was to copy the "old" kernel/profilefield.php back 
again.

My main page shows some text made with the content 
module

dearest claus hviid denmark

http://www.claushviid.dk



 

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430840&aid=1440616&group_id=41586

Bugs item #1440060, was opened at 2006-02-27 21:16
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430840&aid=1440060&group_id=41586

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Core -  Core
Group: XOOPS 2.2.x
Status: Open
Resolution: None
Priority: 5
Submitted By: dejadingo (dejadingo)
Assigned to: Nobody/Anonymous (nobody)
Summary: xoops_version.php errors in Xoops2.2.3/2.2.4

Initial Comment:
modules/system/xoops_version.php
line 199

$modversion['profile']['field'][1]['options'] =
array('nest'=>_NESTED, 'flat'=>_FLAT, 'thread'=>_THREADED);

should be:

$modversion['profile']['field'][1]['options'] =
array(_NESTED => 'nest', _FLAT => 'flat', _THREADED =>
'thread');

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

modules/system/xoops_version.php
line 687

$modversion['config'][38]['options'] =
array("_MD_AM_METAOGEN" => "general",
"_MD_AM_METAO14YRS" => "14 years", "_MD_AM_METAOREST"
=> "restricted", "_MD_AM_METAOMAT", "mature");

should be

$modversion['config'][38]['options'] =
array("_MD_AM_METAOGEN" => "general",
"_MD_AM_METAO14YRS" => "14 years", "_MD_AM_METAOREST"
=> "restricted", "_MD_AM_METAOMAT" => "mature");



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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430840&aid=1440060&group_id=41586

Bugs item #1438677, was opened at 2006-02-25 20:36
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430840&aid=1438677&group_id=41586

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Core -  Core
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Ali Nili (irmtfan)
Assigned to: Nobody/Anonymous (nobody)
Summary: groups_users_link table was emptied by set session table

Initial Comment:
in Preferences --> General setting --> set USE CUSTOM
SESSION to "YES"

then groups_users_link table will be emptied.

xoops 2.2.4
also see this topic:
http://www.xoops.org/modules/newbb/viewtopic.php?viewmode=flat&topic_id=47370&forum=20

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430840&aid=1438677&group_id=41586

Bugs item #1438008, was opened at 2006-02-24 03:02
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430840&aid=1438008&group_id=41586

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Core -  Core
Group: XOOPS 2.0.x
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: global

Initial Comment:
Guys, please don't write the code like this

common.php

original:

require_once XOOPS_ROOT_PATH."/class/xoopssecurity.php";
$xoopsSecurity = new XoopsSecurity();
global $xoopsSecurity;

required by php 5.x.x
global $xoopsSecurity;
$xoopsSecurity = new XoopsSecurity();

because global keyword is equal to overrriding globals
like this, using a superglobal
$GLOBALS['xoopsSecurity'] =& $xoopsSecurity;

I think it is obvious enough.

Please, don't write so

mailto: ewger(at)desk.by


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

Comment By: Nobody/Anonymous (nobody)
Date: 2006-02-24 22:07

Message:
Logged In: NO 

XOOPS is older than PHP 5. So yes, you will find coding
practices that were perfectly ok for PHP 4, but which should
be re-examined for PHP 5.

Remember though, that the current XOOPS versions are not
ONLY for PHP 5, they need to also keep the support of PHP 4.
So removing all object references is not good, as it is only
automatically referenced in PHP 5.



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

Comment By: Nobody/Anonymous (nobody)
Date: 2006-02-24 14:09

Message:
Logged In: NO 

people, please read the manual

php engine is doing such thing like =& automatically. It is
clever enough.

if you try to include mainfile.php
from within a body of a
funciton {

}

such statements don't see globals
(see References with global and static variables) 
in http://www.php.net/global

You don't need to use every where =& .. 
Please, stop this! with object for example you don't need 
& cause objects are always references..


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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430840&aid=1438008&group_id=41586

Bugs item #1438008, was opened at 2006-02-24 03:02
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430840&aid=1438008&group_id=41586

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Core -  Core
Group: XOOPS 2.0.x
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: global

Initial Comment:
Guys, please don't write the code like this

common.php

original:

require_once XOOPS_ROOT_PATH."/class/xoopssecurity.php";
$xoopsSecurity = new XoopsSecurity();
global $xoopsSecurity;

required by php 5.x.x
global $xoopsSecurity;
$xoopsSecurity = new XoopsSecurity();

because global keyword is equal to overrriding globals
like this, using a superglobal
$GLOBALS['xoopsSecurity'] =& $xoopsSecurity;

I think it is obvious enough.

Please, don't write so

mailto: ewger(at)desk.by


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

Comment By: Nobody/Anonymous (nobody)
Date: 2006-02-24 14:09

Message:
Logged In: NO 

people, please read the manual

php engine is doing such thing like =& automatically. It is
clever enough.

if you try to include mainfile.php
from within a body of a
funciton {

}

such statements don't see globals
(see References with global and static variables) 
in http://www.php.net/global

You don't need to use every where =& .. 
Please, stop this! with object for example you don't need 
& cause objects are always references..


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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430840&aid=1438008&group_id=41586

Bugs item #1438171, was opened at 2006-02-24 07:35
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430840&aid=1438171&group_id=41586

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Core -  Core
Group: XOOPS 2.2.x
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: GZIP

Initial Comment:
http://www.xoops.org/modules/newbb/viewtopic.php?topic_id=47354&forum=2

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430840&aid=1438171&group_id=41586

Bugs item #1438008, was opened at 2006-02-24 03:02
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430840&aid=1438008&group_id=41586

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Core -  Core
Group: XOOPS 2.0.x
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: global

Initial Comment:
Guys, please don't write the code like this

common.php

original:

require_once XOOPS_ROOT_PATH."/class/xoopssecurity.php";
$xoopsSecurity = new XoopsSecurity();
global $xoopsSecurity;

required by php 5.x.x
global $xoopsSecurity;
$xoopsSecurity = new XoopsSecurity();

because global keyword is equal to overrriding globals
like this, using a superglobal
$GLOBALS['xoopsSecurity'] =& $xoopsSecurity;

I think it is obvious enough.

Please, don't write so

mailto: ewger(at)desk.by


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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430840&aid=1438008&group_id=41586

Feature Requests item #1437947, was opened at 2006-02-24 10:06
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1437947&group_id=41586

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Xoops_Gold (xoops_gold)
Assigned to: Nobody/Anonymous (nobody)
Summary: pm_link in xoops_user_profile

Initial Comment:
Hello!

I have placed a message in the xoops forum but no one
seemed to be interested to even discuss about it.

Here is my observation:

In the table xoops_user_profile, I had servere problems
importing the data in the following field:

pm_link

This is a system field containing a default standard
data as follows:

<a
href="javascript:openWithSelfMain('{X_URL}/modules/pm/pmlite.php?send2=1&to_userid={X_UID}',
'pmlite', 550, 450);" title="Eine Nachricht schreiben
an {X_UNAME}"><img
src="{X_URL}/modules/pm/images/pm.gif" alt="Eine
Nachricht schreiben an {X_UNAME}" /></a>

Now I find this fields a bit of too much. There could
be certainly a better way of generating a pop-up for
the pm_link, is'nt it? Looking at the extra-ordinary
work by Skalpa, Mitrandir, phppp, etc. I think this
link generation does not fit in the level of
programming what you all guys are doing!!!   ;-)

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1437947&group_id=41586

Feature Requests item #1437944, was opened at 2006-02-24 10:01
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1437944&group_id=41586

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Xoops_Gold (xoops_gold)
Assigned to: Nobody/Anonymous (nobody)
Summary: Seperation of Profile Preferences and Profile data

Initial Comment:
Hallo!

Now that there is a possibility of having custom fields
in the xoops_user_profile table, I see that it would be
very convinient to have a split in two following areas:

xoops_user_profile

AND

xoops_user_preferences

This kind of division may help at various levels. The
preferences are the xoops CMS specific ones that may be
stored seperately in a table that may be of really no
interest to other scrips interfacing with xoops.

Whereas if the profile data is stored into a seperate
table, it would help to export import and interface
with the data with much more ease. 

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1437944&group_id=41586

Bugs item #1437060, was opened at 2006-02-22 14:29
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430840&aid=1437060&group_id=41586

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Cannot join Xoops Forum

Initial Comment:
Sorry if this is the incorrect way to post but I 
couldn't find any other method of contact.  I cannot 
join your forum no what I do.  It keeps coming with 
the message "could not register new user".  I use 
Xoops on my web site and my concern is that other 
users cannot join my Xoops site either.

Barry

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430840&aid=1437060&group_id=41586

Feature Requests item #1435906, was opened at 2006-02-21 14:14
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1435906&group_id=41586

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Xoops_Gold (xoops_gold)
Assigned to: Nobody/Anonymous (nobody)
Summary: Profiles and Roles Manager

Initial Comment:
Hallo!

Currently we have in Xoops only Users and Groups
management.

However, I find it extremely helpful to have some more
tables that would offer more features as follows:

Companies table: Stores a company info...
Roles table: Stores function of a user, like
Administrator, Editor, etc...

and Profiles table: Stores function of a user, like
CEO, Director, etc...

The Profiles module offers an excellent programming
that simply needs to be extended through the CORE
operations. One of the most important part is the Field
Accessibility of this Profile module, which could also
be extended to the new functions.



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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1435906&group_id=41586

Feature Requests item #1435326, was opened at 2006-02-20 17:55
Message generated for change (Comment added) made by xoops_gold
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1435326&group_id=41586

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Core
Group: XOOPS 2.x
Status: Open
Resolution: None
Priority: 5
Submitted By: Xoops_Gold (xoops_gold)
Assigned to: Nobody/Anonymous (nobody)
Summary: 2.3: XoopsCore/CoreServices/Database.xofrm/legacy.php

Initial Comment:
Hallo Skalpa!

Was just going through the legacy.php and found
something that I just thought of drawing your
attention, if you could have a look, when you come out
of your developers submarine, as follows:

class xoops_db_Database_legacy extends
xoops_db_Database_mysql {


    /**
	 * Get field name
	 *
     * @param resource $result query result
     * @param int numerical field index
     * @return string
	 */
	function getFieldName($result, $offset)
	{
		return mysql_field_name($result, $offset);
	}

I suggest:
>>>

function getXoopsFieldName{
....blah
}

And add to it:

function getExternalFieldName{
...
connect to array_remote_db[xx]
...
Get Field Names of Table[xx] (as saved in the Pluggin DB)
...
}

Implications:

The Xoops would then have capacity to save names of the
database and tables to capture the fields.

Hence, all the Users and Groups table from any script
could be loaded by this function.

Use:

Xoops would then have potential to administrate any CMS
including to that of Joomla, provided Xoops remain the
Primary (Super) or Master CMS and others (for e.g.
Joomla) as a slave.

Thereafter, all the Users, Groups and Sessions table of
any CMS could be handled through a database mapping.

Does it make sense, dear captain?

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

>Comment By: Xoops_Gold (xoops_gold)
Date: 2006-02-20 18:07

Message:
Logged In: YES 
user_id=1329834

Further, was just going through more and found the following
in the file:

XOOPS / Frameworks / XoopsCore / CoreServices / Http.xofrm /
session.xoobj / handler-db.php

http://svn.berlios.de/viewcvs/xoops4/XoopsCore/branches/tasks/123542-admin/XOOPS/Frameworks/XoopsCore/CoreServices/Http.xofrm/session.xoobj/handler-db.php?view=markup

function write( $sessionId, $data ) {
    	$sessionId = $this->db->quote( $sessionId );
		$data = $this->db->quote( $data );
		$time = time();
    	
    	list( $count ) = $this->db->fetchRow( $this->db->query(
"SELECT COUNT(*) FROM `$this->tableName` WHERE
sess_id=$sessionId" ) );
 	
    	if ( $count > 0 ) {
			$sql = "UPDATE `$this->tableName` SET
sess_updated=$time,sess_data=$data WHERE sess_id=$sessionId";
    	} else {
    		$ip = $this->db->quote( $_SERVER['REMOTE_ADDR'] );
    		$sql = "INSERT INTO `$this->tableName`
(sess_id,sess_updated,sess_ip,sess_data) VALUES
($sessionId,$time,$ip,$data)";
    	}
		return $this->db->queryF( $sql );
    }

The mapping I suggested could be very simple and could be
implemented as follows:

    	list( $count ) = $this->db->fetchRow( $this->db->query(
"SELECT COUNT(*) FROM `$this->MAPPEDtableName` WHERE
sess_id=$sessionId" ) );
 	
    	if ( $count > 0 ) {
			$sql = "UPDATE `$this->MAPPEDtableName` SET
sess_updated=$time,sess_data=$data WHERE sess_id=$sessionId";
    	} else {
    		$ip = $this->db->quote( $_SERVER['REMOTE_ADDR'] );
    		$sql = "INSERT INTO `$this->MAPPEDtableName`
(sess_id,sess_updated,sess_ip,sess_data) VALUES
($sessionId,$time,$ip,$data)";
    	}

And the $this->MAPPEDtableName will go through all the
sessions table listed in the DB, update them.

Xoops shall provide a Gateway to all other CMS, as User
table is also mapped with this concept!



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

Comment By: Xoops_Gold (xoops_gold)
Date: 2006-02-20 17:57

Message:
Logged In: YES 
user_id=1329834

Ah!

I forgot to post the URL of the script. Thats here:

http://svn.berlios.de/viewcvs/xoops4/XoopsCore/branches/tasks/123542-admin/XOOPS/Frameworks/XoopsCore/CoreServices/Database.xofrm/legacy.php?view=markup

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1435326&group_id=41586

Feature Requests item #1435326, was opened at 2006-02-20 17:55
Message generated for change (Comment added) made by xoops_gold
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1435326&group_id=41586

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Core
Group: XOOPS 2.x
Status: Open
Resolution: None
Priority: 5
Submitted By: Xoops_Gold (xoops_gold)
Assigned to: Nobody/Anonymous (nobody)
Summary: 2.3: XoopsCore/CoreServices/Database.xofrm/legacy.php

Initial Comment:
Hallo Skalpa!

Was just going through the legacy.php and found
something that I just thought of drawing your
attention, if you could have a look, when you come out
of your developers submarine, as follows:

class xoops_db_Database_legacy extends
xoops_db_Database_mysql {


    /**
	 * Get field name
	 *
     * @param resource $result query result
     * @param int numerical field index
     * @return string
	 */
	function getFieldName($result, $offset)
	{
		return mysql_field_name($result, $offset);
	}

I suggest:
>>>

function getXoopsFieldName{
....blah
}

And add to it:

function getExternalFieldName{
...
connect to array_remote_db[xx]
...
Get Field Names of Table[xx] (as saved in the Pluggin DB)
...
}

Implications:

The Xoops would then have capacity to save names of the
database and tables to capture the fields.

Hence, all the Users and Groups table from any script
could be loaded by this function.

Use:

Xoops would then have potential to administrate any CMS
including to that of Joomla, provided Xoops remain the
Primary (Super) or Master CMS and others (for e.g.
Joomla) as a slave.

Thereafter, all the Users, Groups and Sessions table of
any CMS could be handled through a database mapping.

Does it make sense, dear captain?

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

>Comment By: Xoops_Gold (xoops_gold)
Date: 2006-02-20 17:57

Message:
Logged In: YES 
user_id=1329834

Ah!

I forgot to post the URL of the script. Thats here:

http://svn.berlios.de/viewcvs/xoops4/XoopsCore/branches/tasks/123542-admin/XOOPS/Frameworks/XoopsCore/CoreServices/Database.xofrm/legacy.php?view=markup

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1435326&group_id=41586

Feature Requests item #1435326, was opened at 2006-02-20 17:55
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1435326&group_id=41586

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Core
Group: XOOPS 2.x
Status: Open
Resolution: None
Priority: 5
Submitted By: Xoops_Gold (xoops_gold)
Assigned to: Nobody/Anonymous (nobody)
Summary: 2.3: XoopsCore/CoreServices/Database.xofrm/legacy.php

Initial Comment:
Hallo Skalpa!

Was just going through the legacy.php and found
something that I just thought of drawing your
attention, if you could have a look, when you come out
of your developers submarine, as follows:

class xoops_db_Database_legacy extends
xoops_db_Database_mysql {


    /**
	 * Get field name
	 *
     * @param resource $result query result
     * @param int numerical field index
     * @return string
	 */
	function getFieldName($result, $offset)
	{
		return mysql_field_name($result, $offset);
	}

I suggest:
>>>

function getXoopsFieldName{
....blah
}

And add to it:

function getExternalFieldName{
...
connect to array_remote_db[xx]
...
Get Field Names of Table[xx] (as saved in the Pluggin DB)
...
}

Implications:

The Xoops would then have capacity to save names of the
database and tables to capture the fields.

Hence, all the Users and Groups table from any script
could be loaded by this function.

Use:

Xoops would then have potential to administrate any CMS
including to that of Joomla, provided Xoops remain the
Primary (Super) or Master CMS and others (for e.g.
Joomla) as a slave.

Thereafter, all the Users, Groups and Sessions table of
any CMS could be handled through a database mapping.

Does it make sense, dear captain?

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1435326&group_id=41586

Bugs item #1434626, was opened at 2006-02-19 15:59
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430840&aid=1434626&group_id=41586

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Core -  Core
Group: XOOPS 2.2.x
Status: Open
Resolution: None
Priority: 5
Submitted By: Jano (j4n0)
Assigned to: Nobody/Anonymous (nobody)
Summary: Unable to send emails

Initial Comment:
To make the long story short, users of my site don't
receive validation emails after registration. After
entering all required data in registration form,
clicking submit button and confirming data shown in a
table by clicking next submit button I've got a message
confirming, that everything is ok and validation email
has been sent. But it never arrives. I've tried many
times using different browsers (Firefox, IE, Opera) and
different email addresses. It doesn't work at all.

Few words about my configuration:
I'm forced to use PHP mail(). I am using PHP 4,
unfortunately in safe-mode (mail() is available),
register_globals is turned OFF. My XOOPS version is 2.2.4.

I haven't found a solution to my problem, hoping I
don't ask an already answered question. I hope I'll get
some help soon. If you need any further details please
feel free to ask.

Kind regards,

Jano

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430840&aid=1434626&group_id=41586

Bugs item #1434502, was opened at 2006-02-19 00:14
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430840&aid=1434502&group_id=41586

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: modules packages

Initial Comment:
It looks like the modules packages for xoops 2.2 are
broken : I try download them from multiple mirror
locations with the same result : broken file :

uploads/dokuwiki/pages/wiki/playground.txt
uploads/dokuwiki/pages/wiki/syntax.txt
tar: Un bloc zéro solitaire repéré à 18511


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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430840&aid=1434502&group_id=41586

Bugs item #1433681, was opened at 2006-02-17 08:20
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430840&aid=1433681&group_id=41586

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Core -  Core
Group: XOOPS 2.2.x
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Forbidden 403

Initial Comment:
Xoops 2.2.4
Apache 1.3.33
PHP 4.3.11
MYSQL - 4.0.25-standard

I have been getting this error in many sections of my
site since upgrading.

I get it when a user tries to register, but only if I
have the Private messenger module installed.

I get it when trying to reply to a post in cbb 2.32 and
after upgrading to cbb 3.0.

There are other modules that will do it when I try to
adminisrate them.

Someone was saying that if they use the word wish with
a space after it it does it.

Someone thinks it is apache 1.3.33 because they have
the problem on a server with apache 1.3.33 but no
problem with apache 2

This problem in my opinion should take priority over
almost everything else, because you have a lot of sites
out there that are broken, and I think this is probably
the main cause of alot of problems.

Thank You,

John Mordo

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430840&aid=1433681&group_id=41586

Feature Requests item #1432728, was opened at 2006-02-16 10:23
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1432728&group_id=41586

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Xoops_Gold (xoops_gold)
Assigned to: Nobody/Anonymous (nobody)
Summary: REMOTE HOST ./. Auto Lockout feature

Initial Comment:
Hallo!

In the xoops_sessions the sess_ip is captured and
stored for that session.

Can this be taken forward to detect for each and every
call TOGATHER WITH COOKIES? Does this make sense at all?

I thought it can do the following:

New table:

xoops_sessions_track

This would then include all what the sess_id based
activity into it. Following is than possible:

sess_id sess_ip module_id page_id start_time end_time

Therefore DoS would become impossible "if and only if"

end_time - start_time = is less than x seconds...

It would then lockout the user! Also this would help
anathor possibility of locking out users if they tried
for entering their passwords for more than x times,
which could be configured from the admin.

Also it would be able to offer excellent statistics,
RIGHT FROM THE CORE.

Difference:

Modules making a call through SQL queries is different
than CORE registering where the user is at a given time!

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1432728&group_id=41586

Feature Requests item #1432036, was opened at 2006-02-15 10:30
Message generated for change (Comment added) made by xoops_gold
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1432036&group_id=41586

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Xoops_Gold (xoops_gold)
Assigned to: Nobody/Anonymous (nobody)
Summary: XOOPS CORE MANAGER: System functions!

Initial Comment:
Hallo all the core developers!

I would like to know the time frame of the new core, so
that the community of Xoops knows exactly how long do
they have to remain jealous of Joomla users! ;-)

I suggest therefore the following, as I love to see
those functions in xoops as well:

1. Whats there:
- Why do the module developers need to program each
time "save", "delete", "help", "new", etc like here:

http://demo.joomla.org/administrator/index2.php?option=com_categories&section=content

Those are really system functions. There could be a
hook to classes and if the module developers wanna use
them, they could really save their time. By this, one
achives an unified look in the administration.

2. Whats not there in Joomla:

- Group manager with access rights
- Subscriptions manager
- Site manager with access rights
- Universal category manager with access rights
- Menu manager with access rights
- Database mapping manager (use other CMS and standalone)
- Regions manager that mapps a user, products,
companies, etc with regions
- Cache manager
- Modules manager
- Pluggins manager
- User manager with complex access rights
- Permissions manager
- System core Installation manager
- System events manager
- Email manager
- Newsletter manager
- Database manager
- Support manager
- Hooks manager

There are so many functions that are not in Jommla
which are already in Xoops. But they are not programmed
to show up in a commercial way as in Joomla. It is just
the question of a new face and better shape of the core.

Thats my feature request:

Better administration of the core with many existing
and new functions.

I hope that the core team decides rather soon of how
the new administration look would be and which are the
functions that will crop up in time. The value of the
new core from the user point of view in this regards is
of prime importance as compared to a possible delay in
the development of a new Framework of Xoopsphere, or
something. This can be done but if it is at the cost of
time that the users has to wait, that would be a bit of
prolonged and tiresome waiting by us...

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

>Comment By: Xoops_Gold (xoops_gold)
Date: 2006-02-16 10:02

Message:
Logged In: YES 
user_id=1329834

Sorry about that...

Did not notice that this request got submitted twice...

I therefore request to delete or ignore it!

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1432036&group_id=41586

Feature Requests item #1432721, was opened at 2006-02-16 10:00
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1432721&group_id=41586

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Core
Group: XOOPS 2.x
Status: Open
Resolution: None
Priority: 5
Submitted By: Xoops_Gold (xoops_gold)
Assigned to: Nobody/Anonymous (nobody)
Summary: ENTITY MANAGER: Permissions Templates / Sub Groups

Initial Comment:
Hallo all!

Using cerberus tickiting as mentioned in my earlier
feature request, I saw that they have users that are
there and could be easily added to a company. That gave
me an idea as follows:

One cannot have the name of companies as Groups. Having
30.000 companies database for e.g. would mean so many
groups.

So:

It would then be necessary to have SUB GROUPS° within
GROUPS.

This will also open an new world to the features in
Xoops. This leads to one:many, many:many and mand:one
relationships in the core completely and fully developed.

I wonder if this could be achieved with the permission
templates shooting on the modules, groups and sub-groups!!!

Making an hypotheical example of cerberus, as I read
from the post out there as follows:

Group: Support Level Premium
Sub Group: Companies

Group: Editors
Sub Group: Article

Table xoops_companies
>>> com_id  com_legalname  com_address

Table xoops_entities
>>> mapp_id group_id subgroup_id

It is therefore, necessary to have an Entity manager in
the admin seperate to User manager...

I am very exicted about the permission template and am
eagerly waiting it to be implemented in the future
versions, especially in view of sub groups. Does any
any CMS ever created on earth have this feature?

Xoops does understand a group could also comprise one
person -> 1:1, Group with members 1:x. But sub-groups
will bring x:x (Group:Sub-Group) relation quality. And
clarity most of all!

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1432721&group_id=41586

Feature Requests item #1432020, was opened at 2006-02-15 10:05
Message generated for change (Comment added) made by xoops_gold
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1432020&group_id=41586

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 9
Submitted By: Xoops_Gold (xoops_gold)
Assigned to: phppp (phppp)
Summary: XOOPS CORE MANAGER: System functions!

Initial Comment:
Hallo all the core developers!

I would like to know the time frame of the new core, so
that the community of Xoops knows exactly how long do
they have to remain jealous of Joomla users! ;-)

I suggest therefore the following, as I love to see
those functions in xoops as well:

1. Whats there:
- Why do the module developers need to program each
time "save", "delete", "help", "new", etc like here:

http://demo.joomla.org/administrator/index2.php?option=com_categories&section=content

Those are really system functions. There could be a
hook to classes and if the module developers wanna use
them, they could really save their time. By this, one
achives an unified look in the administration.

2. Whats not there in Joomla:

- Group manager with access rights
- Subscriptions manager
- Site manager with access rights
- Universal category manager with access rights
- Menu manager with access rights
- Database mapping manager (use other CMS and standalone)
- Regions manager that mapps a user, products,
companies, etc with regions
- Cache manager
- Modules manager
- Pluggins manager
- User manager with complex access rights
- Permissions manager
- System core Installation manager
- System events manager
- Email manager
- Newsletter manager
- Database manager
- Support manager
- Hooks manager

There are so many functions that are not in Jommla
which are already in Xoops. But they are not programmed
to show up in a commercial way as in Joomla. It is just
the question of a new face and better shape of the core.

Thats my feature request:

Better administration of the core with many existing
and new functions.

I hope that the core team decides rather soon of how
the new administration look would be and which are the
functions that will crop up in time. The value of the
new core from the user point of view in this regards is
of prime importance as compared to a possible delay in
the development of a new Framework of Xoopsphere, or
something. This can be done but if it is at the cost of
time that the users has to wait, that would be a bit of
prolonged and tiresome waiting by us...

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

>Comment By: Xoops_Gold (xoops_gold)
Date: 2006-02-16 02:06

Message:
Logged In: YES 
user_id=1329834

Hallo phppp!

Ok, you asked about my technical taste. Here is my favorite
(DO not underestimate whats in there!):

Download Links 
http://www.cerberusweb.com/download_fetch.php?fv=gui

In this ZIP you will find the following files:
cerberus-gui/includes/cerberus-api/

>>> bitflags.php has UNIX style permissions
>>> /hash.php  >> How interesting!

cerberus-gui/public_gui/cer_PublicUser.class.php
Line132
.....function loadUsersByIds($ids = array()) {
Line 207
function _loadCustomFields() {

cerberus-gui/cerberus-api/login/cer_LoginPlugin.class.php
function getRemoteUserId() {  (Remote <> Local User mapping!)


Reading sessions:
cerberus-gui/gateway-api/functions/sessions.class.php
Line 44
function _read($session_cookie_name) {
.....$recordSet = $this->db->Execute >>> 

This program could check either local or remote through a
pluggin. I am converting a xoops pluggin to log...

Further, I like:
cerberus-gui/includes/functions/privileges.php

class privileges_obj { 
  var $acl_list;
...
  
  function privileges_obj()
  {
  	global $session; // clean up
  	$this->acl_list =
@$session->vars["login_handler"]->user_access->group_acl;
...
  }
  function has_restriction($bitfield,$bitgroup=BITGROUP_1)
  {
  	if($this->is_superuser==1) return false;
  	return $this->check_bit($bitfield, $bitgroup);
  }

Thats nice, is'nt it?

If you see how they use remote_user_ids, database_fields,
etc, you would see that Xoops is not too far from it whereas
Joomla is millions fathom away. Especially the groupping
structure in Mambo was phooh!

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

Comment By: Xoops_Gold (xoops_gold)
Date: 2006-02-15 10:09

Message:
Logged In: YES 
user_id=1329834

Hallo phppp!

This is the result of what I commented on the news of world
press:

http://www.xoops.org/modules/news/article.php?storyid=2848&com_id=26326&com_rootid=26326&com_mode=flat&com_order=0#comment26326

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1432020&group_id=41586

Bugs item #1432102, was opened at 2006-02-15 03:40
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430840&aid=1432102&group_id=41586

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Core -  Core
Group: XOOPS 2.4.x
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Redirect Error

Initial Comment:
i have notice the Reditect error and have solved the 
issue with this, aparently in the tmeplates the 
system_redirect.html was not finished, how ever the 
oflowing code below i used form the 
system_redirect.html from 2.031 (stable) and worked 
flawlessly mabey you guys could let every one knwo 
bout this issue or update ur 2.2.4 core and fix this 
directly! www.bgkiller.com xoops user!


Code----------------------------------------------
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; 
charset=<{$xoops_charset}>" />
<meta http-equiv="Refresh" content="<{$time}>; url=<
{$url}>" />
<title><{$xoops_sitename}></title>
<link rel="stylesheet" type="text/css" media="all" 
href="<{$xoops_themecss}>" />
</head>
<div style="text-align:center; background-color: 
transparent; border-top: 0px solid #FFFFFF; border-
left: 0px solid #FFFFFF; border-right: 0px solid 
#AAAAAA; border-bottom: 0px solid #AAAAAA; font-
weight : bold;">
  <h4><{$message}></h4>
  <p><{$lang_ifnotreload}></p>
</div>
<{if $xoops_logdump != ''}><div><{$xoops_logdump}
></div><{/if}>
</html>
code----------------------------------------------
old code only had color of text and 2 ofhte rlines 
with no redirect html definitions or coding, i 
replaced this and eveyrhting works flawlessly now :)

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430840&aid=1432102&group_id=41586

Feature Requests item #1432036, was opened at 2006-02-15 10:30
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1432036&group_id=41586

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Xoops_Gold (xoops_gold)
Assigned to: Nobody/Anonymous (nobody)
Summary: XOOPS CORE MANAGER: System functions!

Initial Comment:
Hallo all the core developers!

I would like to know the time frame of the new core, so
that the community of Xoops knows exactly how long do
they have to remain jealous of Joomla users! ;-)

I suggest therefore the following, as I love to see
those functions in xoops as well:

1. Whats there:
- Why do the module developers need to program each
time "save", "delete", "help", "new", etc like here:

http://demo.joomla.org/administrator/index2.php?option=com_categories&section=content

Those are really system functions. There could be a
hook to classes and if the module developers wanna use
them, they could really save their time. By this, one
achives an unified look in the administration.

2. Whats not there in Joomla:

- Group manager with access rights
- Subscriptions manager
- Site manager with access rights
- Universal category manager with access rights
- Menu manager with access rights
- Database mapping manager (use other CMS and standalone)
- Regions manager that mapps a user, products,
companies, etc with regions
- Cache manager
- Modules manager
- Pluggins manager
- User manager with complex access rights
- Permissions manager
- System core Installation manager
- System events manager
- Email manager
- Newsletter manager
- Database manager
- Support manager
- Hooks manager

There are so many functions that are not in Jommla
which are already in Xoops. But they are not programmed
to show up in a commercial way as in Joomla. It is just
the question of a new face and better shape of the core.

Thats my feature request:

Better administration of the core with many existing
and new functions.

I hope that the core team decides rather soon of how
the new administration look would be and which are the
functions that will crop up in time. The value of the
new core from the user point of view in this regards is
of prime importance as compared to a possible delay in
the development of a new Framework of Xoopsphere, or
something. This can be done but if it is at the cost of
time that the users has to wait, that would be a bit of
prolonged and tiresome waiting by us...

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1432036&group_id=41586

Feature Requests item #1432020, was opened at 2006-02-15 10:05
Message generated for change (Comment added) made by xoops_gold
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1432020&group_id=41586

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 9
Submitted By: Xoops_Gold (xoops_gold)
Assigned to: phppp (phppp)
Summary: XOOPS CORE MANAGER: System functions!

Initial Comment:
Hallo all the core developers!

I would like to know the time frame of the new core, so
that the community of Xoops knows exactly how long do
they have to remain jealous of Joomla users! ;-)

I suggest therefore the following, as I love to see
those functions in xoops as well:

1. Whats there:
- Why do the module developers need to program each
time "save", "delete", "help", "new", etc like here:

http://demo.joomla.org/administrator/index2.php?option=com_categories&section=content

Those are really system functions. There could be a
hook to classes and if the module developers wanna use
them, they could really save their time. By this, one
achives an unified look in the administration.

2. Whats not there in Joomla:

- Group manager with access rights
- Subscriptions manager
- Site manager with access rights
- Universal category manager with access rights
- Menu manager with access rights
- Database mapping manager (use other CMS and standalone)
- Regions manager that mapps a user, products,
companies, etc with regions
- Cache manager
- Modules manager
- Pluggins manager
- User manager with complex access rights
- Permissions manager
- System core Installation manager
- System events manager
- Email manager
- Newsletter manager
- Database manager
- Support manager
- Hooks manager

There are so many functions that are not in Jommla
which are already in Xoops. But they are not programmed
to show up in a commercial way as in Joomla. It is just
the question of a new face and better shape of the core.

Thats my feature request:

Better administration of the core with many existing
and new functions.

I hope that the core team decides rather soon of how
the new administration look would be and which are the
functions that will crop up in time. The value of the
new core from the user point of view in this regards is
of prime importance as compared to a possible delay in
the development of a new Framework of Xoopsphere, or
something. This can be done but if it is at the cost of
time that the users has to wait, that would be a bit of
prolonged and tiresome waiting by us...

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

>Comment By: Xoops_Gold (xoops_gold)
Date: 2006-02-15 10:09

Message:
Logged In: YES 
user_id=1329834

Hallo phppp!

This is the result of what I commented on the news of world
press:

http://www.xoops.org/modules/news/article.php?storyid=2848&com_id=26326&com_rootid=26326&com_mode=flat&com_order=0#comment26326

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1432020&group_id=41586

Feature Requests item #1432020, was opened at 2006-02-15 10:05
Message generated for change (Settings changed) made by xoops_gold
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1432020&group_id=41586

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
>Priority: 9
Submitted By: Xoops_Gold (xoops_gold)
>Assigned to: phppp (phppp)
Summary: XOOPS CORE MANAGER: System functions!

Initial Comment:
Hallo all the core developers!

I would like to know the time frame of the new core, so
that the community of Xoops knows exactly how long do
they have to remain jealous of Joomla users! ;-)

I suggest therefore the following, as I love to see
those functions in xoops as well:

1. Whats there:
- Why do the module developers need to program each
time "save", "delete", "help", "new", etc like here:

http://demo.joomla.org/administrator/index2.php?option=com_categories&section=content

Those are really system functions. There could be a
hook to classes and if the module developers wanna use
them, they could really save their time. By this, one
achives an unified look in the administration.

2. Whats not there in Joomla:

- Group manager with access rights
- Subscriptions manager
- Site manager with access rights
- Universal category manager with access rights
- Menu manager with access rights
- Database mapping manager (use other CMS and standalone)
- Regions manager that mapps a user, products,
companies, etc with regions
- Cache manager
- Modules manager
- Pluggins manager
- User manager with complex access rights
- Permissions manager
- System core Installation manager
- System events manager
- Email manager
- Newsletter manager
- Database manager
- Support manager
- Hooks manager

There are so many functions that are not in Jommla
which are already in Xoops. But they are not programmed
to show up in a commercial way as in Joomla. It is just
the question of a new face and better shape of the core.

Thats my feature request:

Better administration of the core with many existing
and new functions.

I hope that the core team decides rather soon of how
the new administration look would be and which are the
functions that will crop up in time. The value of the
new core from the user point of view in this regards is
of prime importance as compared to a possible delay in
the development of a new Framework of Xoopsphere, or
something. This can be done but if it is at the cost of
time that the users has to wait, that would be a bit of
prolonged and tiresome waiting by us...

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430843&aid=1432020&group_id=41586