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

XOOPS vs. Herko Coomans

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

Local Support Sites

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

# 96568

dvsshoescom

Welcome to XOOPS!

Archives

XOOPS Code hosted on SourceForge

XOOPS 2.4.2 FINAL Is Released

Posted by Mamba on 2009/11/30 1:20:00 (4541 reads) | Posted on XOOPS
Open in new window
The XOOPS Development Team is pleased to announce that a new release of the #1 CMS System hosted on SourceForge - XOOPS 2.4.2 Final is available for download.

Open in new window

This release is a bugfix-release of XOOPS 2.4.1, done by XOOPS Core Development Team and XOOPS community:

Updates upon community:
- Fixed : "embed" is deprecated in banners (kris_fr)
- Fixed : bug flash banner (display and count) (kris_fr)
- Fixed : Duplicate notifications (trabis)
- Fixed : Cannot delete multiple pms in PM module (trabis)
- Fixed : removed dependency on Framework Captcha (mamba, ghia)
- Fixed : Language problem in xoops mailer (dhcst)
- Fixed : XoopsPersistableObjectHandler::get() not allowing getting objects with id=0 (trabis)
- Fixed : Cannot redeclare class xoopscaptchaimage (trabis)
- Fixed : problem with module menus(article, tags) in oxygen admin gui (trabis)
- Added : missing index.html files (mamba, Culex)
- Added : Frameworks/compat (trabis)
- Added : define language for banner client ID (kris_fr)
- Added : users real name can now be used in themes <{$xoops_name}> (kris_fr)
- Added : comment for download module and theme in last page "xoops installer" (kris_fr)
- Improved : rtl style in oxygen GUI (voltan)
- Improved: added Admin toolbar in Zetagenesis theme (kris_fr)

Updates from Sourceforge trackers:
- Fixed bug #2904049: xoopsform/formfile.php (mamba, Frankblack)

Added Language defines:
- modules/system/language/english/admin/banners.php _AM_CLIENTID

Modified Language file:
- install/language/english/finish.php

Some of the highlights of the XOOPS 2.4.x series:

* a new Admin GUI: Oxygen (Voltan): see picture above
* new mechanism to modularize and extend Core via Preloads (trabis)
* central support for jQuery (trabis)
* improved Installer (DuGris)
* WCAG 2.0 - Sight Impaired Assisted Forms (wishcraft)
* Themeable Admininstration area (trabis)
* support for new WYSIWYG Editors: CKEditor, wymeditor, Xinha, and Spaw2 (wishcraft and Luciorota)
* new System Key (wishcraft)
* Support to PHP 5.3 (trabis)
* profile and pm modules improved by Trabis
* code refactoring and improvements (trabis, catzwolf)
* Security fixes (trabis, wishcraft)

and many more.

Please remember: If you're installing it over previous 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)

Please note: XOOPS 2.4.x series is the LAST version of XOOPS tested on and supporting PHP4. Our next releases will be tested and certified exclusively on PHP5: Read more here

Open in new window

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

Please note: XOOPS 2.4.x series is the LAST version of XOOPS tested on and supporting MySQL version lower than 5.0. Our next releases will be tested and certified exclusively on MySQL 5.0+:

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


Downloading XOOPS
-----------------------------------

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

xoops-2.4.2.zip:
Md5: eb2335af9541e4be9ca3e4449e5e8d15
Sha1: 152c178f0b9c2370ade2c07b140b091ec3d3f969

xoops-2.4.2.tar.gz:
Md5: 3d0ffb8bd30dbd1bb5f30dd937774f7d
Sha1: b01c2dfaefad9c643a7211637887ed0950071321

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 STRONGLY encouraged to move directories "/xoops_lib" (for XOOPS libraries) and "/xoops_data" (for XOOPS data) out of Document Root, and 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 (permission 0777 on Linux).
5. Access the folder where you've installed the htdocs/ files using your web browser to launch the installation wizard
6. Follow the instructions

You can also check out the detailed Installation Guide

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

Upgrading from XOOPS 2.3.3b and 2.4.0 (easy way)

1. Get the right update package from the sourceforge file repository
2. Overwrite files in XOOPS directory on your server with the content of /htdocs
* make sure that you copy the content of /xoops_lib to whatever directory you keep it on the server now (it should be your current XOOPS_TRUST_PATH directory), then delete the /xoops_lib directory. There can NOT be two directories with the content of /xoops_lib
3. If you have Protector previously installed, open the "mainfile.php" file , and remove the Pre-check and Post-check lines (if they exist):

