XOOPS 2.2.3 Released - XOOPS - XOOPS News - XOOPS Web Application System

XOOPS

News

News World of XOOPS Developers Hacks Themes Archive Submit News

XOOPS: XOOPS 2.2.3 Released

Posted by: MithrandirOn 2005/8/26 10:48:55 44870 reads

============================
2005/08/26: Version 2.2.3
============================
- Fixed bug #1262813 - Add User, some fields are reset when error occur (Mithrandir/marook)
- Fixed bug #1262479 - email parsing in module.textsanitizer.php (Mithrandir)
- Fixed bug #1260694 - Mail User: X_UNAME is now Displayname, not Username (Mithrandir/marook)
- Fixed bug #1250347 - search in profiles doesnt work properly (Mithrandir/irmtfan)
- Fixed bug #1248077 - Activation link not fully operational. New constant XOOPS_ABS_URL added (Mithrandir)
- Fixed bug #1247398 - Error in modules/profile/search.php (Mithrandir/edomch)
- Fixed bug #1253289 - Can't make blocks invisible (Mithrandir/barrycooper)
- Fixed bug with XoopsFormSelectUser having a different signature from XOOPS 2.0.x (Mithrandir)
- Fixed bug in MySQLDatabase::quoteString() where empty values would not get enclosed in single quotes (Mithrandir)
- Fixed bug in system/admin/banners/main.php where it was impossible to edit banner clients (Mithrandir/Peekay)
- Fixed bug in system/admin/modulesadmin/modulesadmin.php where configuration categories were not removed on module uninstallation (Mithrandir)
- Fixed bug in system/admin/modulesadmin/modulesadmin.php where block templates could remain in the database after module uninstall (Mithrandir)
- Fixed bug in kernel/module.php where config unused options would not be removed if a config has no options any more (phppp)
- Fixed bug in kernel/object.php where whereclause is wrongly generated for multiple keyname (phppp)
- Fixed bug/typo in include/functions.php function xoops_array_diff_assoc() (phppp)

- Added update procedure to System module update, where blocks and templates without corresponding modules will be removed (Mithrandir)
- Modified kernel/module.php regexp for page detection in getCurrentPage() (phppp)
- Added password length check in modules/profile/register.php (phppp/Aries)

- Added patch #1245922 - Little bug in banner manager (Mithrandir/zoullou)
- Added patch #1249427 - userinfo.php template improvement (Mithrandir/zoullou)
- Modified error message rendering in modules/profile/register.php (phppp)

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

Re: XOOPS 2.2.3 Released

McDonald Published 08/26/2005 11:19 Home away from home Joined 08/15/2005 Comments 1072

Thanks a lot!!!

Another job well done by team of professionals!

Official Module Package links are broken

jondixon Published 08/26/2005 11:25 Not too shy to talk Joined 05/12/2004 Comments 107

Broken links to the packages. Great idea though! One other question: will the modules that have been 'slightly modified' be easy to update from when those module developers make a new version?

Re: XOOPS 2.2.3 Released

basby Published 08/26/2005 11:31 Not too shy to talk Joined 01/28/2003 Comments 109

Thanks for the update!

I have problems with the upgradefrom 2.2.2 to 2.2.3. I have uploaded all files (from the XOOPS 2.2.2 to 2.2.3 Patch) to the server and then tried to log in into the website. I got the following error:

Fatal error: getauthconnection(): Failed opening required '/home-root/class/auth/auth_nl2br.php' (include_path='.:/usr/share/pear:/home/ma010ged/www/include:/usr/share/php:/usr/local/lib/php/') in /home-root/class/auth/authfactory.php on line 33
Warning [PHP]: getauthconnection(/home-root/class/auth/auth_nl2br.php): failed to open stream: No such file or directory in file class/auth/authfactory.php line 33

Note that I changed the real HTML-root to "home-root" in the above. as well as the include_path.

Any idea what this can be?

Re: Official Module Package links are broken

smdcom Published 08/26/2005 11:31 Joined 04/27/2004 Comments 901

thanks for the release... great job!

Re: Official Module Package links are broken

JMorris Published 08/26/2005 11:57 XOOPS is my life! Joined 04/11/2004 Comments 2722

Great News!

I'll be upgrading this evening!

Keep up the GREAT work!

Best Regards,

James

Re: Official Module Package links are broken

Mithrandir Published 08/26/2005 12:13 XOOPS is my life! Joined 06/21/2003 Comments 6320

Quote:

Broken links to the packages. Great idea though! One other question: will the modules that have been 'slightly modified' be easy to update from when those module developers make a new version?

What packages are broken?? They are hosted on sf.net and may not be fully uploaded everywhere - but just try another mirror.

Re: XOOPS 2.2.3 Released HELP!!!!!

herver Published 08/26/2005 12:29 Just popping in Joined 11/30/2004 Comments 2

