Get XOOPS XOOPS FAQ Forums News Themes Modules
News World of XOOPS Developers Hacks Modules Themes YAXS Archive Submit News

XOOPS vs. Herko Coomans

Local Support

Make a donation

Please select an amount to donate


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


Search

Twitter News

Cumulus Tag Cloud

admin Arabic banner block Christmas comments cumulus DayDawn dhsoft e-Commerce E-Learning Google GUI hacks instant-zero jQuery module news Nordic Olédrion oxygen PageRank security SEO simple-XOOPS sport tag Theme wiki xoops

New Users

Registering user

# 117261

rheamad34

Welcome to XOOPS!

Archives

Advertisement

XOOPS Code hosted on SourceForge

XOOPS 2.3.3 Final Is Released

Posted by phppp on 2009/3/15 5:10:00 (29741 reads) | Posted on XOOPS
Open in new window
After over 25,000 downloads of XOOPS 2.3.2b in just three short months (see here), the XOOPS Development Team is pleased to announce the release of XOOPS 2.3.3 Final.

This release includes many bugfixes and user experience improvements, done by XOOPS Core Development Team and XOOPS community.

Some of the areas:
- profile and pm modules improved by dhcst
- installer improved by dugris and marco, etc.
- theme improved by mamba, aph3x, kris and burning
- tinymce editor improved by dugris and luciorota
- snoopy class upgraded by julionc
- smarty upgraded by dhcst
- bug tracker managed by marco

Please remember: If you're installing it over previous test installation, make a BACKUP first!
Please also note that some hacks done for previous XOOPS versions might not work with this release: testing before installing is always a good choice


Download it from Sourceforge repository.

Please post and discuss all issues related to this release in this forum

We also need help with Translations

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

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


Installing XOOPS
-----------------------------------

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 xoops_data/ writable; Create (if not already present) and make the directories 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

Installing Protector in XOOPS
-----------------------------------
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, delete the mainfile.dist.php available at the xoops root, copy /extras/mainfile.dist.php.protector to /htdocs/mainfile.dist.php and rename it to mainfile.dist.php BEFORE installing XOOPS.
To install protector module with upgrading from a previous version to XOOPS 2.3.1, delete the mainfile.dist.php available at the xoops root, copy /extras/mainfile.dist.php.protector to /upgrade/upd-2.0.18-to-2.3.0/mainfile.dist.php and rename it to mainfile.dist.php BEFORE upgrading XOOPS.


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

Upgrading from XOOPS 2.3.1 or 2.3.2 (easy way)
1. Get the right 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 to
define('_CHARSET''UTF-8');
change it back to what it was before, e.g.:
define('_CHARSET''ISO-8859-1');


Upgrading XoopsEditor package:
In the XOOPS 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/tracker2/?group_id=41586&atid=430840
Patch and enhancement: http://sourceforge.net/tracker2/?group_id=41586&atid=430842
Feature design: http://sourceforge.net/tracker2/?group_id=41586&atid=430843
Release announcement: https://lists.sourceforge.net/lists/listinfo/xoops-announcement


XOOPS Development Team
March 15, 2009

==========================================
XOOPS Changelog