include XOOPS_TRUST_PATH.'/modules/protector/include/precheck.inc.php' ;
include XOOPS_TRUST_PATH.'/modules/protector/include/postcheck.inc.php' ;

4. If you're upgrading from XOOPS 2.4.x, make the file /include/license.php writeable (permission 0777 on Linux)
5. Access /upgrade/ with a browser, and follow the instructions
6. Follow the instructions to update your database
7. Delete the "upgrade" folder from your server
8. Update the "system" module from the modules administration interface. Other modules, especially "Profile" and "Protector" are recommended to update as well

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

0. Unpack the archive to your LOCAL computer (e.g. PC) in a temporary directory.
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 computer
2. Delete htdocs/mainfile.php, htdocs/install/, htdocs/cache/, htdocs/template_c/, htdocs/themes/ and htdocs/uploads/ from the "htdocs" folder on your LOCAL computer
* if you have created XOOPS_TRUST_PATH folder on your server, copy the content of /xoops_lib to that directory, and delete /xoops_lib from the "htdocs" folder on your LOCAL computer
3. Upload the content of the /htdocs folder on your LOCAL computer 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, and 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 (permission 0777 on Linux).
6. Ensure the server can write to mainfile.php (permission 0777 on Linux)
7. If you have Protector previously installed, open the "mainfile.php" file , and remove the Pre-check and Post-check lines (if they exist):

include XOOPS_TRUST_PATH.'/modules/protector/include/precheck.inc.php' ;
include XOOPS_TRUST_PATH.'/modules/protector/include/postcheck.inc.php' ;

8. Access /upgrade/ with a browser, and follow the instructions
9. Follow the instructions to update your database
10. Write-protect mainfile.php again (permission 0444 on Linux)
11. Delete the "upgrade" folder from your server
12. 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):

0. Unpack the archive to your LOCAL computer (e.g. PC) in a temporary directory.
1. Move the "upgrade" folder inside the "htdocs" folder on your LOCAL computer (it's been kept separate as it's not needed for full installs)
2. Delete htdocs/mainfile.php, htdocs/install/, htdocs/cache/, htdocs/template_c/, htdocs/themes/ and htdocs/uploads/ from the "htdocs" folder on your LOCAL computer
* if you have created XOOPS_TRUST_PATH folder on your server, copy the content of /xoops_lib to that directory, and delete /xoops_lib from the "htdocs" folder on your LOCAL computer
3. Upload the content of the htdocs folder on your LOCAL computer 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 (permission 0777 on Linux)
6. If you have Protector previously installed, open the "mainfile.php" file , and remove the Pre-check and Post-check lines (if they exist):

include XOOPS_TRUST_PATH.'/modules/protector/include/precheck.inc.php' ;
include XOOPS_TRUST_PATH.'/modules/protector/include/postcheck.inc.php' ;

7. 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.
8. 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 (permission 0777 on Linux).
9. Access /upgrade/ with a browser, and follow the instructions
10. Write-protect mainfile.php again (permission 0444 on Linux)
11. Delete the "upgrade" folder from your server
12. 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 existing 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 existing 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 your previous _CHARSET value, if it has been changed to UTF-8 in your new global.php file as
define('_CHARSET''UTF-8');