After I've installed XOOPS 2.2.2 to 2.2.3 Patch, when I try to log in, I'm taken to a blank page
(http://mysite/users/user.php) from where I can do nothing

Re: Official Module Package links are broken

bluenova Published 08/26/2005 12:33 Updated 08/26/2005 12:36 Joined 04/10/2004 Comments 1022

Quote:

Quote:
Quote:
Broken links to the packages. Great idea though! One other question: will the modules that have been 'slightly modified' be easy to update from when those module developers make a new version?

What packages are broken?? They are hosted on sf.net and may not be fully uploaded everywhere - but just try another mirror.

I also got a 'please report broken file' message when clicking one of the module packagesfor the first time, but trying it a 2nd time it worked fine.

Re: XOOPS 2.2.3 Released

tedcalan Published 08/26/2005 12:51 Just popping in Joined 06/23/2005 Comments 3

All the hard work is greatly appreciated. Would the SmartModules be considered stable with this update? I know Marcan has developmental modules available at SmartFactory, but I'd like to upgrade to 2.2 ASAP on my production site.

Re: XOOPS 2.2.3 Released HELP!!!!!

kapeman Published 08/26/2005 13:02 Updated 08/26/2005 13:21 Just popping in Joined 05/03/2005 Comments 87

I have the same issue.

Please help!!!

Quote from herver's post above:

After I've installed XOOPS 2.2.2 to 2.2.3 Patch, when I try to log in, I'm taken to a blank page
(http://mysite/users/user.php) from where I can do nothing

BTW: how do you quote text? I can't find the option.

Re: XOOPS 2.2.3 Released

WarDick Published 08/26/2005 13:04 Just can't stay away Joined 09/13/2003 Comments 890

Do Not Upgrade

1. Can Not Log In. Get login screen and then a blank page.

2. Prior to upgrade xoopsgallery would work. Now it does not. Now where the album name was I get nl2br instead. See post above it also has nl2br referenced in it.

Quote:

Fixed bug in system/admin/modulesadmin/modulesadmin.php where block templates could remain in the database after module uninstall (Mithrandir

3. Now the template page is not broken but the problem still exists. It is just covered up!

Re: XOOPS 2.2.3 Released

DCrussader Published 08/26/2005 13:18 Friend of XOOPS Joined 07/04/2005 Comments 573

Do not upgrade is a exatcly what I wanna say:

What the hell fixes this release ?

Here how looks my topics in News 1.4 after upgrading
28 nl2 No Edit - Delete
6 nl2br No Edit - Delete
29 nl2 No Edit - Delete
12 nl2b No Edit - Delete

And maybe a lot of other sux are done to this release, gzip compression again is a problem, yeah ?

Now can u provide downgrader to 2.2.2 please ?

Re: XOOPS 2.2.3 Released

ralf57 Published 08/26/2005 13:19 Quite a regular Joined 02/03/2003 Comments 231

The XOOPS Official Module Packages is a great idea.
It not only gives certain modules the "Official approval" but also makes order in the vastity of available modules by grouping them and covering all the specific purposes.

Re: XOOPS 2.2.3 Released HELP!!!!!

wildo Published 08/26/2005 13:21 Just popping in Joined 03/01/2004 Comments 33

Quote:

After I've installed XOOPS 2.2.2 to 2.2.3 Patch, when I try to log in, I'm taken to a blank page
(http://mysite/users/user.php) from where I can do nothing

Same here!!! ;-(

Re: Official Module Package links are broken

CeBepuH Published 08/26/2005 13:29 Not too shy to talk Joined 06/10/2002 Comments 128

There really is a problem with the links in the XOOPS 2.2 Module Packages on this site.

If you click on the link next to this icon

the link is broken.

But if you click on this icon
Resized Image
everything is fine.

Re: XOOPS 2.2.3 Released

basby Published 08/26/2005 13:31 Not too shy to talk Joined 01/28/2003 Comments 109

Quote:

Poster: DCrussader Posted: 2005/8/26 14:18:39

Do not upgrade is a exatcly what I wanna say:

What the hell fixes this release ?

...

And maybe a lot of other sux are done to this release, gzip compression again is a problem, yeah ?

Now can u provide downgrader to 2.2.2 please ?

People are working for FREE, you are using there stuff for FREE. This is not the way to communicate to the XOOPS development people.
Remember YOU are responsible for your site. Make a backup next time before you upgrade.

Shame on you DCrussader!

Re: XOOPS 2.2.3 Released

DCrussader Published 08/26/2005 13:32 Friend of XOOPS Joined 07/04/2005 Comments 573

Quote:

Hard working people who get no appreciation from certain people!

If theres an problem, report it and let it get dealt with!

I will remeber this, instead publishing incompatible pathes better try it before that.

Re: XOOPS 2.2.3 Released

DCrussader Published 08/26/2005 13:39 Friend of XOOPS Joined 07/04/2005 Comments 573

Quote:

People are working for FREE, you are using there stuff for FREE. This is not the way to communicate to the XOOPS development people.

Or use Kazumi Ono XOOPS 2.0.11.1JP

Shame ?
Who have to be shamed ?

This can not be happend with all releases up to 2.0.7.3

Re: XOOPS 2.2.3 Released

phppp Published 08/26/2005 13:48 XOOPS Contributor Joined 01/25/2004 Comments 2857

Before official fix, a quick patch for the error "Fatal error: getauthconnection() ... ":
XOOPS_ROOT_PATH/class/auth/authfactory.php, around line #25

 require_once XOOPS_ROOT_PATH.'/class/auth/auth.php'; 
            if (!$config) { // If there is a config error, we use xoops 
                $xoops_auth_method = 'xoops'; 
            } else { 
                $xoops_auth_method = $config[0]->getVar('conf_value'); 
[b]                if(!is_readable(XOOPS_ROOT_PATH.'/class/auth/auth_' . $xoops_auth_method . '.php')){ 
                    $xoops_auth_method = 'xoops'; 
                } 
[/b] 
            }

As for the blank page on user.php, it ever happened to me but could not reproduce it so I thought it was caused by my misoperation.
For anyone who has the problem, could you plz provide some info so that developers could fix as early as possible? info about: PHP version, Apache or IIS

Re: XOOPS 2.2.3 Released

DCrussader Published 08/26/2005 13:54 Friend of XOOPS Joined 07/04/2005 Comments 573

Thanks phppp for the fast fix, anyway here is the link to 2.2.3 to 2.2.2 downgrader.

http://x22.pzcci.org/files/x223-222-downgrade.tar.gz

Re: XOOPS 2.2.3 Released

basby Published 08/26/2005 13:56 Not too shy to talk Joined 01/28/2003 Comments 109

Thanks phppp for this usefull contribution. My problem is resolved by your solution.

Re: XOOPS 2.2.3 Released

jdseymour Published 08/26/2005 13:57 Updated 08/26/2005 13:58 Friend of XOOPS Joined 11/11/2004 Comments 3782

Although, for those having problems, I am not on my test site. Gambero assembled the changed files for downgrade to 2.2.2. You can find it http://www.savefile.com/files/3894655

2.2.3 is however working flawlessly on my test site.

Re: XOOPS 2.2.3 Released

basby Published 08/26/2005 13:58 Not too shy to talk Joined 01/28/2003 Comments 109

DCrussader thanks for this usefull contribution.

Re: XOOPS 2.2.3 Released

Chado Published 08/26/2005 14:07 Updated 08/26/2005 14:13 Not too shy to talk Joined 06/06/2003 Comments 113

phppp: Thanks!! That did the trick!!!

DCrussader: Some of the same people you just blasted are the ones who helped fix it. Can you cut out the rude reactionary comments!!

As for the user.php problem. You can get around it by going to yoursite/recovery.php and logging in.

*edit
For some reason, on a new install, the main menu and login box are not automatically showing. So, I had to login from recovery.php and activate them.

Re: XOOPS 2.2.3 Released

mrmacadamia Published 08/26/2005 14:18 Just popping in Joined 12/07/2004 Comments 37

phew...thanks phppp!!

Re: XOOPS 2.2.3 Released

loukaum Published 08/26/2005 14:33 Just popping in Joined 11/02/2003 Comments 93

Thanks for the work guys!

After upgrade my website and apply the fix from Phppp got the error:

 Fatal error: [] operator not supported for strings in /MY_WWW_DIR/class/module.textsanitizer.php on line 168

Anyone can give me a clue?

P.S. If I just back my old "module.textsanitizer.php" averthing works fine...

Re: XOOPS 2.2.3 Released

therock Published 08/26/2005 14:33 Just popping in Joined 02/02/2005 Comments 38

Can I upgrade from 2.0.13.1 to this release? And how do I do it?

Re: XOOPS 2.2.3 Released

fredski Published 08/26/2005 14:36 Updated 08/26/2005 14:47 Quite a regular Joined 01/26/2004 Comments 265

Yeah you can log in using that, and get the recovery page, but the admin.php is just as blank as the user page :(

ANd now the front end of my site can't be accessed at all, now that I've logged in with recovery :( bad , very bad

Tried the downgrade but still my site is broken. Just get the white page of death.

Do not use the recovery.php method, at leastthe front end was working before that

Re: XOOPS 2.2.3 Released

kapeman Published 08/26/2005 14:47 Updated 08/26/2005 14:54 Just popping in Joined 05/03/2005 Comments 87

quoted from phppp:

As for the blank page on user.php, it ever happened to me but could not reproduce it so I thought it was caused by my misoperation.
For anyone who has the problem, could you plz provide some info so that developers could fix as early as possible? info about : PHP version, Apache or IIS
end quote:

I am running XOOPS on PHP version 4.3.10
Apache/1.3.33 (Unix)

Also what do I need to do once I use the recovery.php option?

Thanks!

Re: XOOPS 2.2.3 Released

fredski Published 08/26/2005 14:56 Updated 08/26/2005 15:04 Quite a regular Joined 01/26/2004 Comments 265

Well for my site where I was logged in to begin with, updated to 2.2.3 no problem, except with the login error, but that was fixed with the code:

In XOOPS_ROOT_PATH/class/auth/authfactory.php

Replace

 require_once XOOPS_ROOT_PATH.'/class/auth/auth.php'; 
            if (!$config) { // If there is a config error, we use xoops 
                $xoops_auth_method = 'xoops'; 
            } else { 
                $xoops_auth_method = $config[0]->getVar('conf_value'); 
            }

With

 require_once XOOPS_ROOT_PATH.'/class/auth/auth.php'; 
            if (!$config) { // If there is a config error, we use xoops 
                $xoops_auth_method = 'xoops'; 
            } else { 
                $xoops_auth_method = $config[0]->getVar('conf_value'); 
                if(!is_readable(XOOPS_ROOT_PATH.'/class/auth/auth_' . $xoops_auth_method . '.php')){ 
                    $xoops_auth_method = 'xoops'; 
                } 
 
            }

The blank page site I have was due to me not being logged in before I moved the update files over. Therefore I could not update the system module. If the update came with an system update file, I'm sure that would fix the problem.

Server OS: Database: MySQL 4.0.24
Server Date: 08/26/2005 15:56:10 Datebase Date: 08/26/2005 15:56:10
Server Up Time:
HTTP Server: Apache/2.0.46 (CentOS)
PHP Version: 4.3.11 (Zend: 1.3.0)
Server API Apache 2.0 Handler
Apache Version Apache/2.0.46 (CentOS)

My two sites have exactly the same files, the only difference between the updates was that i was logged in on one before the file transfare and I could run the system update, and on the broken one I wasn't logged in and couldn't get to login to run the system update.

Re: XOOPS 2.2.3 Released

frankblack Published 08/26/2005 15:06 Updated 08/26/2005 15:56 Just can't stay away Joined 06/13/2005 Comments 830

As head of the German Official Support Site I am not willing to offer support for XOOPS 2.2 or offer downloads for 2.2.x.x.x.x anymore.

I think this will be the appropriate step until a stable 2.2.x-Version will be released.

I DO understand that there will be problems when a huge step is made from the 2.0.x-versions to the 2.2x-versions.

But with this version-marathon (speaking for Germany only) XOOPS is losing more and more users.

My step means no disrespect for the hard work of the Core Developers!

So now go ahead and beat me up!

Re: XOOPS 2.2.3 Released

herver Published 08/26/2005 15:08 Just popping in Joined 11/30/2004 Comments 2

Thanks DCrussader!!!! :)

Re: XOOPS 2.2.3 Released

vagelis Published 08/26/2005 15:11 Just popping in Joined 09/05/2004 Comments 79

Congratulations. You are the perfect team.

Thanks

Temp 2.2.3 Patch Fix

fredski Published 08/26/2005 15:12 Updated 08/26/2005 15:56 Quite a regular Joined 01/26/2004 Comments 265

OK I have a fix for the ones who can't log in / blank page.

Get the xoopsupdate file from the 2.13 to 2.2 patch copy it to your root and run it in your browser.
then use the auth fix code.

You should now be able to view and login as normal

:)

Although the site that I used recovery.php on is still broke :( I can't get to view the front end or run xoopsupdate.php, I just get a white page when running the update. The only thing I can view is the recovery page :( If I try and view the front page it just tells me that this page can not be displayed, the page you are looking for might have been removed or had its name changed.
But looking in my ftp, I can see theres an index.php file there etc

Anyone help me with this one?

Re: XOOPS 2.2.3 Released

WarDick Published 08/26/2005 15:33 Just can't stay away Joined 09/13/2003 Comments 890

Quote:

2.2.3 is however working flawlessly on my test site.

Can anyone else confirm this?

Was it an upgrade form 2.2.2 or a fresh install?

Re: Temp Fix

Jharis Published 08/26/2005 15:43 Just can't stay away Joined 02/13/2005 Comments 488

Thank You guys for the the FREE work you do for this community. We appreciate you efforts. Please don't let the some peoples negative banter get to you.

Guys remember:
1. All devs strive to release a good solid product thats works across many environments.
2. Do your best to be part of the solution, and be constructive.
3. Post as much detail as possible when you have a problem.
4. Be willing to do your hoome work when you do encounter a problem.
5. Go back over the read me files, check the boards for info, get your facts strait before you post.
5. Consider holding off on upgrading for a couple of weeks and read problems others might be having.
6. Watch how you speak to others on this board. Ask yourself if he were in front of me would I say it the same way? Being nice goes a long way!
7. Be nice! Everyone here works for XOOPS because they love something about it.
8. Remember XOOPS is a free product supported by users working for free.

don (el paso)

Re: XOOPS 2.2.3 Released

cerbero Published 08/26/2005 16:01 Not too shy to talk Joined 09/11/2003 Comments 191

Thanks a lot for your efforts.

It would be very interesting a litle description on every module's package with each contents.

Version Numbers and Patches

monique Published 08/26/2005 16:10 Updated 08/26/2005 16:17 Just popping in Joined 05/23/2005 Comments 62

Hi -- I have version 2.2.1. Can you tell me which patch to use? Thank you, thank you!!

Monique.

Why upgraded so fast?

qingting Published 08/26/2005 16:11 Just popping in Joined 09/05/2003 Comments 11

I found that the Team released 2 xooops in a month or less than a month. Why can you all let more people test the new XOOPS before releasing it with a lot of bugs?
Do you know that each time there is a new release of XOOPS for webistes use other languages such as Chinese like mine, we hav to wait and CAN NOT just simply install the patch files?
This is not a good way to develop a good open source applications.
I strongly ask the Core team to re consider the time of release for each new Xoops!!!

Re: XOOPS 2.2.3 Released

cerbero Published 08/26/2005 16:12 Not too shy to talk Joined 09/11/2003 Comments 191

sorry, i thougt...

Page Navigation fixes for WF-Links 1.03

McDonald Published 08/26/2005 16:12 Home away from home Joined 08/15/2005 Comments 1072

The module WF-Links 1.03 that is included in the PersonalPack and CommunityPack still has the page navigation bug (Page 1,2,3 doesn't work). In a category you can't browse through the pages with links.
To fix this you have to do as follows:

1. Open viewcat.php

2. Go to line 206: $list_by = "'cid=' . $cid";

3. Change this in: $list_by = "cid=$cid";

4. Save and upload viewcat.php

Also the bug with the page navigation in the Admin Main page still fails. For this see the following thread:

http://www.wf-projects.com/modules/newbb/viewtopic.php?topic_id=59&forum=7

Re: Why upgraded so fast?

monique Published 08/26/2005 16:16 Just popping in Joined 05/23/2005 Comments 62

Maybe you should take it upon yourself to let the rest of the world test the new version before you upgrade?

Re: XOOPS 2.2.3 Released

hervet Published 08/26/2005 16:49 Friend of XOOPS Joined 11/04/2003 Comments 2267

In the changelog you have forgoted the correction I have made to the notification's class.

Re: XOOPS 2.2.3 Released

Marco Published 08/26/2005 17:44 Updated 08/26/2005 17:52 Home away from home Joined 03/15/2004 Comments 1256

Quote:

WF-Downloads 2.05a (Slightly modified for XOOPS 2.2)
WF-Links 1.03 (Slightly modified for XOOPS 2.2)
XF-Guestbook 2.22 (Slightly modified for XOOPS 2.2)
SmartFAQ 1.04 (Slightly modified for XOOPS 2.2)
SmartSection 1.0 (Slightly modified for XOOPS 2.2)
SmartClient 1.02 (Slightly modified for XOOPS 2.2)
SmartPartner 1.02 (Slightly modified for XOOPS 2.2)

As local support member, it will be extremly difficult to help end users."where did you get your module ? mith's version ? original one? 2.2 one? 2.0.x one ?
please remove all those files.
I personaly recommend not to upgrade, stay in 2.0.13.1 and wait for a stable and tested version. Mith has worked hard, but his efforts are deserved with this too quick news.
Mith, why not having called for help in debugging process ? Don't forget support community.

I would like to see some RC before final one, especially now. It's not time to waste our time...
I can remember some days where we some critized ono's attitude, about releasing
it's time for XOOPS to become a mature project : to work as a team and to use a due professionnal release process.

Let's change this news and call it "2.2.3 RC1 is released", please.

marco
QA Team

Re: XOOPS 2.2.3 Released

zoullou Published 08/26/2005 17:53 Quite a regular Joined 03/02/2004 Comments 250

I'm agree with Marco.
Mithy, you make a good work but you aren't alone. Submit your new version to a test community before submit release to public

Cheers

Re: XOOPS 2.2.3 Released

Shine Published 08/26/2005 17:57 Updated 08/26/2005 18:00 Just can't stay away Joined 07/22/2002 Comments 822

As moderator of the Dutch XOOPS community supportsite I totally agree with Marco and Frankblanc.

It is undoable to give proper support at this stage. There are to many problems with the 2.2.x version release(s) themselves and next the modules compatibilitie(s).
Please turn the clock back and give it RC release.
If people ask (and they do) I recommend them to stay at 2.0.13.x. at this moment.

Sorry tot say and by all means no offence to the hard work of devs.

Grtz., Shine

Re: XOOPS 2.2.3 Released

LazyBadger Published 08/26/2005 18:17 Home away from home Joined 06/07/2004 Comments 1187

Quote:

here is the link to 2.2.3 to 2.2.2 downgrader

Please, allow users download it for rollback onto 2.2.2, I got only

You don't have permission to access /files/x223-222-downgrade.tar.gz on this server.

and my Frontier now is blank page...
Thank Core Team and personally Mithrandir for this update...
Lamers must die!!!

Re: XOOPS 2.2.3 Released

DCrussader Published 08/26/2005 18:17 Updated 08/26/2005 18:20 Friend of XOOPS Joined 07/04/2005 Comments 573

Yeah, 2.0.13.1/2 is much more stable I recommend it to the Bulgarian users too, after today action with this nullified patch.

Downgraded is re-uploaded (sorry I was so fast during the remove of the whole site).

Reuploaded link - http://x22.pzcci.org/files/x223-222-downgrade.tar.gz
Fixed permissions, again sorry (this was a Mith task, not mine)

Mith, another problem was catched with the stable 2.2.2, RM+Soft Downloads 1.2 Plus, doesnt show the languge files in the administration part, in 2.0.13.1 this problem doesnt exist.

Again with the same module, in 2.2.2 in user interface I've got on every sub-directory ? , eg. Modules ? Themes ?, this trouble not exist in 2.0.

Messing xoops_root/language/english (specialy for publishing news) with third pary modules, such as Herve's News 1.4, makes translation unavailable.

XOOPS 2.2.2 present again the same troubles in xoopsmailer local, such the old time (2.0.9.x) ISO8859-1 hard linked. Japanese cant use it, xoopsmailerlocal.php doesnt work with 2.2.2 anymore.

This calendar ? - wth are the language files, due the total conversion of XOOPS, Date in the left upper corner remains in English.

PDF Class is strongle linked to ISO8855-1, so when the user trys to export News or CBB Forum Post to PDF from Unicode, it get's empy page or strange symbols. (partialy solved).

Later will be added more reports, damn I'm tired of this deleting/uploading, please do not release in feature Alpha versions as stable.

Re: XOOPS 2.2.3 Released

kapeman Published 08/26/2005 18:45 Just popping in Joined 05/03/2005 Comments 87

Thanks fredski!!!

Your changes to the authfactory.php file were all it took to fix my blank user page problem.

I did not have to install any old files.

Thanks!!!

P.S. Prior to using fredski's fix, I was able to get into my site via recovery and update the system module and it did not fix the problem.

XOOPS 2.2.3 is shame

LazyBadger Published 08/26/2005 19:02 Home away from home Joined 06/07/2004 Comments 1187

Link to 2.2.2 in "Latest Releases" will not be replaced to 2.2.3 link on XOOPS2.RU.
I can't say for the whole team, but we'll discuss situation and most probably will join to German and Dutch friends in strike

Re: XOOPS 2.2.3 Released

jdseymour Published 08/26/2005 19:22 Friend of XOOPS Joined 11/11/2004 Comments 3782

Quote:

Was it an upgrade form 2.2.2 or a fresh install?

Upgrade from 2.2.2

Re: XOOPS 2.2.3 Released

dap997 Published 08/26/2005 19:23 Updated 08/26/2005 19:24 Friend of XOOPS Joined 02/20/2005 Comments 37

THANKS !!!
Great Job with Packages.

[size=x-large]
If you need more betatesters simply ask...
You are not alone.
[/size]

We do some support for polish version 2.2.x but only geeks use it now .

dap997

PS Hack from phppp do not solve my iusse with blank screen.
When I use polish language, and xmt skins I got it every time.

[root@localhost ~]# uname -a
Linux localhost.localdomain 2.6.12-1.1398_FC4 #1 Fri Jul 15 00:52:32 EDT 2005 i686 i686 i386 GNU/Linux
[root@localhost ~]# apachectl -ver
Server version: Apache/2.0.54
Server built: Jul 26 2005 06:11:51
[root@localhost ~]# mysql --version
mysql Ver 14.7 Distrib 4.1.12, for redhat-linux-gnu (i386) using readline 4.3
[root@localhost ~]# php -version
PHP 5.0.4 (cli) (built: Aug 17 2005 09:53:54)
Copyright (c) 1997-2004 The PHP Group
Zend Engine v2.0.4-dev, Copyright (c) 1998-2004 Zend Technologies

dap997 (polish support)

How To: No Blank page in 2.2.3

marook Published 08/26/2005 19:34 Updated 08/26/2005 19:47 Friend of XOOPS Joined 09/09/2002 Comments 89

Hi All,

I just updated from 2.2.2 -> 2.2.3 and got a blank page after upgrade.
Here's what to do:
1: Add 'auth' patch mentioned above.
2: Use 'class/module.textsanitizer.php' from 2.2.2 (2.2.3 fails in line 168 acording to PHP Debug mode!)
EDIT: The file is part of 2.2.1 !

Now everything works..

I did have some template issues with a few modified blocks, but I just re-updated those from files, and all work now!

Ohh, and to all of you who simply bash with 'dont run 2.2.x - its not stable...' please turn on some debugging and see what's going on! And then Report Core Bug for crying out loud!

Best,

Re: XOOPS 2.2.3 Released

WarDick Published 08/26/2005 19:35 Just can't stay away Joined 09/13/2003 Comments 890

why is yours the only one working. What magical insight do you have? Anxious to solve the problems.

Re: XOOPS 2.2.3 Released

m0nty Published 08/26/2005 19:36 XOOPS is my life! Joined 10/24/2003 Comments 3337

You know what gets me?

xoops 2.2 was the most open development of XOOPS ever.

it was always AVAILABLE for people to download and test!!

but instead the developers never got the required feedback about bugs, neither were they discovered or reported either. some were, some weren't.

instead what happened more was people downloaded it, tested it and well the devs spent more time answering questions about where this is in admin, how do i enable blocks, how do i change fields, how do i edit templates, how how how.. instead of people actually going thru each option and seeing what it does for themselves.. if people would actually try to figure things out for themselves and let the developers do their jobs, maybe more of these bugs would have been discovered a lot earlier.

i would actually recommend to the core development team to NOT do this open development procedure during future versions (even tho many requested the open ness, it has inevitably caused way more hassle and problems than expected) instead ask for BETA testers to actually test them, and beta testers should *know* how to test and report bugs etc..

beta testers should not be people that have never used XOOPS b4 and don't know how to use it properly.

so all the people who are knowledgable on xoops, and i don't mean programming necessarily, i mean in just knowing how XOOPS works and where everything is etc.. maybe you should get this version on CVS and give it a good testing yourselves, and then lets get this version back on track as it should be instead of wasting all the time on complaining and saying this should be done and that's not working.

Re: XOOPS 2.2.3 Released

snow77 Published 08/26/2005 19:37 Just can't stay away Joined 07/23/2003 Comments 864

I want to thank all the developers and the helpfull people that make part of xoops. I think everyone has done excellent work and truly believe that XOOPS is in one of it's best moments. It´s just a matter of patience to solve issues with recent XOOPS versions.

Xoops gets better every day and I am proud of all the people who have participated in it's evolution.

Re: XOOPS 2.2.3 Released

WarDick Published 08/26/2005 19:40 Just can't stay away Joined 09/13/2003 Comments 890

Quote:

maybe you should get this version on CVS and give it a good testing yourselves, and then lets get this version back on track as it should be instead of wasting all the time on complaining and saying this should be done and that's not working.

Who can download CVS?

Re: XOOPS 2.2.3 Released

Methis Published 08/26/2005 19:44 Just popping in Joined 06/25/2005 Comments 52

Quote:

As moderator of the Dutch XOOPS community supportsite I totally agree with Marco and Frankblanc.
It is undoable to give proper support at this stage. There are to many problems with the 2.2.x version release(s) themselves and next the modules compatibilitie(s).
Please turn the clock back and give it RC release.
If people ask (and they do) I recommend them to stay at 2.0.13.x. at this moment.

Sorry tot say and by all means no offence to the hard work of devs.

Grtz., Shine

Also in the Italian XOOPS community this is the line of action.
This is not an officiali line and I'm not a moderator on that site but if someone asks for notice about an upgrade to 2.2 ours advice (not only mine but also moderator and administrator's ones) is to to keep 2.0.13 version.

Moreover in the Italian official site there are lots of users that think that a Release Candidate period should last also 3-4 mounths if necessary and that's better 4-5 version a year than this "version-marathon" (to use a frankblack's expression that we Italian perfectly understand).

However I've to say that XOOPS Official Module Packages were a very good idea...for example in this period I read some newbie that did answer like that: "Apart sending private massage what's possible to do with Xoops?"

Re: XOOPS 2.2.3 Released

m0nty Published 08/26/2005 19:53 XOOPS is my life! Joined 10/24/2003 Comments 3337

Quote:

Who can download CVS?

anybody can download the CVS via sourceforge site.

you will need a program called tortoiseCVS or winCVS. it gives you the info on sourceforge when you click the browseCVS link..

Re: XOOPS 2.2.3 Released

davidl2 Published 08/26/2005 19:53 XOOPS is my life! Joined 05/26/2003 Comments 4843

The module packs are an excellent idea indeed....

The grumble about the changes made earlier... well I can understand that - perhaps a text file with changes made should have been included with them?

If one is included... i stand corrected

Re: XOOPS 2.2.3 Released

jdseymour Published 08/26/2005 20:02 Friend of XOOPS Joined 11/11/2004 Comments 3782

Quote:

why is yours the only one working. What magical insight do you have? Anxious to solve the problems.

Possibly, because I use a custom loggin built into my theme, not the login block? Anyway I have logged in and out most all day, no blank pages, no errors, only one admin page for a module giving me formatting problems, but still works.

Re: XOOPS 2.2.3 Released

WarDick Published 08/26/2005 21:03 Updated 08/26/2005 21:04 Just can't stay away Joined 09/13/2003 Comments 890

There are a few things you need to get started

* A SourceForge account
* An account here, in the XOOPS development site
* Authorization to use CVS
* A CVS client

Re: XOOPS 2.2.3 Released

WarDick Published 08/26/2005 21:05 Just can't stay away Joined 09/13/2003 Comments 890

Quote:

Possibly, because I use a custom loggin built into my theme, not the login block? Anyway I have logged in and out most all day, no blank pages, no errors, only one admin page for a module giving me formatting problems, but still works.

Any chance you could share this magic theme or just the magic part!

Re: XOOPS 2.2.3 Released

m0nty Published 08/26/2005 21:08 XOOPS is my life! Joined 10/24/2003 Comments 3337

Quote:

There are a few things you need to get started

* A SourceForge account
* An account here, in the XOOPS development site
* Authorization to use CVS
* A CVS client

that's if you're a developer. and need to submit changes etc..

to just simply download the CVS, u only need the CVS client (tortoiseCVS). you don't need to have an account or anything to download the CVS..

but either way, just simply download the zip and take it from there.. the CVS version isn't all needed..

Re: XOOPS 2.2.3 Released

DCrussader Published 08/26/2005 21:19 Friend of XOOPS Joined 07/04/2005 Comments 573

@Monty: Quote:

but instead the developers never got the required feedback about bugs, neither were they discovered or reported either. some were, some weren't.

Do u remeber PD-Downloads 1.2 dissusion, why to submit bug reports when no one take it seriously ?

Re: XOOPS 2.2.3 Released

Duke_Henry Published 08/26/2005 21:25 Just popping in Joined 07/30/2004 Comments 37

Great job! Upgrade went flawlessly, everything is still happy!

I, as well as many others appreciate the hard work put into this software.

Thanks again!

Re: XOOPS 2.2.3 Released

WarDick Published 08/26/2005 21:40 Just can't stay away Joined 09/13/2003 Comments 890

A zip file is not CVS.

So is there CVS access or not?

Re: XOOPS 2.2.3 Released

m0nty Published 08/26/2005 21:41 XOOPS is my life! Joined 10/24/2003 Comments 3337

Quote:

Do u remeber PD-Downloads 1.2 dissusion, why to submit bug reports when no one take it seriously ?

i'm not gonna get into a nitpicking argument on this from a totally irrelevant question.

but my reply to that question is pretty simple >

if you don't submit those bug reports then don't complain to the devs when a final version is released and those bugs are still present!!!

this isn't pd-downloads.. this is the XOOPS core! and bugs reports do get attention paid to once they are discovered and reported..

Re: XOOPS 2.2.3 Released

m0nty Published 08/26/2005 21:45 XOOPS is my life! Joined 10/24/2003 Comments 3337

Quote:

A zip file is not CVS.

So is there CVS access or not?

again.. YES cvs access for downloading is always available.. using tortoiseCVS.. you don't need an account or anything other than the client to download it.

i'm not saying that the CVS is different to the zip contents, but it contains the latest changes made. all i'm trying to say here is that people who know XOOPS and how to use it and who CAN bug test properly need to be doing it. it's irrelevant whether you bug test the latest CVS or the zip file contents.

Re: XOOPS 2.2.3 Released

hervet Published 08/26/2005 21:55 Friend of XOOPS Joined 11/04/2003 Comments 2267

Monty,

I'm not sure that the content of the cvs is the best version to test. In general that's a version developpers are working on, so it's often in a unfinish state.

Bye,
Hervé

Re: XOOPS 2.2.3 Released

Briese Published 08/26/2005 22:33 Just popping in Joined 01/03/2002 Comments 39

I present Onokazus version:
XOOPS 2.0.11.1-jp
on jp.xoops2.de in a PHP5 environment (German language) stable and to the test was installed the newbb2 and wf-downloads.

Greeting Briese
(ex Admin German support)

Re: XOOPS 2.2.3 Released

Lance_ Published 08/26/2005 22:58 Home away from home Joined 01/12/2004 Comments 983

Thanks to the Devs for the hard work.

Since this is .3 release doesn,t it mean it's a beta type of release, with a .4 being the stable. Or is that numbering convention not used down this far in the row. LOL

Cheers

Re: XOOPS 2.2.3 Released

--Psy Published 08/27/2005 2:01 Updated 08/27/2005 2:06 Just popping in Joined 08/02/2005 Comments 28

Quote:

I just updated from 2.2.2 -> 2.2.3 and got a blank page after upgrade.
Here's what to do:
1: Add 'auth' patch mentioned above.
2: Use 'class/module.textsanitizer.php' from 2.2.2 (2.2.3 fails in line 168 acording to PHP Debug mode!)

Confirmed that this file totally crash PHP 4.2.1 running under Windows 2000/XP. File version 2.2.2 works ok.

Must I report as a bug using the bug report tool?

Re: XOOPS 2.2.3 Released

davidl2 Published 08/27/2005 2:24 Updated 07/13/2007 8:18 XOOPS is my life! Joined 05/26/2003 Comments 4843

Re: XOOPS 2.2.3 Released

JMorris Published 08/27/2005 3:01 Updated 08/27/2005 3:20 XOOPS is my life! Joined 04/11/2004 Comments 2722

First of all, thank you Core Team for all your hard work. It's truly sadening how your work goes unappreciated. Other than a couple little glitches, this seems to be a major improvement over 2.2.2.

@phppp
Your patch worked flawlessly. Thank you!

Now for my bug report...

Any custom block that was center column - center no longer works after upgrade. Left and Right column custom blocks are not affected.

Content of block after upgrade:

1

MySQL Debug:

 SELECT DISTINCT i.instanceid, b.*, i.* FROM myprefix_block_instance i, myprefix_newblocks b, myprefix_block_module_link m WHERE m.block_id=i.instanceid AND i.instanceid IN (1,2,3,4,71,5,7,8,9,10,11,12,44,60,61,139,68,70,72,73,74,75,76,77,80,81,83,84,135,150,149,110,138,109,136,116,117,118,120,141,152,153,154) AND i.visible=1 AND i.bid=b.bid AND b.isactive=1 AND m.module_id=0 AND m.pageid IN (0, 1) ORDER BY i.weight,i.instanceid 
( 0.005817)

PHP and Smarty Debug did not produce any errors.

Server OS: RHEL 4.0 Linux i686 Dual Xeon
Web Server Platform: Apache 1.3.33 (Unix)
PHP Version: 4.3.11
MySQL Version: 4.0.25-standard
Upgrade Path: 2.0.13 >> 2.2.1 >> 2.2.2 >> 2.2.3

I've tried resubmitting the block and I've tried recreating the block. Neither worked. Sorry I don't have more information for you. This is all I could think to check.

If anyone has any ideas, I would greatly appreciate it! I'd really hate to roll my site back to 2.2.2 since this release fixes so many of the bugs that have really been a pain for me.

@Those who whine about this release...

1. RTFM! (The directions were pretty darn simple)
2. Backup before upgrading! (I guess common sense is not that common)
3. Be Grateful, not Greedy! (it's not like you paid for XOOPS!)
4. QUIT YOUR BITCHIN! (If you're not a part of the solution, you're a part of the problem!)

Again, Core Team, THANK YOU for all your hard work and dedication! Much respect due!

Thank you,

James

EDIT: When Content Type is set to any other option than Auto Format (Smilies Disabled), the custom block works. If you set the block to Auto Format (Smilies Disabled), the block content shows up as "1".

Hope this helps track down the problem.

Best Regards,

James

Re: XOOPS 2.2.3 Released - Bugs

barryc Published 08/27/2005 6:50 Just can't stay away Joined 03/20/2004 Comments 480

I'm not sure how much this information will help, but it sure is odd. I have two sites running 2.2.2, one a test site and the other a replacement for my live site, which I'm rebuilding in 2.2.x, to allow me to change some modules being used, etc.

Both are on shared servers with the same hosting company. Both run Linux, Apache 1.3.33, PHP 4.3.11, mySQL 4.3.25 standard.

I updated the test site to 2.2.3 while I was logged in as admin. I updated the system module. Everything went fine and the site worked normally. I could log out and back in again. So, I decided to update the site being rebuilt. Followed the same procedure. Updated the system module and found that center columns displayed the 1 as described above. Then I logged out and tried to log back in. I got the white page.

I don't understand this at all. The two sites are running some common modules and some that are different, but I am not sure how that might cause this difference in behavior.

I have downgraded to 2.2.2 until some fixes are found. However, I do want to echo the sentiments that we should be supportive of the folks doing the core work. I sometimes get concerned that they might walk away when the abuse gets too bad. So, guys, thanks for the work you do on this project.

Barry Cooper

Re: XOOPS 2.2.3 Released

Chappy Published 08/27/2005 7:03 Updated 08/27/2005 7:11 Friend of XOOPS Joined 12/14/2002 Comments 456

Ditto to what you said, JMorris and BarryC.

The running of a professional site requires that webmasters make themselves aware of what updates/upgrades entail, and what their risks are. It has been clear from the outset that 1) The 2.2.x releases are a major leap ahead and have a steeper learning curve; 2) That module development is lagging behind core development, and indeed, it is well known (for those who bother to check the forums and comments) that compatibility has been a significant issue; 3) That updating to the latest releases entails risk that some part of the system will have bugs. I respect some of the support sites wanting to wait for a more stable version before recommending upgrade. You do that because you're smart, and you're following the successes and failures of the new branch. And, I understand the request to mark it as an RC, though not sure I agree.

But, the tone of many of these posts hurts the whole XOOPS project (IMO).

Change is always hard. There will always be bugs in the system, new ways of doing things, and lag time for supportive new tools to develop that serve that change. On one site, one that has a lot of users and needs to be more professional, I'm sticking with the 2.0.13 until the 2.2 branch is more mature. In another site, one that I just play with, I feel excited and happy, in my non-programmer way, to test the new versions, report what I find to the best of my ability, and know that there will be glitches. I know that one of the smart folks around here will fix the bug pretty soon. We're smart people - weigh the risks, wait until some data is in that indicates that develoment is where you think it needs to be, accept that there will be glitches and have fun. I think it's a privilege to be part of testing the next generation of XOOPS and am looking forward to playing with xoopsphere (assuming we haven't chased off devs).

Note: As far as some of the bugs with balnk page are concerned, I ran recovery.php and set phpdebug, and got the Fatal error: getauthconnection()reported by Basby, did the fix by phppp, updated the system module, AND deleted the templates_c file. I am not having any more issues with login. I do get the center-center problems reported, though.

Re: XOOPS 2.2.3 Released

Mithrandir Published 08/27/2005 7:24 XOOPS is my life! Joined 06/21/2003 Comments 6320

Very saddened.

I can't express my feelings with this. I try to make things as well as possible. I try to test things as well as possible. When I don't find any bugs, I find it is time for a release.

You say that we should have a beta tester team. I couldn't agree more. Who is going to step up to this? Please email me at mithrandir at XOOPS dot org

In XOOPS 2.2.3 there seems to be two large bugs:
1) Authentication framework, where apparently the wrong authentication method is applied due to insufficient checking
2) A MyTextSanitizer problem that we will look into