============================
2009/03/15: Version 2.3.3
============================
Updates from Sourceforge trackers:
- Fixed bug #2414112: Hardcoded Style (mowaffak/dugris)
- Fixed bug #2419532: maxlength (25) for adminname and display strong password generator (bandit/dugris)
- Fixed bug #2501237: merger complete configuration files (default and custom) (zoullou/dugris)
- Fixed bug #2426129: XoopsFormEditor class uses the selected XoopsEditor customized renderValidationJS method when exists (luciorota)
- Fixed bug #2164522: Last login date display fixed for user had never logged (julionc/marco/colossus)
- Fixed bug #2164510: "Url" field in Profile module isn't a link (julionc/marco/colossus)
- Fixed bug #2217070: CSS Language files were not adequately loaded in Cpanel GUI and wrong css file (julionc/tititou)
- Fixed bug #2331727: rank image was not required in edit form but checked upon submission (phppp/burning/marco)
- Fixed bug #2163373: removed extra ':' from smilie form (phppp/tititou)
- Fixed bug #2341118: blank page only guests (dhcst)
- Fixed bug #1193857: UTF-8 for non-english Websites(dhcst)
- Fixed bug #2340000: display *=required for the required fields (dhcst)
- Fixed bug #2172528: Fatal error: Call to a member function isAdmin() (dhcst)
- Fixed bug #2378095: module pm - wrong start values (mcleines)
- Fixed bug #2332106: exm css warning (dhcst)
- Fixed bug #2158984: Remember me checkbox set to on by default (dhcst)
- Fixed bug #2344245: module pm - prune function
- Fixed bug #2494356: Upgrade Smarty 2.6.22 (dhcst)
- Fixed bug #2340215: [img] and [url] (dhcst)
- Fixed bug #2192934: PM - Can't delete
- Fixed bug #2414383: Blocks were not sorted correctly once data are not reconciled (phppp/mcleines/dejadingo)
- Fixed bug #2571592: Element id is not recognized in XoopsFormCheckBox (phppp/madreus)
- Fixed bug #2579969: typo in config "filterxss_on_display" (phppp/marco/grandoc)
- Fixed bug #2549140: CAPTCHA image is not displayed with some IE browsers (phppp/saba/dhcst)
- Fixed bug #2489130: element id is not used correctly (phppp/trabis)
- Fixed bug #2573097: request parameters are not stored in block admin (phppp/sabahan)
- Fixed bug #2380971: display informative message for notification options (phppp/bandit-x)
- Fixed bug #2483646: caption for username is missing (phppp/sabahan/mcleines)
- Fixed bug #2340302: username is truncated when editing a user by admin (phppp/GPboarder)
- Fixed bug #2602337: variable "XOOPS_VAR_PATH" is wrongly typed in upgrader 2.0.18 to 2.3.0 (phppp/mcleines)
- Fixed bug #2340700: improvement on readme (phppp/ghia/Phmo)
- Fixed bug #2637832: content is missing in function xoopsCodeTarea (phppp/mamba/ToloXoop/Ghia)

+ Implemented feature #2154340 or meta tags for register, user and userinfo files for SEO Optimization (julionc/kerkyra)
+ Implemented feature #2193964 or localization in Installer system (julionc/voltan)

Updates upon community:
- Fixed pagenav - extra parameter contains an anchor (dugris)
- Fixed sort categories - module profile (dhcst/trabis)
- Fixed permission for Usergroups - module profile (dhcst)
- Fixed bug in user.php: page is not accessible due to infinitive redirect loop if profile module is installed but permission is not set properly (phppp/AAAAAgg)
- Refactoring XoopsLogger in /class/logger/xoopslogger.php (julionc/phppp/tititou)
- Changed language folder from 'dutch' to 'nederlands' in upgrade (phppp)
- Improved installer (dugris/phppp/ezsky/marco)
- Improved system_siteclosed.html in default and Zetagenesis Theme (mamba/aph3x/kris/dugris)
- Improved system_redirect.html in defautl and Zetagenesis theme (kris)
- Improved template cache handler to allow module-wide cache update (phppp)
+ Added search field groups - module profile (only for webmasters)
+ Added checks for XOOPS_TRUST_PATH outside DocumentRoot, Xoops_Cache is writable (dhcst)
+ Implemented template to homepage (phppp)
+ Implemented localization support for content rendering (phppp/julionc/rowdie/irmtfan/mamba/voltan)
+ Implemented localization support for RSS feeds (phppp/dugris)
+ Added module names to not installed module list (phppp)
+ Added module preference entrance to system preference list (phppp/herve)
+ Added double_encode support to MyTextSanitizer::htmlSpecialChars (phppp/dugris/dhcst)
+ Added Stylesheet for pagenav (burning/kris)

Third-party updates:
- Upgraded Snoopy Class to 1.2.4 (julionc)
- Upgraded Smarty to 2.6.22 (dhcst)

Modified language files:
/language/english/global.php added: "_REQUIRED" (dhcst)
/language/english/admin.php added: "_AD_WARNINGINSTALL", "_AD_WARNINGWRITEABLE", "_AD_WARNINGNOTWRITEABLE" and "_AD_WARNINGXOOPSLIBINSIDE" (phppp/dhcst)
/language/english/user.php (julionc)
/modules/system/language/english/admin/preferences.php added: "_MD_AM_MODULEPREF" (phppp)
/modules/profile/language/english/modinfo.php added: "_PROFILE_MI_NEVER_LOGED_IN" (julionc)
/modules/profile/language/english/main.php added: "_PROFILE_MA_ACTUS" and "_PROFILE_MA_FOUNDUSER" (dhcst)
/install/language/english/install.php (phppp)
/install/language/english/welcome.php (phppp)
/install/language/english/finish.php (phppp)

Added language files:
/language/english/backend.php (phppp)
/language/english/style.css (phppp)
/themes/zetagenesis/language/english/ (phppp)
/themes/zetagenesis/language/english/main.php (phppp)
/themes/zetagenesis/language/english/script.js (phppp)
/themes/zetagenesis/language/english/style.css (phppp)
/upgrade/language/english/style.css (phppp)
/install/language/english/support.php (dugris)
/install/language/english/support.png (dugris)



