XOOPS 2.0.10 BETA Released - XOOPS - XOOPS News

XOOPS

News

News World of XOOPS Developers Hacks Themes Archive Submit News

XOOPS: XOOPS 2.0.10 BETA Released

Posted by: MithrandirOn 2005/3/26 15:39:57 17075 reads

The XOOPS Core Development Team brings you a beta version of the next step in XOOPS Development.

XOOPS version 2.0.10 beta is a security-improving release that lessens the use of fopen with URLs and brings a completely new tool for securing modules against CSRF attacks: The XoopsSecurity class.

This is just a beta for now, since the token system still needs some testing, but provided we get enough positive feedback, a final 2.0.10 release should be released within 1-2 weeks.

This release contains files for the core-included versions of News and Newbb (1.1 and 1, respectively). If you use Newbb 2 and/or News 1.2 or later, you should not upload the files in modules/news and modules/newbb as they will mess up these modules.

Xoops 2.0.10 Beta Full (.tar.gz)
Xoops 2.0.10 Beta Full (.zip)
Xoops 2.0.9.3 to 2.0.10 Beta Patch (.tar.gz)
Xoops 2.0.9.3 to 2.0.10 Beta Patch (.zip)

====
XoopsSecurity
====
The new class for handling security handles some routines including checking the HTTP REFERER and global variable contamination by request parameters.

It also introduces a token system for securing forms against CSRF attacks.

The comments are owned by the author. We aren't responsible for their content.

Re: XOOPS 2.0.10 BETA Released

Peekay Published 03/26/2005 15:43 XOOPS is my life! Joined 11/20/2004 Comments 2335

Congratulations! Look forward to trying this out.

Re: XOOPS 2.0.10 BETA Released

maumed Published 03/26/2005 15:54 Just popping in Joined 10/18/2004 Comments 50

Congrats for the great work!

[]s
Mauricio

Re: XOOPS 2.0.10 BETA Released

rowdie Published 03/26/2005 16:17 Just can't stay away Joined 07/21/2004 Comments 846

Thanks for all the hard work. I'm looking forward to using the new token system

A suggestion (indirectly related):
Is it possible for the core team to also release a full XOOPS 2.0.9.3 core version? The upgrade from 2.0.9.3 to 2.0.10 Beta is confusing if people don't know about the security patch. And it makes little sense for new users to have to patch a freshly downloaded 'stable' core release.

Re: XOOPS 2.0.10 BETA Released

Mithrandir Published 03/26/2005 16:19 Updated 03/26/2005 18:49 XOOPS is my life! Joined 06/21/2003 Comments 6320

Gahh.. knew I forgot something.

I'll put the 2.0.9.3 patch into the stable 2.0.10 patch so it can be used for upgrading from both 2.0.9.2 and 2.0.9.3

[size=x-small]Edited: 2.0.10 PATCH naturally[/size]

Re: XOOPS 2.0.10 BETA Released

rowdie Published 03/26/2005 16:46 Just can't stay away Joined 07/21/2004 Comments 846

Thankyou, that will solve the upgrade problem. But I still would like to see a full XOOPS 2.0.9.3 listed as the latest stable release. This beta release will become the stable release soon, which is great, but in the meantime people are downloading XOOPS and having to patch it before they get to a true 'stable' version. It's not right

Re: XOOPS 2.0.10 BETA Released

Speed Published 03/26/2005 17:15 Quite a regular Joined 05/18/2004 Comments 310

Does this work with Protector or does it replace Protector? Thanks for the security update!

Re: XOOPS 2.0.10 BETA Released

blacKurd Published 03/26/2005 18:35 Just popping in Joined 03/06/2005 Comments 6

Great work!
Thanks...

Re: XOOPS 2.0.10 BETA Released

alitan Published 03/26/2005 18:53 Quite a regular Joined 03/14/2004 Comments 399

