XOOPS 2.3.1 Final Is Released

sign petition today!

Local Support

Make a donation

Search

Advanced Search

Twitter News

Cumulus Tag Cloud

more...

New Users

Registering user

# 117251

gerd69

Welcome to XOOPS!

News Archives

Next article » « Previous article

Posted by phppp on 2008/10/11 9:50:00 (12178 reads) | Posted on XOOPS

The XOOPS Development Team is pleased to announce the release of XOOPS 2.3.1 Final.

This release is mainly focused on bug fixes for XOOPS 2.3.0 release according to community feedback.
A couple of bugs in upgrade scripts from 2.2 to 2.3 have been fixed, as well as profile field access problems.
Debug information visibility has been improved according to community demands, debug information level is enabled as a temporary solution.
Meanwhile XOOPS news aggregator has been improved for non UTF-8 charset websites, multiple feeds are enabled.

Download from Sourceforge repository.

System requirements
-----------------------------------

PHP:
Any PHP version >= 4.3 (PHP 4.2.x may work but is not officially supported, PHP 5.0+ is strongly recommended)

MySQL:
MySQL server 3.23+ (MySQL 5.0+ is strongly recommended)

Web server:
Any server supporting the required PHP version (Apache highly recommended)

Downloading XOOPS 2.3.1
-----------------------------------

Your can get this release package from the sourceforge.net file repository.
Both .zip and .gz archives are provided.

Installing XOOPS 2.3.1
-----------------------------------

1. Copy the content of the htdocs/ folder where it can be accessed by your server
2. Ensure mainfile.php and uploads/ are writable by the web server
3. For security considerations, you are encouraged to move directories xoops_lib (for XOOPS libraries) and xoops_data (for XOOPS data) out of document root, or even change the folder names.
4. Make the directory of xoops_data/ writable; Create and make the directories of xoops_data/caches/, xoops_data/caches/xoops_cache/, xoops_data/caches/smarty_cache/ and xoops_data/caches/smarty_compile/ writable.
5. Access the folder where you installed the htdocs/ files using your web browser to launch the installation wizard

We also highly recommend the installation of the PROTECTOR module which will bring additional security protection and logging capabilities to your site.

To install protector module with a fresh new installation of XOOPS 2.3.1, copy /extras/mainfile.dist.php.protector to /htdocs/mainfile.dist.php BEFORE installing XOOPS.
To install protector module with upgrading from a previous version to XOOPS 2.3.1, copy /extras/mainfile.dist.php.protector to /upgrade/upd-2.0.18-to-2.3.0/mainfile.dist.php BEFORE upgrading XOOPS.

Upgrading from a previous version
-----------------------------------

Upgrading from XOOPS 2.3.0 (easy way)
1. Get the update package from the sourceforge file repository
2. Overwrite your existing files with the new ones
3. Move the "upgrade" folder inside the "htdocs" folder (it's been kept out as it's not needed for full installs) on your local machine
4. Access /upgrade/ with a browser, and follow the instructions
5. Follow the instructions to update your database
6. Delete the upgrade folder from your server
7. Update the "system" module from the modules administration interface, other modules, especially "profile" are recommended to update as well

Upgrading from XOOPS 2.0.* above 2.0.14 and 2.2.* (using the full package)
1. Move the "upgrade" folder inside the "htdocs" folder (it's been kept out as it's not needed for full installs) on your local machine
2. Delete htdocs/mainfile.php, htdocs/install/, htdocs/cache/, htdocs/extras/, htdocs/template_c/, htdocs/themes/ and htdocs/uploads/ from the "htdocs" folder on your LOCAL machine
3. Upload the content of the htdocs folder on your LOCAL machine over your existing files on your server
4. For security considerations, you are encouraged to move directories xoops_lib (for XOOPS libraries) and xoops_data (for XOOPS data) out of document root, or even change the folder names.
5. Make the directory of xoops_data/ writable; Create and make the directories of xoops_data/caches/, xoops_data/caches/xoops_cache/, xoops_data/caches/smarty_cache/ and xoops_data/caches/smarty_compile/ writable.
6. Ensure the server can write to mainfile.php
7. Access /upgrade/ with a browser, and follow the instructions
8. Follow the instructions to update your database
9. Write-protect mainfile.php again
10. Delete the upgrade folder from your server
11. Update the "system" module from the modules administration interface, other modules are recommended to update as well