Printer Friendly Page Send this Story to a Friend Create a PDF from the article


Bookmark this article at these sites

                   

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

Thank's for this job

Doc Api for this release is on Dev.XooFoo (Doxygen and PhpXref)

Kris
Posted: 2009/3/15 8:46 • Updated: 2009/3/15 8:46
Kris, that's fantastic!!! Thank you for doing it so quickly!
Posted: 2009/3/15 8:52 • Updated: 2009/3/15 8:52
Upgraded two sites, so far so good

Thanks!
Posted: 2009/3/15 10:47 • Updated: 2009/3/15 10:47
We've just updated XOOPS Website to 2.3.3 - it took us 5 minutes to upload files, update, and so far so good

If you see anything weird, please let us know.

And thanks to all the developers and users who have contributed to this release!

This is the best release of XOOPS ever, and we very much appreciate all your help!!!
Posted: 2009/3/16 0:00 • Updated: 2009/3/16 0:32
can i download this anywhere else?
the sourceforge page doesn't seem to be loading pretty well on my side
Posted: 2009/3/16 0:34 • Updated: 2009/3/16 0:34
Quote:
can i download this anywhere else?

Try another SourceForge Mirror
Posted: 2009/3/16 0:42 • Updated: 2009/3/16 0:42
I am still wondering when the multixoops in the SVN Tasks is going to be merged with the Trunk.. Anyway you can download the tarball from the SVN if you want to give it a go..

Download XOOP 2.3.3 as a Torrent if you want!
Posted: 2009/3/16 2:06 • Updated: 2009/3/16 2:06
Let's do more testing of it, and then let's shoot probably for 2.4, together with Simple-XOOPS merger.

We need to make sure that we get a positive feedback from people about its usability and performance.

If people install it and it blows an existing installation, they would kill us

So please help Wishcraft with testing of the Multisite capabilities. This is a very important feature for future XOOPS releases!!!
Posted: 2009/3/16 2:10 • Updated: 2009/3/16 2:10
I find this explaination confusing and incomplete.
Quote:
Upgrading a non UTF-8 site:
... snip ...
- 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');


What is the existant value? Previous old or current changed new value? Which one exists?
And the example shown should suggest what to do and not only what is wrong.
Therefore:Quote:

Upgrading a non UTF-8 site:
... snip ...
- Modify /languages/yourlanguage/global.php to use your previous _CHARSET value.
If it has been changed to UTF-8 in your new global.php file to
define('_CHARSET''UTF-8');
change it back to eg
define('_CHARSET''ISO-8859-1');


Quote:
If you see anything weird, please let us know.

A style change.

Quote:
- snoopy class upgraded by julionc
This Snoopy class does still not process the HTTP error status codes.
Posted: 2009/3/16 5:24 • Updated: 2009/10/24 12:58
great news! i will rebuild my site with XOOPS 2.3.3 very soon!
Posted: 2009/3/16 9:08 • Updated: 2009/3/16 9:08
upgrade xoops2.3.2b on xoops2.3.3 has passed without any problems, but I noticed that in the yogurt module smilies do not work more

Regards
saba
Posted: 2009/3/16 11:07 • Updated: 2009/3/16 11:07
Is final Framework for XOOPS 2.3.3?
Posted: 2009/3/16 13:24 • Updated: 2009/3/16 13:26
Good news... :)

But the surcharge for themes doesn't work... :( (You need to use the default templates...)
And the Preview don't show the accent ; for exemple à ==> ?
Posted: 2009/3/16 15:18 • Updated: 2009/3/16 15:19
just to add my appreciatiation for the effort everyone went to in ensuring that the upgrade path was smooth. I was so relieved that the upgrade appears to have worked well and painlessly. :) (upgraded from 2.0.18 - 2.3.3)

Andrew
Posted: 2009/3/24 20:24 • Updated: 2009/3/24 20:24
Upgrade went well... Small problem. Maybe someone could tell me how to fix.

The zetagenesis theme doesn't find ajax_indicator_01.gif in its img folder, but looks for it in the root directory under a non-exeistent folder called img.

In the zetagenesis theme, where do I fix this?

Regards,

JammerPro
Posted: 2009/3/25 9:36 • Updated: 2009/3/25 9:36
Good news... :)
Posted: 2009/3/31 17:29 • Updated: 2009/3/31 17:29
Upgraders using the full package: Beware of your adapted configurations!
Posted: 2009/4/10 14:37 • Updated: 2009/4/10 14:37
There is some error. Same link for this news and Government of Parana releases its new Website powered by XOOPS. If yomeone can check this and repair
Posted: 2009/4/17 17:21 • Updated: 2009/4/17 17:21
Quote:
There is some error. Same link for this news and Government of Parana releases its new Website powered by XOOPS