Aparat from that, we get announcements about local support sites not supporting us in XOOPS 2.2
What is that going to help? We don't need you to tell us that things are wrong, we need you to help us make them right.

Releases aren't tested well enough? Help us test it.
Bugs are found? Use the Bug reporting procedures

The modules in the module packages have VERY slight modifications. So if someone has a problem with them
1) I very much doubt it is due to my changes
2) it is easy to see which version is used - "does it work on XOOPS 2.2?" = my modified versions

I will get a diff to the module developers so they can get it incorporated in future versions of their modules, replacing the ones in the current packages.

I'm very sorry about the errors, but I cannot fix what I don't know exists - so help me find these things sooner, please?

Re: XOOPS 2.2.3 Released

Shine Published 08/27/2005 7:52 Just can't stay away Joined 07/22/2002 Comments 822

Today the Dutch support has labeled XOOPS 2.2.x as unstabel. I am very sorry Mith we had to take this step. I know you are doing your very best and understand your dissappointment regarding the given comments.
Meanwhile I am trying to set up a proper Dutch test team, to get more and better bugs report input, so we all together can solve these error problems as soon as possible.

May I advice you to bring back the status to RC ?

Grtz., Shine

Re: XOOPS 2.2.3 Released

Mithrandir Published 08/27/2005 7:55 XOOPS is my life! Joined 06/21/2003 Comments 6320