Upgrading XOOPS Editors:
In the XOOPS package, there are four Editors included: dhtmltextarea and textarea for plain text, CKeditor and TinyMCE for WYSIWYG HTML.
There are six additional WYSIWYG Editors available: FCKeditor, Koivi, NiceEdit, Wymeditor, Xinha, and Spaw2 that you can download from XOOPS SourceForge (https://sourceforge.net/projects/xoops/files/XOOPS%20Editors/)
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 tools will be available for 2.4 using FireBug (see http://tinyurl.com/nmnjdp)



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
November 30th, 2009


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.

Great Work!
Posted: 2009/11/30 2:48 • Updated: 2009/11/30 2:48
great news
Posted: 2009/11/30 2:50 • Updated: 2009/11/30 2:50
Great news!

Also, just to write down. I'm still using exm admin panel rather than new voltan's one. I saw some benefits from new one, but I'm accustomed to exm and hope it will continue to be in xoops for next versions.
Posted: 2009/11/30 10:26 • Updated: 2009/11/30 10:30
thanks for the update packs!
Posted: 2009/11/30 10:29 • Updated: 2009/11/30 10:29
Thanks for the update packs!
Posted: 2009/11/30 11:07 • Updated: 2009/11/30 11:07
Upgrade-Package 2.4.1->2.4.2 htdocs/modules/protector: there is an index.html although there is an index.php. I could be wrong, but if NO index.php is there an index.html have to placed there.

I just saw it, that in class/xoopsform/formradio.php a label was added for rendering. From what I know: there is no universal attribute called name for the html-tag label. I did not check other xoopsform elements. Still we are from being xhtml-compliant (not even transitional!), I have the feeling that we move more and more away (myPOV).

Apart from that: good job!
Posted: 2009/11/30 11:36 • Updated: 2009/11/30 11:36
Well done one and all.

I dunno.... I come back after a break and two upgrades in two days

Looks like some good bug-fixes in there, too. Top stuff
Posted: 2009/11/30 11:51 • Updated: 2009/11/30 11:51
Thanks for this release

Doc API with phpxref --> Dev.XooFoo - PhpXref
Doc API with Doxygen --> Dev.XooFoo - Doxygen
Doc API Chm ebook --> Tutos.XooFoo - Tools / Documentation
Posted: 2009/11/30 14:23 • Updated: 2009/11/30 14:25
Open in new window

Posted: 2009/11/30 14:30 • Updated: 2009/11/30 14:30
Kris, thanks for the documentation

Andrey - good catch! It's been fixed!
Posted: 2009/11/30 16:43 • Updated: 2009/11/30 16:43
Thank you for the update , good Job

I ahve 2 Requests :

1- Notfiy For the New Update from Admin area .. Auto Check

2- Before Start Updating a Message asks Me How i feel To day .
Posted: 2009/11/30 16:57 • Updated: 2009/11/30 16:57
Upgrade-Package 2.4.1->2.4.2: there isn't an 'index.php' in 'upgrade' directory. I can't upgrade my xoops site.
What's wrong?
Posted: 2009/12/1 10:21 • Updated: 2009/12/1 10:21
Quote:
Upgrade-Package 2.4.1->2.4.2: there isn't an 'index.php' in 'upgrade' directory. I can't upgrade my xoops site.
What's wrong?

Let me check, and I'll get back to you

[EDIT] this is an upgrade, so the files included are only file that were different from XOOPS 2.4.1, so if you have the upgrade folder from 2.4.1, and overwrite it with these ones, then everything is fine.

But I just updated the files in SourceForge, so they will now contain the full Upgrade directory.
Posted: 2009/12/1 10:43 • Updated: 2009/12/1 11:06
A couple of questions:

Wouldn't it be useful to include in the readme instructions to copy the folder upgrade into your XOOPS dir?

When I unzip the package the resulting folder contains another copy of the zipped upgrade package. Why is that?

barryc
Posted: 2009/12/1 12:40 • Updated: 2009/12/1 12:40
Barry, which package?
Posted: 2009/12/1 12:44 • Updated: 2009/12/1 12:44
Here is my German Promotion for the new XOOPS 2.4.2
Posted: 2009/12/1 13:29 • Updated: 2009/12/1 13:29
Mamba,

2.3.3b-to-2.4.2

This is what I see in the folder when I unzip it:

checksum.md5
docs
htdocs
release_notes.txt
upgrade
xoops2.3.3b-to-2.4.2.zip

[Edit] Incidentally, my home machine on which I unzip before uploading is a Mac, OS X Snow Leopard.

[Edit #2] I also have a Windows machine here and tested the download on that, with the same result.

barryc
Posted: 2009/12/1 14:20 • Updated: 2009/12/2 0:42
Quote:
I also have a Windows machine here and tested the download on that, with the same result.

Barry, thanks for reporting - it has been fixed now.
Posted: 2009/12/3 1:37 • Updated: 2009/12/3 1:37
Just call it a feeling, but 2.4.2 seems to be slower than 2.0.18 I've just upgraded. Unfortunately I made no speed test before and after. Anyone have the same feeling?
Posted: 2009/12/4 14:44 • Updated: 2009/12/4 14:44
Hi,
Upgrade from 2.4.1 to 2.4.2 steps are not mentioned. I have downloaded the zip file so what should I do just need to pace upgrade folder or should replace with other files in this zip file after take backup.

thanks
Posted: 2009/12/4 21:20 • Updated: 2009/12/4 21:20
If you use smartsection 2.13 or 2.14 you should read this thread (bug fix): http://www.xoops.org/modules/newbb/vi ... pic_id=70210&forum=72

Best wishes
Posted: 2009/12/27 19:49 • Updated: 2009/12/27 19:49