Upgrading from any XOOPS ranging from 2.0.7 to 2.0.13.2 (using the full package):
1. Move the "upgrade" folder inside the "htdocs" folder (it's been kept out as it's not needed for full installs) on your LOCAL machine
2. Delete htdocs/mainfile.php, htdocs/install/, htdocs/cache/, htdocs/extras/, htdocs/template_c/, htdocs/themes/ and htdocs/uploads/ from the "htdocs" folder on your LOCAL machine
3. Upload the content of the htdocs folder on your LOCAL machine over your existing files on your server
4. Delete the following folders and files from your server (they belong to an old version):
* class/smarty/core
* class/smarty/plugins/resource.db.php
5. Ensure the server can write to mainfile.php
6. For security considerations, you are encouraged to move directories xoops_lib (for XOOPS libraries) and xoops_data (for XOOPS data) out of document root, or even change the folder names.
7. Make the directory of xoops_data/ writable; Create and make the directories of xoops_data/caches/, xoops_data/caches/xoops_cache/, xoops_data/caches/smarty_cache/ and xoops_data/caches/smarty_compile/ writable.
8. Access /upgrade/ with a browser, and follow the instructions
9. Write-protect mainfile.php again
10. Delete the upgrade folder from your server
11. Update the "system" module from the modules administration interface, other modules are recommended to update as well

Upgrading a non UTF-8 site:
UTF-8 encoding has been introduced into XOOPS 2.3 as default charset. However, there might be some problems with converting existent websites from non UTF-8 charset to UTF-8.
Before there is a good enough solution for this conversion, following settings are recommended when you upgrade an existent website if you are not an experienced user:
- Select "Do not change" option in "Database character set and collation" step during upgrade process
- Modify /languages/yourlanguage/global.php to use existent _CHARSET value if it has been changed to UTF-8 in your new global.php file as


define('_CHARSET', 'UTF-8');

Upgrading XoopsEditor package:
In the XOOPS 2.3.1 package, there are five editors included: dhtmltextarea and textarea for plain text, fckeditor, tinymce and koivi for WYSIWYG HTML.
Since there are some directory structure changes in both fckeditor and tinymce editors, you are recommended to remove existent editors before uploading the new additors.
And if you are using fckeditor for modules, please modify module specific configs following the files in /fckeditor/modules/, especially if you use "article" module.

Debug information display level
-----------------------------------

Since XOOPS 2.3.1 debug information display level is enabled as a temporary solution for 2.3* to show debug information to different level of users: to all users, to members or to admins only.
The configuration can be set in /xoops_data/configs/xoopsconfig.php
A new debug information renderer is redesigned in XOOPS 3.0

Files integrity check
-----------------------------------

The full XOOPS package is released with a script able to check if all the system files have been correctly uploaded to the server. To use it, follow these instructions:

1. Upload the checksum.php and checksum.md5 files located in the XOOPS package root to your XOOPS server folder (putting them next to mainfile.php).
2. Execute checksum.php with your browser
3. If necessary, re-upload the missing or corrupted system files
4. Remove checksum.php and checksum.md5 from your server

Modules
-----------------------------------

This release contains only the "system-related modules". You are invited to browse the XOOPS modules repository to if you need additional functionality. Note: as a new repository is being built, the current repository is not up-to-date, PLEASE VISIT INDIVIDUAL DEVELOPERS' WEBSITES TO MAKE SURE YOU ARE USING LATEST VERSION OF MODULES.

How to contribute
-----------------------------------
Bug report: http://sourceforge.net/tracker/?group_id=41586&atid=430840
Patch and enhancement: http://sourceforge.net/tracker/?group_id=41586&atid=430842
Feature design: http://sourceforge.net/tracker/?group_id=41586&atid=430843
Release announcement: https://lists.sourceforge.net/lists/listinfo/xoops-announcement

XOOPS Development Team
October 10th, 2008

Next article » « Previous article

Bookmark this article at these sites

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

Thank you!

Cheers ;o)

Posted: 2008/10/11 9:53 • Updated: 2008/10/11 9:53

DarinAllan

great job. thank you for your hard working! XOOPS is back!