You don't need to fall down on your knees thanking your deity of choice for XOOPS 2.2.3, but I must admit that I feel like crying right now.

That may not be very manly, but the feedback I get for the work I do is really awful.
I have called out for help on numerous occasions. Anyone remember the time (quite recently) where I asked for help to give the Links section a facelift? I have received ONE reply - and he doesn't respond to my messages about how I foresee the process.

We need beta/RC/Release testers, yes. We sure do. Everyone says so and everyone agrees. Let me see someone actually DO something about it. Contact me, so we can get you organised and know where to send the releases for testing.

We need documenters to look at the changes in XOOPS 2.2 and how they affect modules so module developers know how to make their modules work with XOOPS 2.2
Let me see someone actually DO something about it. Contact me, so we can get you organised and get a dialogue going on how modules should be updated.

We need module testers to test which modules have critters with XOOPS 2.2
Let me see someone actually DO something about it. Contact me, so we can get you organised and get a dialogue going on how modules should be tested.

I'll go off and sob somewhere quiet for the weekend.
Will be back Monday.

Re: XOOPS 2.2.3 Released

teibaz Published 08/27/2005 7:57 Not too shy to talk Joined 06/13/2004 Comments 103

there are some kind of bugs.. for ex, if i'm trying to `view account` (debug mode is on) i got this:

 Notice [PHP]: Only variables should be assigned by reference in file d:wwwkernelobject.php line 819 