Fixed. Thank you for making us aware of it!
Posted: 2009/4/17 19:17 • Updated: 2009/4/19 12:19
Step 6 is causing trouble on some servers. For the time being, I think it is best that the install is completed as it is, with the directories of xoops_lib and xoops_data in the root. When the install is verified to work, then make the move and adapt mainfile.php as some post install actions.
(Until the install script can check and move these folders itself and provide renaming for the case of in root.)

Maybe the insecure warning in admin should vanish or moderated, when the folders are in root, but are renamed and have an .htaccess file.

The file check should be adapted to read the position of the moved folders so all files can be verified.
Posted: 2009/4/19 6:30 • Updated: 2009/4/19 6:30
Change 'Administration' to lang string by adding:

define("XOOPS_ADMINISTRATION", "Administration");

to global.php lang file, then replace:

<title>'.htmlspecialchars($xoopsConfig['sitename']).'
Administration</title>

with:

<title>'.htmlspecialchars($xoopsConfig['sitename']).'
'.XOOPS_ADMINISTRATION.'</title>

in the following files:

modules/system/admin/tplsets/main.php
modules/system/class/gui/default/cp_functions.php
modules/system/class/gui/default/default.php
modules/system/class/gui/legacy/cp_functions.php
Posted: 2009/5/3 10:59 • Updated: 2009/5/3 10:59
Hi,
After upgrade i'm get a blank screen in admin area.

Help.
Posted: 2009/5/7 18:56 • Updated: 2009/5/7 18:56
I, too am experiencing blank admin.php, modules/module_name/admin.php, all backend seems to be blank. No errors with debug on. Mystified...
Posted: 2009/5/29 14:26 • Updated: 2009/5/29 14:26
The same thing on my site.a new installed site have no this problem.
Posted: 2009/5/29 15:02 • Updated: 2009/5/29 15:02
How bout XOOPS version 2.0.16.
Which one instruction should i follow?
Posted: 2009/6/24 4:22 • Updated: 2009/6/24 4:22
Alhafizh, there are instructions for 2.0.16:

Quote:
Upgrading from XOOPS 2.0.* above 2.0.14 and 2.2.* (using the full package)

Posted: 2009/6/24 7:13 • Updated: 2009/6/24 7:13
why is the repository empty?
Posted: 2009/7/2 12:49 • Updated: 2009/7/2 12:49
See this.
Posted: 2009/7/2 13:05 • Updated: 2009/7/2 13:05
I'm newbie to this and found this error during installation. Anyone can please help me?

Fatal error: Class 'XoopsLogger' not found in /home/bdpharma/public_html/sms/install/class/dbmanager.php on line 49


My site address id: http://sms.mig33forum.com
Posted: 2009/7/7 22:44 • Updated: 2009/7/7 22:44
Please run checksum to make sure that you have all files.
Posted: 2009/7/7 23:21 • Updated: 2009/7/7 23:21
How to run checksum? I'm a newbie. Kindly tell me the process. It will be great help.
Posted: 2009/7/8 12:11 • Updated: 2009/7/8 12:11
The instructions are here on top, in the section: "Files integrity check"
Posted: 2009/7/8 13:00 • Updated: 2009/7/8 13:00
Thanks for your prompt respond..

I need more little advice about this error

"Fatal error: Cannot redeclare class upgrade_2014 in \xxx\xxx\public_html\upgrade\upd-2.0.13-to-2.0.14\index.php on line 168"
Posted: 2009/7/15 0:23 • Updated: 2009/7/15 0:23
the download link to the 2.3.3 is broken
Posted: 2009/8/23 10:51 • Updated: 2009/8/23 10:51
Probably, because the update of it with the security patch.
Use this link:
http://sourceforge.net/projects/xoops ... eleases%29/XOOPS%202.3.3/
Posted: 2009/8/23 11:27 • Updated: 2009/8/23 11:27
Due to changes on SourceForge, some of the links might be broken. This one is now fixed.

If you find one, please let us know, and we'll fix them.

BTW - the current download of 2.3.3 has been patched with this Security Patch
Posted: 2009/8/23 13:36 • Updated: 2009/8/23 16:41
Here is a good question
im using XOOPS v2.0.18.1

yea i know im behind on things

but i wanted to upgrade to the latest
Would it be easy to ROLL BACK
and if so
whats the most proper way of doing it incase it doesnt work on my setup?
Posted: 2009/10/24 12:49 • Updated: 2009/10/24 12:49