Hi
Spacial thanks to XOOPS Core Team, for their hard work.However, I have two question now;
-- After downloading the patch for upgrading XOOPS 2.0.9.3, One thing attracted My attention, and that was that, some modules' files were replaced (Including Newbb v1, and I think news 1.1), Now I want to know that, people who use Newbb v2.0.2 and News 1.3, what should they do?(including myself), these files are part of the last and old versions of News and Newbb modules and I think if I replace them, they will not work.
-- Another question is when the new versions of the default modules will be included in the XOOPS package? (such as newbb v 2.0.2 and News 1.3)

Again thanks for your great work.

Re: XOOPS 2.0.10 BETA Released

Mithrandir Published 03/26/2005 19:10 XOOPS is my life! Joined 06/21/2003 Comments 6320

1: Yes, they are for the versions included with the core. I.e. version 1.1 of News and Newbb 1

If you have Newbb 2 you will have to wait for the Newbb team to implement this. News 1.3 already has its own ticket system implemented.

2: The new versions of News and Newbb will not be included in a core package. XOOPS 2.0.10 will be the last core release with modules included. Instead we will make module packages targeting specific areas.

Re: XOOPS 2.0.10 BETA Released

Pnooka Published 03/26/2005 19:20 Just popping in Joined 07/16/2004 Comments 68

The only problem is that this patch killed all my php blocks. I have a couple straight php blocks with some modules, after the test upgrade they are all gone.

Re: XOOPS 2.0.10 BETA Released

whitedragon Published 03/26/2005 19:28 Just popping in Joined 08/27/2004 Comments 39

Well, the new XOOPS is great and works nice, but I found a stupid bug. When you log out, you see that it prints out something like: “You are now logged out somename. Thank you for your visit to our site……..”. Well, the problem is that it does not print the name of user ( that “somename” in my example) but it prints
. How to solve this?
Thank you!

Re: XOOPS 2.0.10 BETA Released

Mithrandir Published 03/26/2005 19:34 XOOPS is my life! Joined 06/21/2003 Comments 6320

That's weird. Any php debug errors (@ both of you)

Re: XOOPS 2.0.10 BETA Released

whitedragon Published 03/26/2005 19:41 Updated 03/26/2005 20:12 Just popping in Joined 08/27/2004 Comments 39

Ok, now it's really weird. No php errors, not a single one.

--edit--
I checked the user.php and language user.php but they are the same as before so I don’t have an idea where’s the problem.

Re: XOOPS 2.0.10 BETA Released

Pnooka Published 03/26/2005 19:47 Just popping in Joined 07/16/2004 Comments 68

No php debug errors at all, block showing title only. The content is gone completely, it's very strange.

Re: XOOPS 2.0.10 BETA Released

webfmpl Published 03/26/2005 20:19 Updated 03/26/2005 21:22 Just popping in Joined 12/03/2004 Comments 19

After this upgrade I can`t create my own blocks and I don`t see early created custom blocks (HTML and auto-formated).
Greets

Re: XOOPS 2.0.10 BETA Released

Mithrandir Published 03/26/2005 20:35 XOOPS is my life! Joined 06/21/2003 Comments 6320

OK, so there seems to be some problems with

a) Custom blocks
b) Logout

I'll check it out tomorrow. Thank you for reporting this.

Re: XOOPS 2.0.10 BETA Released

zimmi88 Published 03/26/2005 21:15 Just popping in Joined 03/09/2005 Comments 57

Hi! Thanks for the new release. Besides the two bugs already mentioned, another bug I've come across is that when XOOPS generates a popup, the mainpage changes to a page with the word "[object]" on it.
Once again, thanks for the new release!
-zimmi88 =)

Re: XOOPS 2.0.10 BETA Released

Mithrandir Published 03/26/2005 21:44 XOOPS is my life! Joined 06/21/2003 Comments 6320

1) Custom blocks - bug located and will be fixed
2) Logout message - investigation in progress
3) Popup changes main window - Will investigate