Warning [PHP]: session_start(): Cannot send session cache limiter - headers already sent (output started at d:wwwlanguagelithuanianglobal.php:1) in file d:wwwincludecommon.php line 206 
Notice [PHP]: Only variables should be assigned by reference in file d:wwwkernelprofile.php line 93 
Notice [PHP]: Only variables should be assigned by reference in file d:wwwkerneluser.php line 610 
Notice [PHP]: Only variables should be assigned by reference in file d:wwwincludecommon.php line 209 
Notice [PHP]: Only variables should be assigned by reference in file d:wwwincludecommon.php line 223 
Notice [PHP]: Only variables should be assigned by reference in file d:wwwkernelobject.php line 819 
Notice [PHP]: Only variables should be assigned by reference in file d:wwwkernelobject.php line 819 
Warning [PHP]: Cannot modify header information - headers already sent by (output started at d:wwwlanguagelithuanianglobal.php:1) in file d:wwwuser.php line 60

What it could be the solution?

Re: XOOPS 2.2.3 Released

Marco Published 08/27/2005 7:58 Updated 08/27/2005 8:01 Home away from home Joined 03/15/2004 Comments 1256

Quote:

When I don't find any bugs, I find it is time for a release.

well, I would like to hear
"When I don't find any bugs, I find it is time for a RC release."

At local support site, we are VERY disappointed as USERS tell us "why is this version named final version. Seems it has not been tested at all".

I think there is no advantages reinventing the wheel. RC are made, in IT world, to ensure, in front a larger bench of people, version is ready to be published. You know mith how I helped you in 2.1 debugging process.This method was the right one. We must do it again, and it's in your interest too : less critics, increase of speed in development process, every one is collectively responsible for saying : "ok, this RC is bug free, we can tell it one".

I propose several levels of debub parties should be settled :
1/ a few people like support community members and choosen well known debug experts, received betas, this at each step of development process if it is possible
After corrections were made, an RC is released.
2/ This RC is posted officialy at xoops.org. If needed RC2/RC3/ect. are released. Devs ask community to get involved in release protocol "Are you ok with this version to be a final. Be responsible for."

I would love XOOPS use such professionnal methods from now, so XOOPS life will be easier for all of us, collectively, devs, endusers, support team members. I don't want heavy procedures, we have to set pragmatices ones (these were a proposal) but we need somes to bring XOOPS at the right level we want it to be : the best cms.

Let's make people responsible and involved collectively in debug process !

Don't hesitate to call some of us for help. We are here for that.
marco

Re: XOOPS 2.2.3 Released

Mithrandir Published 08/27/2005 8:08 XOOPS is my life! Joined 06/21/2003 Comments 6320

Marco, I agree that this would be the optimal way of doing it, but it does require that there are people willing to do the testing of RC's.

The activation link bug in emails has been there from XOOPS 2.1 to 2.2.2... but noone found it. Will this be changed with a RC release? Depends on whether someone will test it thoroughly. For that, we need someone, who not only wants to test the release for themselves, but feel obligated to test everything. Your debug party was clearly a step on the way, but it was not enough.

We need people from whom we can EXPECT a thorough release, not just hope for it. Will you help me get this team up and running?

@Teibaz:
Check your xoops-root/language/lithuanian/global.php and see if there are whitespaces/new lines BEFORE the

Re: XOOPS 2.2.3 Released

liture Published 08/27/2005 8:12 Updated 08/27/2005 8:13 Just popping in Joined 08/10/2005 Comments 42

The upgrade went ok BUT I am facing 2 problems
1- Wehn registering new users, I always have the error: "Sorry, your password must be at least 3 characters long." even if the password is longer than that

2- Some users reported to me tat they get "No security Tolken.."

Can you please help/advice?

Re: XOOPS 2.2.3 Released

teibaz Published 08/27/2005 8:13 Not too shy to talk Joined 06/13/2004 Comments 103

trim?

Re: XOOPS 2.2.3 Released

Marco Published 08/27/2005 8:19 Updated 08/27/2005 8:23 Home away from home Joined 03/15/2004 Comments 1256

Quote:

but it was not enough.

you made too many modifications in core (many features were provided),
- so it was impossible to test everything in a short time and without becoming fed up.
- i didn't know after a few days what was corrected, what was not
- forum is not the right tool for that, or we should set a rule: a thread per debugger.

For next versions, if possible, could we test per developments phases, to be more efficient.

I'm sure some of us will help. The right way is to make community get involved. For that, let's make it responsible with a clear process where it has some responsabilities. I don't want XOOPS Forum to be a Mc Donald's Desk. Let's make people work more together and work more closely with XOOPS local support communities.

Be sure i will help you in this process, because XOOPS need it.
But i would like to hear other core devs about that. To set that we need everyones approval (why not making a dedicated thread about that into forum?)
Let's go
marco

Re: XOOPS 2.2.3 Released

rowdie Published 08/27/2005 8:20 Just can't stay away Joined 07/21/2004 Comments 846

Mith, it's not enough to throw a RC version at people, give them a few days and hope it's tested thoroughly. Testers need time, and they need to know what been changed so they can focus their tests.

I'll help you get a test team up and running, if you want my help.

Rowd

Re: XOOPS 2.2.3 Released

Mithrandir Published 08/27/2005 8:26 XOOPS is my life! Joined 06/21/2003 Comments 6320

Thanks, Rowd and Marco.

I'll add you to the list that also counts Chappy and Teibaz.

More are welcomed.

Re: XOOPS 2.2.3 Released

Marco Published 08/27/2005 8:27 Home away from home Joined 03/15/2004 Comments 1256