Posted: 2008/10/11 10:22 • Updated: 2008/10/11 10:22

dslchart

Outstanding - thank you one and all

Posted: 2008/10/11 10:42 • Updated: 2008/10/11 10:42

JAVesey

Upgrade appears to have gone fine on two sites so far!

Thanks again ;o)

Posted: 2008/10/11 10:47 • Updated: 2008/10/11 10:47

DarinAllan

yep, we hope we reached the maturity point with this release. Let's see if you find new bugs, i hope not so many !
we'll from now focus on utf8 conversion concerns, and 3.0.
have fun

Here is the changelog :
Quote:

============================
2008/10/11: Version 2.3.1
============================
- Fixed bug #2147303 for xoops.js as well as missing revision #1281 (phppp/cpks)
- Fixed bug #2147607: admin tab menus are not rendered (phppp/marco)
- Fixed bug #2148598: removed extra spaces and lines after PHP close tag (phppp/igomen)
- Fixed bug #2148589: corrected prompting messages in module install/uninstall (phppp/igomen)
- Fixed bug #2148257 by extending range of js calendar (phppp/marco)
- Fixed wrong regdate in adding user (bug #2154326) (phppp/trabis/Alian/marco)
- Fixed bug #2154335: page is not redirected correctly after deleting a visibility item (phppp/Reintjan/marco)
- Fixed bug #2155512: paths were wrongly configured for koivi editor (phppp/dnprossi/marco)
- Fixed bug #2151858: Added missing index files to prevent directory traversal (phppp/phmo/marco)
- Fixed bug #2154367: title attribute is not properly rendered in case there are bbcode tags inside url tag (phppp/blueteen/marco)
- Fixed bug #2101426: required select field is not adequately validated in profile module (phppp/marco/RC78)
- Improved xoops.css mainly for positioning img elements (phppp/Ianez)
- Improved CAPTCHA verification to return true value when CAPTCHA is disabled (phppp/dongzhi)
- Improved tinyMCE editor (luciorota/phppp)
- Improved debug information visibility suggested in tracker #2106895. Log renderer is redesigned in XOOPS 3.0 but we also added a temporary solution for XOOPS 2.3 (phppp/trabis/marco)

Posted: 2008/10/11 11:17 • Updated: 2008/10/11 13:24

Marco

thanks all developers !
Persian translation of this news
http://www.irxoops.org/modules/news/article.php?storyid=277

and persian language for XOOPS 2.3.1
http://www.irxoops.org/modules/wfdown ... lefile.php?cid=14&lid=244

Posted: 2008/10/11 12:59 • Updated: 2008/10/11 12:59

voltan

Thank You

Doc Api is here :

- http://dev.xoofoo.org/dev_xoops_231/ (by doxygen)
- http://dev.xoofoo.org/xoopsphpxref/231/ (by PhpXref)

and e-book (chm format) is found --> http://tutos.xoofoo.org/modules/mydow ... /visit.php?cid=11&lid=146

also hack for morphogenesis 2.x theme --> http://tutos.xoofoo.org/modules/mydow ... /visit.php?cid=20&lid=147

Kris

Posted: 2008/10/11 14:56 • Updated: 2008/10/11 15:30

kris_fr

Upgrade is fine, only modules bloks what have not DIV does not show width 100% and I have to a manually myself write into block templates style width 100%
Thanks
Saba

Posted: 2008/10/11 18:15 • Updated: 2008/10/11 18:15

sabaM

I found the problem with the blocks' width, to be due to the new following entry in xoops.css


#centercolumn .blockContent, .xo-blockcontent 

{     display: inline; }  

/* for IE/Mac */

I commented out the lines, and all is correct again. It may not be the correct solution however!!!

Posted: 2008/10/12 4:00 • Updated: 2008/10/12 4:00

pgroell

As a 2.2 user I am glad to see that the merge of 2.0 and 2.2 branches can be done successfully in 2.3 version.
Themable admin, clonable blocks, extended profile module, private messages module, well done and thank you for keeping all this good feature in 2.3 version.
One more thing though. What about themable redirect page? Can be the redirect page encapsulated into the theme design like in 2.2 branch? Is this difficult to achieve ? Would be great, don't you think?

I have installed on my localhost without any problem. Have to test an upgrade process of a 2.2 installation.

Posted: 2008/10/12 10:06 • Updated: 2008/10/12 10:06

blindman

and the polish translation goes here
Polskie t?umaczenie znajdziecie tutaj

Posted: 2008/10/12 15:38 • Updated: 2008/10/12 15:38

red_Slider

@sabaM
which is exactly the problem you encountered?
and which browser/operating system?

@pgroell
the line in xoop.css should be..

display: inline-block;

Ian

Posted: 2008/10/13 3:41 • Updated: 2008/10/13 9:18

ianez

Turkish translation is here: http://www.xoops-tr.com/modules/mydow ... inglefile.php?cid=1&lid=6

Posted: 2008/10/13 10:10 • Updated: 2008/10/13 10:11

canbula

First, thanks to all of you for translating XOOPS!!!

Please post links to all "language files" for 2.3.1 in the Translation news

Posted: 2008/10/13 12:00 • Updated: 2008/10/13 12:00

Mamba

xoops 2.3.1 uses a different code for inserting images in content, using now the float property to align them in the text (which is more w3c compliant)
this change needed a workaround for keeping floated object in the right position, which has been added in the end of xoops.css.

Actually there's an addition to do to preserve total comapatibility with theme based on morphogenesis structure (as zetagenesis also), and avoid some block messing..

So the actual code in the end of xoops.css:


#centercolumn .blockContent:after, .xo-blockcontent:after {

    content:    ".";

    display:    block;

    height:     0px;

    clear:      both;

    visibility: hidden;

}