Thanks for the feedback.

Re: XOOPS 2.0.10 BETA Released

Gruby Published 03/27/2005 6:30 Just popping in Joined 11/06/2003 Comments 16

there`s a bug with the site search, too, i think. i cant search anymore, allways get "please fill in all data..", but theres data already in :)

Re: XOOPS 2.0.10 BETA Released

studioC Published 03/27/2005 8:22 Updated 03/27/2005 8:25 Friend of XOOPS Joined 12/07/2003 Comments 922

hello jan,

on a fresh install imagemanager doesn't store anything (no categories) ... and no errors on debug ...

michael

Re: XOOPS 2.0.10 BETA Released

sylvainb Published 03/27/2005 8:24 Not too shy to talk Joined 02/11/2003 Comments 168

Hello Mith,

Quote:

1) Custom blocks - bug located and will be fixed

That's ok but there seems to be the same troubles with some modules (xp-weather, eCal at least).
Both modules doesn't have templates so the html code is in the php files and they can't be displayed anymore with 2.0.10 beta.

No php debug to show.

Re: XOOPS 2.0.10 BETA Released

Mithrandir Published 03/27/2005 9:42 XOOPS is my life! Joined 06/21/2003 Comments 6320

Yep - that's what I found out when investigating the bug.

1) Blocks without templates don't show - bug located and will be fixed
2) Logout message
3) popup changes main window
4) Imagemanager not saving

Re: XOOPS 2.0.10 BETA Released

Gruby Published 03/27/2005 10:43 Just popping in Joined 11/06/2003 Comments 16

and the search runs by you all after updating?

Re: XOOPS 2.0.10 BETA Released

wanikoo Published 03/27/2005 11:06 Updated 03/27/2005 20:39 Not too shy to talk Joined 12/27/2003 Comments 129

Quote:

2) Logout message

/html/include/functions.php
function redirect_header($url, $time = 3, $message = '', $addredirect = true)
---
From:
$xoopsTpl->assign('message', htmlspecialchars($message));
To:
$xoopsTpl->assign('message', $message);

It will works well

Re: XOOPS 2.0.10 BETA Released

Mithrandir Published 03/27/2005 11:33 XOOPS is my life! Joined 06/21/2003 Comments 6320

OK:

1) Blocks without templates don't show - Bug located and fixed
2) Logout message - seems the htmlspecialchars() was misplaced. Removed. Thanks Wanikoo
3) popup changes main window - this one stomps me. I have no idea why it does that. It does not seem to have anything to do with the JS function since the image manager and MySQL debug window works fine
4) Imagemanager not saving - Bug located and fixed
5) Search not submitting correctly - Bug located and fixed

Re: XOOPS 2.0.10 BETA Released

Mithrandir Published 03/27/2005 11:41 XOOPS is my life! Joined 06/21/2003 Comments 6320

Narrowing down the popup problem, it seems to change the main window, when the popup is initiated by a link () and not when it is initiated by a form submission or a javascript onclick event.

Any help is appreciated

Re: XOOPS 2.0.10 BETA Released

Mithrandir Published 03/27/2005 12:47 XOOPS is my life! Joined 06/21/2003 Comments 6320

OK, think I found it:

http://jennifermadden.com/162/examples/window1.html

I don't know why this hasn't been a problem before, but when using a HREF tag and the javascript:openWithSelfMain() function, one should use javascript:void openWithSelfMain() ...

I'll change that for 2.0.10 beta2, but some modules may experience similar problems.

Re: XOOPS 2.0.10 BETA Released

Mithrandir Published 03/27/2005 13:09 XOOPS is my life! Joined 06/21/2003 Comments 6320

Yep, that does seem to do the trick. There were some changes in the openWithSelfMain() JS function from 2.0.9.x to 2.0.10 beta that weren't corrected throughout the system. Remind me to write a proper explanation for this for the final release as it may impact module code.

Any other bugs? Otherwise I will release 2.0.10 beta2 in a couple of hours.

Re: XOOPS 2.0.10 BETA Released

wanikoo Published 03/27/2005 13:33 Updated 03/27/2005 20:38 Not too shy to talk Joined 12/27/2003 Comments 129

Quote:

3) popup changes main window - this one stomps me. I have no idea why it does that. It does not seem to have anything to do with the JS function since the image manager and MySQL debug window works fine

/html/include/xoops.js

From:

 function openWithSelfMain(url,name,width,height) { 
    var options = "width=" + width + ",height=" + height + ",toolbar=no,location=no,directories=no,status=no,menubar=no,scrollbars=yes,resizable=yes,copyhistory=no"; 
 
    var new_window = window.open(url, name, options); 
    window.self.name = "main"; 
    new_window.focus(); 
    return new_window; 
}

To:

 function openWithSelfMain(url,name,width,height) { 
    var options = "width=" + width + ",height=" + height + ",toolbar=no,location=no,directories=no,status=no,menubar=no,scrollbars=yes,resizable=yes,copyhistory=no"; 
 
    new_window = window.open(url, name, options); 
    window.self.name = "main"; 
    new_window.focus(); 
}

I mean no "return new_window;"
It will work well

Re: XOOPS 2.0.10 BETA Released

Mithrandir Published 03/27/2005 13:41 XOOPS is my life! Joined 06/21/2003 Comments 6320

In this particular incident, yes, but I think it will cause problems elsewhere, when openwithselfmain is NOT called from a HREF

Re: XOOPS 2.0.10 BETA Released

wanikoo Published 03/27/2005 14:54 Updated 03/27/2005 20:37 Not too shy to talk Joined 12/27/2003 Comments 129

/html/class/xoopssecurity.php

 function checkSuperglobals() { 
        foreach (array('GLOBALS', '_SESSION', 'HTTP_SESSION_VARS', '_GET', 'HTTP_GET_VARS', '_POST', 'HTTP_POST_VARS', '_COOKIE', 'HTTP_COOKIE_VARS', '_REQUEST', '_SERVER', '_ENV', '_FILES', 'xoopsDB', 'xoopsUser', 'xoopsUserId', 'xoopsUserGroups', 'xoopsUserIsAdmin', 'xoopsConfig', 'xoopsOption', 'xoopsModule', 'xoopsModuleConfig') as $bad_global) { 
            if (isset($_REQUEST[$bad_global])) { 
                header('Location: '.XOOPS_URL.'/'); 
                exit(); 
            } 
        } 
    }

Umm....
How about adding HTTP_SERVER_VARS, HTTP_POST_FILES, HTTP_ENV_VARS to bad globals?

Re: XOOPS 2.0.10 BETA Released

Mithrandir Published 03/27/2005 14:59 XOOPS is my life! Joined 06/21/2003 Comments 6320

Good idea. Anything else missing?

Re: XOOPS 2.0.10 BETA Released

phppp Published 03/27/2005 15:56 XOOPS Contributor Joined 01/25/2004 Comments 2857

Is Beta 2 coming out soon?
There are some problems with module/block admin. Will see details after the bugs mentioned above are fixed.

minor one:
xoops/header.php line #188
if (!isset($show_lblock)) {
$xoopsTpl->assign('xoops_showlblock', 0);

Another: the comment system at xoops.org has page navigator, has it been available in the 2.010?
If so, plz add page to the block of "recent comment" -- at this moment at xoops.org, no matter which comment you click, you will be led to the first page of the comments.

Re: XOOPS 2.0.10 BETA Released

Mithrandir Published 03/27/2005 16:02 XOOPS is my life! Joined 06/21/2003 Comments 6320

Yes, I'm planning to release 2.0.10 beta2 tonight, unless more bugs surface. I would love to hear what "some problems with module/block admin" is. I don't want to have more betas than necessary, so could you elaborate on which problems?

Thanks for the header.php typo, I found that earlier on.

The comment system at xoops.org is a hack, that is very quick, very dirty and not at all finished. It only allows flat view of comments and as you have noticed, the page navigation works, but the comment locating code is not there, so it will always load first page.

Instead of reworking the comment system, I would rather work on a hook solution that would enable us to replace the comments with a newbb thread. However that is not a small task and should therefore be in XooSphere, I think, and not in the 2.0-based versions.

Re: XOOPS 2.0.10 BETA Released

phppp Published 03/27/2005 16:29 XOOPS Contributor Joined 01/25/2004 Comments 2857

class/xoopsblock.php
========================
function countSimilarBlocks($moduleId, $funcNum, $showFunc = null)
========================
Have not got time to understand the logic but it is not adequate to determine a block by using "showFunc".

module blocks:
Duplicated blocks do not disappear in 2.093. Since not see relevant changes, I guess (not sure, that why I said "will see beta 2...") the problem still there.

Another indirect problem (I guess the core team will focus on xoopSphere and it might not be a problem any more):
There should be some protection for the variables used by system/admin/modules.
For instance, I used a $GLOBAL["dirname"] variable in one of my new modules and it killed all my system. It took me one week time to find the cause (do not call me a fool).

Re: XOOPS 2.0.10 BETA Released

Mithrandir Published 03/27/2005 16:39 XOOPS is my life! Joined 06/21/2003 Comments 6320

countSimilarBlocks determines blocks by using module ID, funcNum (which is the index of the block in xoops_version.php IIRC) and showFunc if available. Together, these should identify a block - but I agree that the method is not optimal.

Where did you use that $GLOBAL["dirname"] so it caused problems?

Re: XOOPS 2.0.10 BETA Released

phppp Published 03/27/2005 16:54 Updated 03/27/2005 16:55 XOOPS Contributor Joined 01/25/2004 Comments 2857

If you put the $GLOBALS["dirname"] = "someSpecifiedDirname" (even just $dirname = ...) into xoops_version.php of a module, then the $dirname in system/admin/modules/main.php will be changed to "someSpecifiedDirname", which should be kept as "system" (not sure the specific value but it works in some way like this).

Re: XOOPS 2.0.10 BETA Released

Mithrandir Published 03/27/2005 17:01 XOOPS is my life! Joined 06/21/2003 Comments 6320

leads to the next question: Why do that?

And another: How should we be able to do this protection?

And a final: Do you know of more examples, so we can make a list of variables to protect/warn against using?

Re: XOOPS 2.0.10 BETA Released

Gambero[removed] Published 03/27/2005 17:09 Quite a regular Joined 01/13/2005 Comments 393

Wanikoo for XOOPS core developer!

Re: XOOPS 2.0.10 BETA Released

phppp Published 03/27/2005 17:10 XOOPS Contributor Joined 01/25/2004 Comments 2857

why: clone with no source code change is a feature of my new modules so the dirname should be assigned in a different way other than $modversion['dirname'] = "something"

How to protect: no good idea yet but perhaps give a prefix like system_ or xoops_ to the system variables or $xoopsVariables["dirname"] like the $xoopsOptions. It seems not worthy to do so much work for XOOPS 2.0x. Perhaps to list the reserved system variables in dev wiki?

Re: XOOPS 2.0.10 BETA Released

Mithrandir Published 03/27/2005 17:19 XOOPS is my life! Joined 06/21/2003 Comments 6320

Quote:

the dirname should be assigned in a different way other than $modversion['dirname'] = "something"

but is it better to assign it with $GLOBALS['dirname'] = "something" (or some code to detect the directory name)?

And mainly I'm wondering why you set a global variable in xoops_version.php. But you are right, it will not be for XOOPS 2.x

I'll see what I can do, but basically I don't see this as a core problem (sorry - and of course it would help to have a list of reserved variables, but xoops_version.php should really only declare local variables or $modversion[] indexes)

Re: XOOPS 2.0.10 BETA Released

phppp Published 03/27/2005 17:33 XOOPS Contributor Joined 01/25/2004 Comments 2857

Quote:

And mainly I'm wondering why you set a global variable in xoops_version.php.

right, it is not a core problem.
The lesson from the "story" is that module developers need be aware of such reserved variables.

Back to my specific topic, it is part of a complex solution that some variables in xoops_version.php need to be pre-specified. Of course, the problem could be easiy avoided.

Re: XOOPS 2.0.10 BETA Released

Yurdal Published 03/27/2005 20:05 Friend of XOOPS Joined 03/27/2005 Comments 386

After the upgrade the RSS Feed block (RSS) doesnt work anymore, also the headlines module doesnt work properly, you cant add a site anymore, i did a fresh installl of 2.0.10 because a update failed from 2.0.9.3, when will be the new patch availible ?
Thank

Re: XOOPS 2.0.10 BETA Released

wanikoo Published 03/27/2005 20:33 Updated 03/27/2005 20:36 Not too shy to talk Joined 12/27/2003 Comments 129

Quote:

Xoops 2.0.10 will be the last core release with modules included. Instead we will make module packages targeting specific areas.

Umm...
I see...
but...
before you exclude basic modules from core package,
could you change some codes of basic modules for PHP5 Compatibility?

-------------
For example: xoopsheadline

/modules/xoopsheadline/class/headline.php
From:

 if (get_class($headline) != 'xoopsheadlineheadline') { 
    return false; 
}

To:

 if (strtolower(get_class($headline)) != 'xoopsheadlineheadline') { 
    return false; 
}

/modules/xoopsheadline/index.php
/modules/xoopsheadline/admin/index.php

From:
$hlman =& xoops_getmodulehandler('headline');;
To:
$hlman =& xoops_getmodulehandler('headline');

/class/xml/saxparser.php

From:

 function free() 
    { 
        xml_parser_free($this->parser); 
 
        $is_php5 = strpos(phpversion(), "5"); 
        // If there is no 5 in the php version or it is not the first number 
        if ($is_php5 === false || $is_php5 > 0) { 
            unset($this); 
            $this = null; 
        } 
        else { 
           $this->__destruct(); 
        } 
    }

To:

 function free() 
    { 
        xml_parser_free($this->parser); 
 
        unset($this); 
        //$this = null; 
    }

Umm
The former seems to be logically correct....
but
PHP5 still gives us this error message if we don't remove $this=null;

Fatal error: Cannot re-assign $this in xxxxxxxx/saxparser.php on line 167
( tested with xoopsheadline on PHP5.0.3 )

PS:
Umm..
I forgot to say to this
Thanks to XOOPS Core Team for all the great work!!

Re: XOOPS 2.0.10 BETA Released

Mithrandir Published 03/27/2005 20:40 XOOPS is my life! Joined 06/21/2003 Comments 6320

All modules in those module packages will be looked through for PHP5-compatibility, but it is likely that we will remove the xoopsheadline module altogether and go for e.g. xhld instead.

Regarding the parse error in saxparser.php, I think I have found a solution in 2.0.10 beta 2

Re: XOOPS 2.0.10 BETA Released

hervet Published 03/28/2005 10:40 Friend of XOOPS Joined 11/04/2003 Comments 2267

If you apply some modifications to some modules, do it also for some other modules, for example the contact module, just have a look to the module's index page.

Re: XOOPS 2.0.10 BETA Released

Mithrandir Published 03/28/2005 11:14 XOOPS is my life! Joined 06/21/2003 Comments 6320

I would assume something like this:

Contact module -> Liaise
Newbb 1 -> Newbb 2
News 1.1 -> News 1.? (1.3 stable enough? Well, it should be by the time it's needed)
MyDownloads -> WF-Downloads (if scalability is improved over 2.05 - will have to investigate)
MyLinks -> Seems to be a myriad of link management modules popping up at the moment so should be easy to exchange
Sections -> WF-Sections and/or other section modules, depending on purpose of the package
XoopsFAQ -> SmartFAQ
XoopsHeadline -> xhld
XoopsMembers -> will investigate a replacement
XoopsPartners -> SmartPartner (?)
XoopsPoll -> hummm... still hoping for a further developed module cropping up from somewhere

So the current core modules are pretty much replaceable by newer and better supported modules and the need for me to add this to my workload is unnecessary, I feel.

Re: XOOPS 2.0.10 BETA Released

hervet Published 03/28/2005 18:39 Updated 03/28/2005 18:47 Friend of XOOPS Joined 11/04/2003 Comments 2267

I don't understand why some modifications are made to some modules wich are developped and maintained (newbb and news) while the other "standard" modules are not modified when they should be. I really don't understand.

PS : Yes News 1.3 is largely stable since a long time.

Re: XOOPS 2.0.10 BETA Released

Mithrandir Published 03/28/2005 18:50 XOOPS is my life! Joined 06/21/2003 Comments 6320

Now I get the point of your message, but I don't understand it? What is wrong with the contact module?

Re: XOOPS 2.0.10 BETA Released

hervet Published 03/28/2005 18:58 Friend of XOOPS Joined 11/04/2003 Comments 2267

News 1.3 is stable and secure (at least for me) so why do you spend and lost your time to modify the old version while, for example, the contact module is using this :
Quote:

extract($HTTP_POST_VARS);

Time should be spent where it's needed. It's not logic to modify the old ones while the others are not secure at all.

Just my opinion...

Re: XOOPS 2.0.10 BETA Released

Mithrandir Published 03/28/2005 19:14 XOOPS is my life! Joined 06/21/2003 Comments 6320

You are asking why the token system has been implemented in News 1.1 that is distributed with the core? Because it would be rather silly making a security feature and not use it in the modules distributed with the core.

Anticipating your question of why the News module in the core is not updated to 1.21 or 1.3, we have had that discussion before and we will solve that when we remove the modules from the core package and have the module packages instead - where News 1.3 will of course be used.

Regarding the extract() I don't really see much to be excited about as it is used in that particular page. It is true that extract(), foreach($_POST [..]) and register globals can be a security risk - if the programmer is not careful with how variables are used. This is not the case here. If the contact module's index.php is guilty of anything it is lacking variable sanitation before being used in an email message, but that's that.

We're getting sidetracked, though. If the 2.0.10 beta3 fixes the reported bugs (headlines module, popups, notifications, comments admin and a missing ) the 2.0.10 final version will be released and I will start working on 2.1.0 where no modules are included and News 1.3 & Newbb 2 will get the exposure and recognition they deserve.

Login

Username

Password

Remember me

Search

Advanced Search

Donat-O-Meter

Stats
Goal:	$100.00
Due Date:	Nov 30
Gross Amount:	$0.00
Net Balance:	$0.00
Left to go:	$100.00

Latest GitHub Commits

{{ record.sha.slice(0, 7) }} - {{ record.commit.message | truncate }}

{{ record.commit.author.name }} {{ record.commit.author.date | formatDate }}

XOOPS: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Re: XOOPS 2.0.10 BETA Released

Login

Search

Recent Comments

Re: New Admin Theme for XOOPS (Beta)

Sanford Pharmacy: Exceptional Pharmacy Services Tailored to You

Re: New Admin Theme for XOOPS (Beta)

Re: XOOPS 2.5.12 Beta-2 available for Testing

Re: XOOPS 2.5.12 Beta-2 available for Testing

Who's Online

Donat-O-Meter

Latest GitHub Commits

{{ record.sha.slice(0, 7) }} - {{ record.commit.message | truncate }}

Archives

News archives