another point : to document/explain changes and awaited impacts/side effects (what we should test first because part was heavy changed",please, so we can test with more efficiency.
like rowdie, we need time, that's why for heavy changes (like 2.1 has), we have to test per phase.

Re: XOOPS 2.2.3 Released

Mithrandir Published 08/27/2005 8:30 XOOPS is my life! Joined 06/21/2003 Comments 6320

Let's take that as soon as we get the team up and running, laying down the "rules of engagement" for releases and testing.

Think about how you would like things to go, write them down and let's get them on the table in a structured manner first thing next week.

I've got to go now, but will be on this on Monday.

Re: XOOPS 2.2.3 Released

teibaz Published 08/27/2005 8:35 Updated 08/27/2005 8:43 Not too shy to talk Joined 06/13/2004 Comments 103

i find out my problems. It's because of bad translation. I'll fix this.

but this wouldn't be if where would be trim, to ensure, that is at the very begining :]

Re: XOOPS 2.2.3 Released

studioC Published 08/27/2005 8:38 Friend of XOOPS Joined 12/07/2003 Comments 922

Hey Jan, keep your head up! no need to feel like you need to cry. You've done a great work. Be proud of that work. Perhaps we should think about the way releasing the versions, true.

Some time ago, a friend of mine started to open a site for betatesters in germany cause he's not that familiar with english language but... what do you think how many are willing to help on that?

HOW MANY are willing to help at all?

I AM a member of XOOPS for the last years but I mostly see people in our community who are crying that something does NOT work or that a feature is missing. Everybody is giving in HIS comment and loves to argue on everythink but less of them are really willing to help. That's reality of XOOPS community.

Those who know me will know which people i mean. Sometimes it's too much if you even want some feedback. Everybody expects the best from XOOPS but not willing to help on this.

Not that much motivating.

You are doing a great job the last month jan but i wonder that you did not kick your XOOPS things out of your window before.

Perhaps we should not make every version available for all members. Can we have an option in userform to set to yes if someone is willing to have some tests and who knows what he does?

And let only those donwload and test these versions?

KISS and THANKS mith.
michael

Re: XOOPS 2.2.3 Released

studioC Published 08/27/2005 8:48 Updated 08/27/2005 8:49 Friend of XOOPS Joined 12/07/2003 Comments 922

To some of YOU!

WHY? WHAT do you think WHY some of the devs have left XOOPS?

Is it because XOOPS is that bad? Can't you imagine that it is a bit of THIS, because of the way YOU are acting?. The way you are reacting?

Ok, some things could have been arranged better but on the one hand YOU are crying for more and more features and sooner realeases ... on the other hand you are moaning and crying and not willing to give someting back (help and at least comments).

Did you thought about HOW a community is working?

Re: XOOPS 2.2.3 Released

Marco Published 08/27/2005 8:53 Home away from home Joined 03/15/2004 Comments 1256

Please discuss release protocol in this thread. Ideas and opinions are awaited !
https://xoops.org/modules/newbb/viewtopic.php?topic_id=40697&forum=11&post_id=178299#forumpost178299

marco
QA Team

Re: XOOPS 2.2.3 Released

kaotik Published 08/27/2005 9:30 Just can't stay away Joined 02/19/2004 Comments 861

Please add me to beta testing group. I'll be happy to help out where I can.

Re: XOOPS 2.2.3 Released

einherjer Published 08/27/2005 9:58 Just popping in Joined 11/08/2002 Comments 30

i really wonder why so many people use a new release on a production site without testing it with their environment - and then cry out when something is not working.

Personally i test all releases with a local copy of my site (Windows users could easily use xampp for this). If this works i try the update again with a copy on my server - it is really no effort to copy the site to a /test dir, protect the /test dir with a .htaccess, make a copy of the db also and adapt mainfile.php to the /test dir.
If everything is ok for me, i have a look on the language files, close my site and do the update - AFTER a full backup.

Remember that XOOPS is available at no charge. You can use it for free. You can also have a look at the source code, modify it and fix errors. So you can at least spend some time for testing.

I would never apply a patch or update to a critical system without testing - even if the software producer marked it as 'stable'.

It makes no difference if a software costs 0,-- or 10.000,-- - their could always be errors that was not found in alpha, beta and RC states of the software.

So calm down and test the next time. Praise the dev team if it works and report errors if it works not (praise the dev team later in this case).

Mith, thanks for your great work and have a nice and recreative weekend. Have some beer and fun and spend no thoughts on errors, XOOPS and php

Ok, maybe Mith have to learn that a RC7 is better than an unstable release - but we have also something to think about: A test before an update is always recommendable!

Re: XOOPS 2.2.3 Released

Horatio Published 08/27/2005 10:15 Just popping in Joined 07/02/2005 Comments 13

The site I have been managing has completely crashed. I am thinking about reverting back to the stable 2.0.13 release...

Truly a shame this. But probably necessary for development.

Good luck!

Re: XOOPS 2.2.3 Released

Chappy Published 08/27/2005 10:46 Friend of XOOPS Joined 12/14/2002 Comments 456

I agree, einherjer. I feel like we bloody our own when we react as has been the case in this thread. I wouldn't do what Mith - or any of the other devs for that matter - do if I were paid.

The thing is that this was supposed to be a bug fix release. Not a bunch of new things, advances, etc. Mith wouldn't have released it unless he felt that he had a quality product - that he just stamped out a few bugs and added a few fixes.

If there had not been any glitches in this release, would anybody have said anything about it? Would anyone have questioned the process of releases? Maybe a few people who do actually do something for xoops, but on the whole, IMO, few others. No, for most of us we would have gone on thinking that the great XOOPS fairy that magically leaves free software in the middle of the night had appeared once more, and we can update our sites with the assurance that we need do no research on our own, nor read any comments, nor do any backup, nor participate in any meaningful wqay.

We have had RC's and betas before put out by Mith. It's not like he is unaware of the process. Most releases with major changes have RC's and betas. But in this case, it was mostly bug fixes.

It was like changing out spark plugs in a car and mistakenly the wires are reconnected out of order. You don't shoot the mechanic, you just fix it. In this case, we criticize publicly in a forum like this, rudely in some cases: Why the hell does someone want to keep doing this? Hey, mistakes happen. Fix it and get over it. Procedural improvements can be easily fixed. People are another matter.

Re: XOOPS 2.2.3 Released

davidl2 Published 08/27/2005 10:50 XOOPS is my life! Joined 05/26/2003 Comments 4843

Exactly Chappy... let's fix the issues with this release so people can use it - and make sure a proceedure is in place for future releases... that way the immediate problem can be dealt with - and it can prevent as much stress happening next time.

Re: XOOPS 2.2.3 Released

mCity Published 08/27/2005 11:01 Updated 08/27/2005 11:07 Just popping in Joined 03/31/2003 Comments 52

Quote:
We need beta/RC/Release testers, yes. We sure do. Everyone says so and everyone agrees. Let me see someone actually DO something about it. Contact me, so we can get you organised and know where to send the releases for testing.

Mr. Mithrandir,

I don't want to post this such comment in xoops.org. However, I was frighten by your above post. Are you going to tell us you didn't have the beta test before? I am thinking if you have studied software development or project management. Your release announcement should show that this is a beta test and you are asking for people to join beta test team.

Please and pls, Mr. Mithrandir, please amend the announcement right now as you should know how many people are still going to download the file and upgrade their site in every minutes.

Regards and Best Regards.
mCity

Re: XOOPS 2.2.3 Released

davidl2 Published 08/27/2005 11:11 XOOPS is my life! Joined 05/26/2003 Comments 4843

mCity - I think most issues have been solved in this thread... I think Mith is talking about future releases..

Things are tested, I am certain, but with something as complex as XOOPS - not every factor can be found immediately... and in the case of this release, there where problems with 2.2.2 - which needed to be sorted as soon as possible.

2.2.3 (with the above fixes) seems to work much better than 2.2.2 - so this was an improved version... we just need to make sure that future ones are as perfect as possible.

So - lets look into how things can be improved, not complaining about the current situation....

Re: XOOPS 2.2.3 Released

DCrussader Published 08/27/2005 11:24 Friend of XOOPS Joined 07/04/2005 Comments 573

The most stable version in XOOPS are:

2.0.13 (not 2.0.13.1)
and 2.0.7.3, this version Rocks

Mith one question if u allow ?

What fixes the stable 2.0.13.1 against 2.0.13, why the registration doesnt work ?

Re: XOOPS 2.2.3 Released

m0nty Published 08/27/2005 11:37 XOOPS is my life! Joined 10/24/2003 Comments 3337

hhttp://72.29.75.243/~wwcncom/mansfieldcc/index.php

is XOOPS 2.0.13.1, u tell me if the registration doesn't work?

Re: XOOPS 2.2.3 Released

JMorris Published 08/27/2005 11:58 Updated 08/27/2005 12:25 XOOPS is my life! Joined 04/11/2004 Comments 2722

As you know, with college and work, my schedule is tight, but I will volunteer to help in any way I can, as often as I can.

I'm most experienced with themes and templates. I can focus my attention in these areas to make the most effecient use of my time. There seem to be quite a few little bugs with the new default theme, so I will start working on fixes ASAP.

I wish I could offer more.

Best Regards,

James

BTW...
http://mywebresource.com is running 2.2.3

There's only two problems so far that I haven't been able to fix:

1. The block issue reported above
2. "Sorry, your password must be at least 3 characters long." when users try to register, even if the password is long enough.

EDIT:Work-around for registration problem:
I replaced the 2.2.3 register.php with the 2.2.2 version and now registration works.

I will submit this to the bug tracker after I see if I can fix it.

Best Regards,

James

Re: XOOPS 2.2.3 Released

phppp Published 08/27/2005 12:20 XOOPS Contributor Joined 01/25/2004 Comments 2857

I would like to let some of us know:
Before Mith decided to make the release, he inquired of the Core Team members, no objection.
Before he released the packages, he inquired of Core members about bugs. No new bug or problem reported.

It seems test from only core members is far from adequate.
As it has been discussed before, a Test Team composed by community users is really important, which could provide usage info from different environments and could discover potential problems from users with no PHP or XOOPS knowledge.

So, if you have suggestions or willing to help for Test Team, visit:
https://xoops.org/modules/newbb/viewtopic.php?topic_id=40697

If you have any bugs/problems, visit:
http://sourceforge.net/tracker/?func=add&group_id=41586&atid=430840

Re: XOOPS 2.2.3 Released

phppp Published 08/27/2005 12:30 XOOPS Contributor Joined 01/25/2004 Comments 2857

"Sorry, your password must be at least 3 characters long."

modules/profile/register.php
line #75
if (!empty($xoopsModuleConfig['minpass']) && [b][color=FF0000]strlen[/color][/b]($_POST['pass']) <$xoopsModuleConfig['minpass']) {

The bug was introduced by me when making a quick fix.

Re: XOOPS 2.2.3 Released

WarDick Published 08/27/2005 12:34 Just can't stay away Joined 09/13/2003 Comments 890

Quote:
My 2.2.3 test site is working ok so far ...

Things are looking up! How about center blocks? I have a differnet set of modules working and most are working correctly but no center blocks.

What version of modules.textsanitizer are you using?

Re: XOOPS 2.2.3 Released

Lance_ Published 08/27/2005 12:44 Home away from home Joined 01/12/2004 Comments 983

I commend Myth for the manner in which he's taken the criticism. Bite down on it and move forward.

I am willing to help in testing and anything else that could help the community out.

As phppp said, the core developpers doing the testing is not adequate, they won't test it like some of us poor sobs will try to use it. LOL

Peace

Re: XOOPS 2.2.3 Released

JMorris Published 08/27/2005 12:55 Updated 08/27/2005 13:30 XOOPS is my life! Joined 04/11/2004 Comments 2722

@phppp

Man, that was fast! Thanks a lot!

I'll update my files and let you know the results.

Best Regards,

James

EDIT: Worked like a charm. Thanks!

Re: XOOPS 2.2.3 Released

carnuke Published 08/27/2005 12:57 Home away from home Joined 11/05/2003 Comments 1955

Quote: Mithrandir
Quote:
You don't need to fall down on your knees thanking your deity of choice for XOOPS 2.2.3, but I must admit that I feel like crying right now.

That may not be very manly, but the feedback I get for the work I do is really awful.
I have called out for help on numerous occasions. Anyone remember the time (quite recently) where I asked for help to give the Links section a facelift? I have received ONE reply - and he doesn't respond to my messages about how I foresee the process.

We need beta/RC/Release testers, yes. We sure do. Everyone says so and everyone agrees. Let me see someone actually DO something about it. Contact me, so we can get you organised and know where to send the releases for testing.

We need documenters to look at the changes in XOOPS 2.2 and how they affect modules so module developers know how to make their modules work with XOOPS 2.2
Let me see someone actually DO something about it. Contact me, so we can get you organised and get a dialogue going on how modules should be updated.

We need module testers to test which modules have critters with XOOPS 2.2
Let me see someone actually DO something about it. Contact me, so we can get you organised and get a dialogue going on how modules should be tested.

I'll go off and sob somewhere quiet for the weekend.
Will be back Monday.

It is very distressing to read this whole thread and especially to see Jan's comments here.

We need to be very careful as a community that we do not forget that XOOPS is an open source development project and that nobody has any rights to a guaranteed quality product!

That said, I nust stand and support Mithrandir, not because I am a core team member, but simply as a grateful XOOPS user who appreciates the amount of time and skill that Jan has inputed into this project.

I am saddened at the vitrionic comments that are directed to this release and the developers. They have inputed thousands of hours total of development time and testing with NOTHING in return, only to be met with what criticism.

Yes, I have tested this release myself and yes, there are problems which have already been detailed... BUT, it all my testing was on a test site and not a production site.

My point ... there has been no harm done to my production sites, so I dont have to sweat the small stuff.

Does anyone leave their car or home without locking the door? no, you take adequate precautions, even if you live in a safe neighbourhood.

Well, a new release, should be a 'safe neighboirhood' but you still lock the door to yoiur production site untill, you have prooved the system.

Mithrandir, and other developers who have given so much to advance the cause of of XOOPS: my sincere thanks go to you all for your time, committment and above all resiliance to weather the storms of criticism. Be assured, there are those who appreciate and understand the ethics of open source and say 'well done for all your efforts, this is not a black day'

Richard

Re: XOOPS 2.2.3 Released

mCity Published 08/27/2005 15:13 Updated 08/27/2005 15:46 Just popping in Joined 03/31/2003 Comments 52

Quote:
I think Mith is talking about future releases..

David, as you said, and that was why I posted a request to Mith to rollback to finish a complete beta test for this release that he ignored. OK, you all were eager to fix problems in 2.2.2 is fine. However, the announcement and the release will affect all those webmaster who are still running in version other from 2.2.2. Imagine how much are they who will upgarde and get problem in the coming two weeks. Compare the current counter and the counter after two weeks, then you will feel the power to destroy their trust on all hard working core developers just by one careless release.

How much the first statement, "The XOOPS Core Development Team is happy to release..", showed to all webmaster "Trust us without reservation". Plesae understand what my point is! And your German partner just proved my concern. Is there any actual problem if this is just the beta test and release it a few weeks later?

As you should know that the original XOOPS creator, Onokazu, announced in his site the reason why he chose to quit XOOPS to build xoopscube, proclaimed to be a stable and stable and stable XOOPS distribution. He warned that the XOOPS here would be no longer stable. Why here still made his warning come true!

Now just a few hours pass, few weeks come.
Rollback is what you have to do to start the improvement right now.

Please, please rollback now!
mCity

Re: XOOPS 2.2.3 Released

davidl2 Published 08/27/2005 20:27 XOOPS is my life! Joined 05/26/2003 Comments 4843

I hope we are starting the improvements off now... between the community - as it should be.

Let us get this current release stable first - fixing the errors people have found - and make sure that future releases follow a proceedure with more testing etc.

This release is out now... let's just make sure it's sorted to everyones satisfaction asap - and that all issues are fixed.... I imagine that in a day or so we will see a version with the relevent issues fixed (not a new version number i hope... as it only seems to be a few changes required)

Onokazu is certainly entitled to his opinion... I also agree that perhaps more and improved testing should have been done... and it was tested amongst the core coders (see Phppp's earlier post)... but obviously some things where missed...

Let's not waste time complaining about problems... lets use the situation to make sure they don't happen in the future, and to ensure that we get a smoother journey in the future.

One thing... I am not a core programmer, I am not a module programmer... I barely understand php coding myself.... I count myself as an ordinary XOOPS user - who appreciates the work that is done on his behalf, and wants to give as much as he takes from the community in my power.... I don't like people complaining ... but if they have reasons, lets look at them.

The complaints boiled down to:

1 - Too many releases

Perhaps... perhaps not.... there was security issues that needed fixing recently, so these needed a new version. Also new bugs where found ... these also needed fixing.... so if these are needed, surely it is in everyones interest to sort them out as soon as possible.

2 - Not enough testing

Xoops core has been tested by core programmers.... and various key persons... that is from what I understand. I don't know how it is tested, but I am sure that it is NOT just released as a new version as soon as Mith is happy with it! I would guess that several people would have said that it appears to work fine for them, and to fix issues they have come across.

Now - it is obvious that the proceedure may be in need of change.

A thread has been created to look into this issue.. and to set up a team of people to test new releases. This is the start of a considerable improvement in my eyes....

The initial release of XOOPS 2.2 had a regular nightly build release... and several beta releases... and this was a good idea in some ways... However, I felt that reading the postings of the time - that some issues where overlooked by the shear volume of people asking similar questions.

A team of people... perhaps only 12 or so... who have experience with XOOPS - but are able to think from an ordinary users point of view - and able to give consise error reports - could achieve more than having hundreds of people giving the same answers and asking the same questions.

Anyway - we know the situation - let's get it fixed and get things right for the future!

Re: XOOPS 2.2.3 Released

Calipsy Published 08/27/2005 20:48 Just popping in Joined 04/30/2003 Comments 87

I also had problem with the upgrade patch, however, soon as I followed the intructions to modify the class/auth/authfactory.php my XOOPS site is back and working like a charm!

Thanks for this release!

Re: XOOPS 2.2.3 Released

webfmpl Published 08/27/2005 21:24 Just popping in Joined 12/03/2004 Comments 19

Main core bugs are fixed, but does anyone know what happened with Xoopsgallery module. I have same errors as @WarDick. They appear after 2.2.2 > ....3 upgrade.
Quote:
... Prior to upgrade xoopsgallery would work. Now it does not. Now where the album name was I get nl2br instead. See post above it also has nl2br referenced in it.

P.S.
Great work, thanks to X-core Dev. Team.

Re: XOOPS 2.2.3 Released

kapeman Published 08/27/2005 22:54 Just popping in Joined 05/03/2005 Comments 87

The fix for the strange text with album names in gallery was provided by marook:

quote:

"2: Use 'class/module.textsanitizer.php' from 2.2.2 (2.2.3 fails in line 168 acording to PHP Debug mode!)
EDIT: The file is part of 2.2.1 !"

That fixed the same problem I had with xoopsgallery.

Thanks marook!!!

Re: XOOPS 2.2.3 Released

marook Published 08/27/2005 22:55 Friend of XOOPS Joined 09/09/2002 Comments 89

Quote:
...but does anyone know what happened with Xoopsgallery module...

What??? 1.3.3.7 is working fine:
http://www.saltocity.dk/modules/xoopsgallery/

Site is 2.2.3

Re: XOOPS 2.2.3 Released

JMorris Published 08/27/2005 23:36 XOOPS is my life! Joined 04/11/2004 Comments 2722

Quote:
A team of people... perhaps only 12 or so... who have experience with XOOPS - but are able to think from an ordinary users point of view - and able to give consise error reports - could achieve more than having hundreds of people giving the same answers and asking the same questions.

Perhaps a clear, consice definition of what would be considered a good bug report would be helpful?

Best Regards,

James

Re: XOOPS 2.2.3 Released

LazyBadger Published 08/28/2005 0:07 Home away from home Joined 06/07/2004 Comments 1187

Something like it?

"Hello, XOOPS Developers

I'm using XOOPS 2.2.2 (result of installation XOOPS-Nightlies and incremental updates, install of full package 2.2.1 and applying patch 2.2.1-2.2.2) on PHP v. 4.3.5 with MySQL 4.0.18 and want to report a bug:

Bug Description:
Some block setting for block "Site Info" from module System are ignored.

Even if I have enable "Show administrators group" in block options, two users with admin's right aren't shown in block. I'm using default template-set

Steps for reproduce a bug
1. Add "Site Info" to the list of used blocks
2. Edit block and enable to show admins
3. Configure other settings as you want
4. Check block on frontend page and detect missing part of information

Additional information:
Block in question can be viewed here, admin rights granted to responsible person on request"

Re: XOOPS 2.2.3 Released

JMorris Published 08/28/2005 0:21 Updated 08/28/2005 0:42 XOOPS is my life! Joined 04/11/2004 Comments 2722

Thank you LB!

That makes things a LOT clearer.

In addition to what you've mentioned above, perhaps the following might be useful as well:

1. PHP, MySQL, and Smarty Debug output, if applicable
2. Apache/IIS version
3. Server OS (Linux/Windows)
4. If a solution is found, a detailed description of how to apply it

Thanks again!

James

Proper Bug Report (Was - Re: XOOPS 2.2.3 Released)

LazyBadger Published 08/28/2005 0:29 Home away from home Joined 06/07/2004 Comments 1187

Or this form
"
Bug description:
Users group management broken in XOOPS 2.2.2
/modules/system/admin.php?fct=groups and any operation on this page generate errors with references to file groupform.php
/modules/system/admin/themes/xoops_version.php): failed to open stream: No such file or directory in file modules/system/admin/groups/groupform.php line 45
/modules/system/admin/themes/xoops_version.php' for inclusion (include_path='.:/usr/lib/php:/usr/lib/php/pear') in file modules/system/admin/groups/groupform.php line 45
File modules/system/admin/groups/groupform.php has these keywords
$Id: groupform.php,v 1.9 2005/08/08 06:29:29 skalpa Exp $
and md5sum 629fcf06d34df49c483ad5ca55972f62

Steps to reproduce a bug:
1. Get XOOPS 2.2.2 site with admin access
2. Login as admin
3. Enable PHP-debug in General Preferences
4. Execute from admin-menu Users - Groups"

Re: Proper Bug Report (Was - Re: XOOPS 2.2.3 Released)

JMorris Published 08/28/2005 0:44 Updated 08/28/2005 0:56 XOOPS is my life! Joined 04/11/2004 Comments 2722

Based on your suggestion and the above additional information, I've come up with the following "cookie cutter" template.

Quote:

Polite Opening,

I'm experiencing a bug after [installing | upgrading to] and would like to report a bug.

Bug Description:
----------------
Provide as much information regarding the bug as possible. Include any appropriate information such as, what you did prior to noticing the bug, what are the affects of the bug, does the bug affect all users, is the bug viewable in all browsers, etc.

Steps for reproduce the bug:
----------------------------
In clear, concise, numbered steps, walk the Devs through the proces of reproducting the error, if possible.

Example:
1. Add "Site Info" to the list of used blocks
2. Edit block and enable to show admins
3. Configure other settings as you want
4. Check block on frontend page and detect missing part of information

Debug Output:
-------------
Put your PHP, MySQL, and Smarty Debug output here. Seperate with headings. If you are getting a White Screen of Death (WSOD), paste whatever php output is on the screen.

Example:
PHP Debug Output:

MySQL Debug Output:

Additional information:
-----------------------
The bug in question can be viewed at (provide indicators of where to look on the page). Admin rights granted to responsible person on request (optional, but may be helpful).

Posible solution:
-----------------
If possible, provide a detailed description of how to fix the problem. As above, write in clear, conscise, numbered steps that the Devs can easily follow.

Server Information:
------------------

Polite Closing,

Your Name
your@email.com
http://yourwebsite.com/

Would a Core Team member verify that this would be what you are looking for in a bug report?

Thank you,

James

Re: Proper Bug Report (Was - Re: XOOPS 2.2.3 Released)

Dave_L Published 08/28/2005 3:05 XOOPS is my life! Joined 11/07/2003 Comments 2277

The "cookie cutter" template looks good to me.

Some of the sections could be omitted, depending on the situation.

If applicable, the report should also specify information about current theme and modules.

The email address isn't necessarily required (I don't like posting email addresses in public), although there should be some means provided to contact the reporter for additional information.

Re: Proper Bug Report (Was - Re: XOOPS 2.2.3 Released)

LazyBadger Published 08/28/2005 3:23 Home away from home Joined 06/07/2004 Comments 1187

When we report about core issues, themes and modules play nothing

Re: Proper Bug Report (Was - Re: XOOPS 2.2.3 Released)

JMorris Published 08/28/2005 3:43 XOOPS is my life! Joined 04/11/2004 Comments 2722

Quote:
When we report about core issues, themes and modules play nothing

I don't agree. Depending on the situation, reporting the installed modules and the theme used very well may help the Devs track down whether the issue is with the core or with a third-party component.

Keep in mind, this "cookie cutter" template is targeted to the inexperienced XOOPS user, not experienced users or developers. I'm sure there have been many instances where a bug has been reported that, in reality, had little or nothing to do with the core, but was caused by a third-party component. With the recent compatibility issues, I'm sure this will increase.

Just MHO.

Best Regards,

James

Re: XOOPS 2.2.3 Released

--Psy Published 08/28/2005 3:53 Just popping in Joined 08/02/2005 Comments 28

Another one, too silly to be reported as a bug but a detail that perhaps worth to be corrected:

theme_moduleadmin.html
<div id='buttontop'>      <table style="width: 100%; padding: 0; " cellspacing="0">          <tr>              <td style="width: 70%; font-size: 10px; text-align: left; color: #2F5376; padding: 0 6px; line-height: 18px;">                  <a href="../index.php"><{$smarty.const._AD_NAV_MODHOME}>a>              td>              <td style="width: 30%; font-size: 10px; text-align: right; color: #2F5376; padding: 0 6px; line-height: 18px;">                  <b><{$modulemenu.name}> <{$smarty.const._AD_NAV_MODADMIN}>b> <{$modulemenu.breadcrumb}>              td>          tr>      table> div> [color=FF0000] <br style="clear:both;" />[/color] <div id='buttonbar'>      <ul>          <{foreach item=link from=$modulemenu.links key=id}>              <{if $id == $modulemenu.current}>                  <li class='current'>              <{else}>                  <li>              <{/if}>                  <a href='<{$link.link}>'><span><{$link.title}>span>a>              li>          <{/foreach}>      ul> div> <br style="clear:both;" />

This solves the blank space that breaks some admin's menu tag box on IE.

Re: XOOPS 2.2.3 Released

Marco Published 08/28/2005 7:13 Home away from home Joined 03/15/2004 Comments 1256

A new summary of our Release Protocol and Methods collective brainstorming is available here

https://xoops.org/modules/newbb/viewtopic.php?topic_id=40697&start=20#forumpost178495

Marco
QA Team

Re: XOOPS 2.2.3 Released

damaster Published 08/28/2005 13:18 Just can't stay away Joined 05/11/2003 Comments 556

Nice to see u come up with the new ergonomic interface and the "packages feature"...
Hope Xoops, once debugged, will be back on the road cause it deserve to compete with great cms.

Well, here at the A.M. Lab R&D and University of Geneva, people have chosen Dokeos running on Mandriva Linux, who also choose Dokeos who's looking after a cms solution [hint]

Dokeos, development :

Quote:
Our programming philosophy is inspired from Extreme Programming; our interface philosophy benefits from the Usability theory developed by Jakob Nielsen.

Working with us means:

* you keep control on the evolution of the software you ordered;
* you can follow the evolution of the programme step by step;
* you can change your mind in the middle of development process;
* you can see interface before programme is written;
* you get just enough of what you asked for;
* your interface remains simple;
* you are confronted to other people's views on the same problems,
which will help you take the better decision;
* good teaching remains the objective and it is never alienated to any
technical autonomous ambition.

Good luck to you too and XOOPS Community, keep that good work, professionally!

Waiting for a more mature release!

Re: XOOPS 2.2.3 Released

Marco Published 08/28/2005 16:53 Updated 08/28/2005 16:54 Home away from home Joined 03/15/2004 Comments 1256

A new release protocol proposal is up (it's quite a final one)

https://xoops.org/modules/newbb/viewtopic.php?topic_id=40697&start=30#forumpost178558

Core Devs, what's your opinion
please give us feedbacks
marc
QA team

Re: XOOPS 2.2.3 Released

phppp Published 08/28/2005 17:02 XOOPS Contributor Joined 01/25/2004 Comments 2857

Developers will be back on xoops.org on Monday.

.... Utter Dismay

shiningstar Published 08/28/2005 20:04 Just popping in Joined 08/28/2005 Comments 1

I DO NOT BELIEVE THIS,

remember you have no rights with xoops, no waranties any and all support provided by Mithrandir and his Developers is purely out of the goodness of their hearts so show some DAMN RESPECT!

Mithrandir, I will email you as well, im no PHP developer and I dont have a clue how I can help, tell me what I can do and I will try...

Unlike many of you I dont know php and I am no debugger! But I am willing to help!

The rest of you, use the new version, REPORT THE BUGS and help XOOPS get this release sorted!

Re: XOOPS 2.2.3 Released

gestroud Published 08/28/2005 23:05 Home away from home Joined 12/22/2004 Comments 1538

XOOPS has helped me get 25 sites up and online, and it hasn't cost me anything but time. I'm more than happy to help with testing & debugging in any way that I can.

BE ADVISED:

1. I'm good at HTML, but don't know php.

2. I'm not ready to install the new version on a production site, but I do have the XSAS installed on my computer.

Sign me up, coach!

Re: XOOPS 2.2.3 Released

Mithrandir Published 08/29/2005 6:35 XOOPS is my life! Joined 06/21/2003 Comments 6320

OK, I'm back.

Got plenty of tasks today, so sorry if I miss anything.

First I'll get briefed on my received emails, the beta testing thread that's going on, the PM's I've received and the backlog of translations and modules that have been submitted but not approved yet.

I will discuss this with the others, but imagine that XOOPS 2.2.3 will be re-labeled to an RC1 and we'll work with the new beta testing team to release a RC 2 within the next month.

Thanks for your support and dedication - especially to those that have now stepped up to help with the testing process.

Re: XOOPS 2.2.3 Released

russel1 Published 08/29/2005 7:00 Just popping in Joined 01/12/2005 Comments 16

Although I really appreciate the work that is done with 2.2.x series. There should be done something with the releases. It gives XOOPS a bad name. So until 2.2.x is in a better shape I will stick with 2.0.13.1.
I really hope you don't drop the 2.0.x series soon and provide security fixes until 2.2.x is better.
What are the plans regarding 2.0.x anyway?

Re: XOOPS 2.2.3 Released

pdajunkee Published 08/29/2005 7:33 Just popping in Joined 09/03/2004 Comments 53

Chado: I stumbled across a similar problem with my main menu dissapearing. Most likely user error on my part.

I cloned my template and then listed the system templates. I had to re-generate system_block_mainmenu.html and system_block_siteinfo.html.

Everything is working smoothly now. This may not be the best way to fix, but it worked for me.

Re: XOOPS 2.2.3 Released

espressobuff Published 08/29/2005 7:38 Just popping in Joined 06/27/2005 Comments 2

Kindly also check /footer.php.

one of the admin pages of my module calls xoops_cp_footer but it dies within footer.php apparently because XOOPS_ROOT_PATH isn't defined.

my page run after i comment these lines:

//lines 27-29 of /footer.php
//if (!defined("XOOPS_ROOT_PATH")) {
// die("XOOPS root path not defined");
//}

Email activation Bug

liture Published 08/29/2005 8:58 Just popping in Joined 08/10/2005 Comments 42

After registration the link sent to the email for activation has duplicated address and even if it is removed it will not work

http://mysite.comhttp://mysite/modules/profile/activate.php?op=actv&id=4&actkey=xxxcxxxx

Please advice

Re: XOOPS 2.2.3 Released

nachenko Published 09/02/2005 19:09 Quite a regular Joined 01/18/2005 Comments 356

It WORKS!!!!!!!!!!!!!

Applied both fixes in the code: The first one on class/auth/authfactory.php, specified just in the beginning of this page, and the other one fixed by phppp:

Quote:
"Sorry, your password must be at least 3 characters long."

modules/profile/register.php
line #75

if (!empty($xoopsModuleConfig['minpass']) && strlen($_POST['pass']) <$xoopsModuleConfig['minpass']) {

Thanks. It works ROCK SOLID with News and WFSection. Now i have to test MyAlbum module. I'm even thinking about going on opening friday next week.

Check here:

http://www.ecro2006.com/eng

Thanks, thanks a lot.

Re: XOOPS 2.2.3 Released

mario Published 09/03/2005 20:54 Just popping in Joined 12/29/2002 Comments 48

i have the exact same problem.

Re: XOOPS 2.2.3 Released

mario Published 09/04/2005 18:11 Updated 09/05/2005 7:46 Just popping in Joined 12/29/2002 Comments 48

i can not edit useres anymore.

when in the groups section in noticed that the "edit user" box has no checkmark in it.

i put one in, click submit

get the database updated ok

go back to look in groups

still no checkmark in the "edit user"

can anyone help

Re: Email activation Bug

famaTV Published 09/24/2005 15:01 Just popping in Joined 09/14/2005 Comments 8

I am facing the same problem with the email activation .... using the latest XOOPS 2.2.3

Re: XOOPS 2.2.3 Released

xzone9 Published 12/28/2005 1:12 Just popping in Joined 07/06/2004 Comments 2

How did you repair the errors? I have the same results. Thanks-

Login

Username

Password

Remember me

Register now! | Lost Password?

Search

Advanced Search

Recent Comments

Re: New Admin Theme for XOOPS (Beta)

Publisher liomj 10/28/2024 23:33

Sanford Pharmacy: Exceptional Pharmacy Services Tailored to You

Publisher donaldjohn 10/16/2024 9:53

Re: New Admin Theme for XOOPS (Beta)

Publisher walkero 10/15/2024 18:30

Re: XOOPS 2.5.12 Beta-2 available for Testing

Publisher cadch 08/30/2024 6:33

Re: XOOPS 2.5.12 Beta-2 available for Testing

Publisher cadch 08/30/2024 6:30

Who's Online

242 user(s) are online (5 user(s) are browsing XOOPS News)

Members: 0

Guests: 242

more...

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 }}

Archives

News archives

January 2017

November 2016

October 2016

September 2016

August 2016

July 2016

June 2016

May 2016

April 2016

March 2016

February 2016

January 2016

December 2015

November 2015

October 2015

September 2015

July 2015

May 2015

April 2015

March 2015

February 2015

January 2015

December 2014

November 2014

October 2014

September 2014

August 2014

July 2014

June 2014

May 2014

April 2014

March 2014

February 2014

January 2014

December 2013

November 2013

October 2013

September 2013

August 2013

July 2013

June 2013

May 2013

April 2013

March 2013

February 2013

January 2013

December 2012

November 2012

October 2012

September 2012

August 2012

July 2012

June 2012

May 2012

April 2012

March 2012

February 2012

January 2012

December 2011

November 2011

October 2011

September 2011

August 2011

July 2011

June 2011

May 2011

April 2011

March 2011

February 2011

January 2011

December 2010

November 2010

October 2010

September 2010

August 2010

July 2010

June 2010

May 2010

April 2010

March 2010

February 2010

January 2010

December 2009

November 2009

October 2009

September 2009

August 2009

July 2009

June 2009

May 2009

April 2009

March 2009

February 2009

January 2009

December 2008

November 2008

October 2008

September 2008

August 2008

July 2008

June 2008

May 2008

April 2008

March 2008

February 2008

January 2008

December 2007

November 2007

October 2007

September 2007

August 2007

July 2007

June 2007

May 2007

April 2007

March 2007

February 2007

January 2007

December 2006

November 2006

October 2006

September 2006

August 2006

July 2006

June 2006

May 2006

April 2006

March 2006

February 2006

January 2006

December 2005

November 2005

October 2005

September 2005

August 2005

July 2005

June 2005

May 2005

April 2005

March 2005

February 2005

January 2005

December 2004

November 2004

October 2004

September 2004

August 2004

July 2004

June 2004

May 2004

April 2004

March 2004

February 2004

January 2004

December 2003

November 2003

October 2003

September 2003

August 2003

July 2003

June 2003

May 2003

April 2003

March 2003

February 2003

January 2003

December 2002

November 2002

October 2002

September 2002

August 2002

July 2002

June 2002

May 2002

April 2002

March 2002

February 2002

January 2002

December 2001

December 1969

About us

About Xoops

Why XOOPS?

Board of Advisors

Xoops Innovators

XOOPSers

XOOPS Etiquette

Learn

Books

FAQ

Core Guides

Module Guides

Use

Download Xoops

Module @ GitHub

Themes@ GitHub

Languages @ GitHub

Support Forums

International Support

Develop GitHub

Core @ GitHub

Module @ GitHub

Themes@ GitHub

Languages @ GitHub

Legacy XOOPS @ SourceForge

Coding Standards PSR-2

Contribute

$$$ Donations

Join Team

Core @ GitHub

Module @ GitHub

Themes@ GitHub

Languages @ GitHub

Report Core Bug

Connect

Facebook

LinkedIn

Flickr

YouTube

Ohloh

Twitter

Terms of Use | Privacy Policy | Hosted by Arvixe Hosting |

Design: B.Heyula

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