#centercolumn .blockContent, .xo-blockcontent {

    display:    inline-block;

}  /* for IE/Mac */



#centercolumn .blockContent, .xo-blockcontent {

    clear:      both; /* for Gecko */

    height:     1%; /* for IE */

}

should be changed in:


#centercolumn .blockContent:after, #xo-page .xo-blockcontent:after {

    content:    ".";

    display:    block;

    height:     0px;

    clear:      both;

    visibility: hidden;

}



#centercolumn .blockContent, #xo-page .xo-blockcontent {

    display:    inline-block; /* for IE/Mac */

}  



#centercolumn .blockContent, #xo-page .xo-blockcontent {

    clear:      both; /* for Gecko */

    height:     1%; /* for IE */

}

this should work for most of the situations,
use the forum to report any issue related

Ian

Posted: 2008/10/17 4:21 • Updated: 2008/10/17 4:23

ianez

Correct me if I'm wrong, but the link to "Download the latest XOOPS version" on the top page leads to v2.3.0 ...
I think the link needs changing so that it leads to v2.3.1 doesn't it?

Posted: 2008/10/18 22:29 • Updated: 2008/10/18 22:29

sailjapan

Quote:

Correct me if I'm wrong, but the link to "Download the latest XOOPS version" on the top page leads to v2.3.0 ...
I think the link needs changing so that it leads to v2.3.1 doesn't it?

Thanks for the catch! It has been updated...

Posted: 2008/10/19 3:30 • Updated: 2008/10/19 3:30

Mamba

Upgrade from XOOPS 2.2.5 to XOOPS 2.3.1 are semi-success, the custom blocks are gone. News blocks are gone. The sub menu does not show on the block section to select.

Any advice?

Posted: 2008/10/30 22:21 • Updated: 2008/10/30 22:21

canuser

I upgraded system site from 2.2.6 to 2.3.1 and site working well but admin page profile module do not open and give me this error message:

This page cannot be displayed due to an internal error.

You can provide the following information to the administrators of this site to help them solve the problem:

Error: The package only works for XOOPS 2.3+
Backtrace:
/Frameworks/art/functions.ini.php (15)
/Frameworks/art/functions.admin.php (17)
/modules/profile/admin/header.php (28)
/modules/profile/admin/field.php (20)

Posted: 2008/11/7 12:29 • Updated: 2008/11/7 12:29

amin_ts

XOOPS vs. Herko Coomans

Local Support

Make a donation

Search

Twitter News

Cumulus Tag Cloud

New Users

Archives

News Archives

Advertisement

XOOPS 2.3.1 Final Is Released

About Us

Learn

Use

Develop

Contribute

Connect

Do you want your username revealed with your donation?
	Yes - List me as a Generous Donor
	No - List my donation as from an Anonymous Donor