PHP Open Source Content Management Systems

Joomla Upgrade 1.5.17 (formerly known as 1.5.16)

23 April 2010 joomla.org released the new version 1.5.16 - almost 5 months after the release of 1.5.15 - although the .15 version had no major security issues, there are some moderate security concerns:

  • If a user entered a URL with a negative query limit or offset, a PHP notice would display revealing information about the system.
  • The migration script in the Joomla! installer does not check the file type being uploaded. If the installation application is present, an attacker could use it to upload malicious files to a server. (It is NEVER recommended to leave the installer script on a live server)
  • Session id doesn't get modified when user logs in.  A remote site may be able to forward a visitor to the Joomla! site and set a specific cookie.  If the user then logs in, the remote site can use that cookie to authenticate as that user.
  • When a user requests a password reset, the reset tokens were stored in plain text in the database. While this is not a vulnerability in itself, it allows user accounts to be compromised if there is an extension on the site with an SQL injection vulnerability.

There are also some minor fixes in the core components of joomla, mainly:

  • contact
  • newsfeeds
  • media


Unfortunately there were at least three new bugs introduced with this new version, so 4 days later there was a new release 1.5.17 with these fixes:

  • Fixed problem logging in when Session Handler is set to None
  • Fixed error message when running Joomla! in a PHP version prior to version 5.2
  • Reverted change to JFolder::makesafe method that introduced a bug


There are a few issues you have to have to take in account when updating to 1.5.17 :

  • If you used an early version of the upgrade files for 1.5.16 (not the full release) you may have incorrect file permissions of 775 instead of 664 for your files. This was do to an error in the automatic packaging of those files.


How to upgrade Joomla ?

  1. Download the needed patch file (according to the version you want to upgrade)
  2. Backup your site (use Akeeba Backup or Backup from Hosting Cpanel)
  3. Unpack the patch file
  4. Overwrite all files on your FTP
  5. Check that your website is working correctly



Keep in mind not to overwrite the configuration.php file (it is never supplied in the package, the sample configuration is named configuration.php-dist)

Our recommendation: Upgrade sometimes in the near future, but don't rush into it. If your website is stable and you're running 1.5.15 - you should be fine for a while. Test an upgrade first on a less important website you have, see how it plays out.

Joomla Extension - HOT or NOT Deluxe Factory 1.0.2

HOT or NOT Deluxe Factory 1.0.2 provides an easy voting system, requiring only a single click action for a speedy process. The component can be used to rate different images like landscapes, art, etc. or if the genre mode is enabled, more particular for male and female images. The upload is very easy, allowing also multiple upload. For each picture a sharelink and the number of hits will be visible and if admin enabled the description, comments and tags. To allow the administrator content control on the site, each picture and comment can be reported.

HOT or NOT Deluxe Factory 1.0.2 released on February 10, 2010.

  • New feature: added Top Rated in the Categories module.
  • Fixed issues regarding Love Factory integration, BMP files.

HOT or NOT Deluxe Factory 1.0.1 released on December 9, 2009.

  • New feature: possibility to edit the image description from the backend.
  • New feature: added confirmation and error messages after voting.
  • Fixed issues regarding saving image details from the backend (and no tags were entered), php and mysql different timezones issue.

HOT or NOT Deluxe Factory 1.0.0 released on October 15, 2009.

Joomla Blog Extension - Deluxe Blog Factory 1.1.2
Deluxe Blog Factory 1.1.2 Edit PDF Print E-mail

Deluxe Blog Factory is an user friendly, webmaster friendly blogging extension for Joomla 1.5, with a native and fresh MVC codebase. Full of features, it is a well thought alternative to Wordpress blogging, allowing you to use Joomla versatility and well known blogging conventions - like RSS Syndication, Bookmarking Sites (like Digg, Twitter, Facebook, etc). Featuring a Web 2.0 Dashboard with draggable panes and all-in-reach controls, your blogging experience is truly comfortable and in a luxuriant environment.

Deluxe Blog Factory 1.1.2 released on February 19, 2009. 

  • New feature: Search plugin.
  • Fixed several issues regarding PHP4 compatibility issues, strip all javascript when saving post, detect and show error if jQuery UI library is not loaded, modules links Itemids.

Deluxe Blog Factory 1.1.1 released on December 7, 2009.

  • Added menu link for 'Followed Blogs' for users with no blog.
  • Fixed issues regarding new post notification for followers, links from feed, post new comment form, with rss feeds when joomla SEF was active and "Add suffix to URLs" was set to Yes, generating feeds, IE8 blog page display, post view, smarty template not displaying captcha, restore backup (strings in array), sending emails to admin on new comment and no admin selected, display comments, strip javascript when saving post, etc.

Deluxe Blog Factory 1.1.0 released on November 30, 2009.

  • New feature: Backup and Restore.
  • Fixed issue regarding backend save post.

Deluxe Blog Factory 1.0.2 released on November 25, 2009.

  • SH404SEF extension.
  • Fixed issues regarding template and php short open tags.

Deluxe Blog Factory 1.0.1 released on November 20, 2009.

  • Fixed several issues including router.php, routes in Smarty templates.

Deluxe Blog Factory 1.0.0 released on November 9, 2009.

Free Joomla Extension - SEO Keyword Factory v1.0.0

SEO Keyword Factory will allow you to create and maintain a search engine friendly web site by building and saving keyword-rich URLs for a better search engine relevance.

The SEO link is created automatically after the search keywords that brings the visitor on that certain page. Google, Yahoo and Bing are now integrated. In order for the component to function properly, webmasters must enable the System SEO Keyword Factory plugin, which detects the referral from the search engine and will allow to create and maintain a search engine relevant website.

 SEO Keyword Factory

The component comes with a link manager, where all created links are displayed, given the webmaster the possibility to add new links or edit existing ones. When editing, the landing page can be changed, the keywords, number of hits and the publishing state of that certain item. The filter function allows a search after relevant words.

At the component settings, global configuration, the webmaster can set the plugin status and the following parameters:

  • keywords transformation (upper, lower, capital, unchanged),
  • keywords separator,
  • link terminator,
  • number of columns and rows visible per page in the frontend,
  • banned words (if any of this words is found in the search engine keywords, the link will not be generated).

This product is part of our GPL Club. We are offering it now for free download to all site users, according to our terms and conditions. Support for this product is part of the GPL Club and available only to our GPL Club members.

Joomla Dating and Matchmaking Extension Love Factory 1.3.0

This Joomla Extension allows users to interact in the same way they are used on larger dating sites, and allowing you to enjoy the full power of Joomla. This Native Joomla 1.5.x MVC code does not require legacy plugin, and through 100% open source allows you to perform special tweaks for a better integration according to your needs.

Using a templating system (in this case we have a simple and an advanced system) your web site will keep a coherent look and a nice web 2.0 feeling.

released on February 18, 2010.   

  • Re-factored most of the code, for better maintainability and easier extensibility.
  • Improved some SQL queries for better performance.
  • Improved router for better SEF URLs.
  • Implemented three registration modes:

1. Overriding the Joomla's registration system (users only have to register once, a Joomla profile and a Love Factory profile are created at the same time) (uses the Love Factory plugin).

2. Using the Joomla registration system, but require users to fill in their Love Factorry profile before they can use any of the component's functions.

3. Using the Joomla registration system and do not require users to fillin their Love Factory profile (an empty profile will be created the first time they use the component's functions).

  • Implemented a plugin system for Payment Gateways.
  • Added option in the backend (enable/disable) to first sort the results of the search by the membership order and then by the user's selected criteria.
  • Implemented an Infobar (uses the Love Factory plugin) to show information about new messages, interactions or pending friendship requests. This can be enabled/disabled from the backend and on a user level. From the backend the interval at which it refreshes can be set to reduce server load.
  • Implemented Status box (enable/disable from backend): user can set their status about what are they doing right now. Maximum number of characters can be set from the backend.
  • Implemented Wallpage (enable/disable from backend): shows recent activity from the user (status change, photo added, new comments or new ratings).
  • New Module: Last visitors; users can see who who last visited their profile.
  • Added several custom system fields:

A. Online status: shows the online status of the user; labels for the online and offline are editable.

B. Email: field used only when the registration mode is set to override; can be set to check for availability using ajax.

C. Password: field used only when the registration mode is set to override.

D. Password repeat: field used only when the registration mode is set to override.

E. Main photo upload: field used only when registering or when filling in the profile (users can be forced to upload a photo in order to use the site/component).

F. No. of friends: shows the number of friends of the user.

  • The Title of custom fields (user or system fields) can be hidden (enable/disable) from the backend.
  • The Labels of custom fields (user or system fields) can be set depending on the type of page being shown: view, edit or search. (For example: the field Date of birth on the edit page should be labeld as "Date of birth", but on the view page it should be labeld as "Age" and on the search page as "Age between").
  • Custom fields of type Text area can be set to allow HTML tags.
  • Custom fields of types Drop down (multiple select) and Checkboxes can be set their SQL query operand (OR/AND).
  • Last seen custom field can be set to show the date in regular mode or in "x days ago" mode.
  • Main photo custom field can be set to link to user's profile page, user's gallery page or no link at all.
  • Sex custom field can be set to show in 2 modes: Drop down (single select) or Radio buttons.
  • Looking for field can be set to show in 4 modes: Drop down (single select), Radio buttons, Drop down (multiple select) or Checkboxes; using the last 2 options, users can have a multiple selection choice.
  • Username field on the registration page can be set to check the availability using ajax.
  • Improved the pages creation page: zones can be moved around using drag and drop functionality.
  • Added 2 more customizable pages using custom fields: profile fill in page and friends list view page.
  • Users can hide/show the search form.
  • Search results can now be ordered by Number of photos or friends.
  • Redesigned the profile view page, added more ajax functionalities for a better user experience.
  • Added a quick reply mode to received messages.
  • Changed the memberships implementation: all the memberships sold, are now being saved. For example: user A buys membership B for 1 year which allowes him to have a maximum of 10 friends. Six months later the administrator decides that 10 maximum friends are to much for membership B and reduces the number to 5. User A won't be affected by the change, as the membership was saved and it will be applied for the remaining six months. Also, if a user buys a membership for unlimited time, then this membership will be used if no other membership is active.

The new major version is coming with significant improvements and desired features like just seen.

Also the new version, although a new major version, is provided for free upon request to all existing license holders. Visit the contact us page and our customer FAQ.

Upgrading instructions from 1.2.x to 1.3.0.

BEFORE ALL THIS BACK-UP YOUR SITE COMPLETELY!!!
We are not responsible of any loss, etc.


1. First you'll need to backup the data from the 1.2.x version. Go to backend, Backup and Restore, Backup tab, set Include settings to Yes if you want to save the current settings and Include photos' name to Yes if you want to save the photos (please take note that the photo files are not backed up, you will have to manually backup the photos folder to another location, and after the update, move it back).
2. Uninstall Love Factory version 1.2.x.
3. Install Love Factory version 1.3.0.
4. Go to Backup and Restore, Restore tab, select from the Backup file field the backup file saved on step 1, and hit Restore.
5. If you set Yes to Inlcude the photos' name, copy the backed up photos folder to components\com_lovefactory\storage\

Zimplit CMS 3.0 Eases Reseller Implementation Woes

For its 3.0 release, Krabi & Mask — the folks behind Zimplit CMS (site), have refined the fully rebrandable, commercial version of their CMS to target web hosting resellers looking to add a simple web site creation tool.

Zimplit 3.0 install includes demos, documentation and a selection of templates — all rebrandable. Zimplit's site-edit toolbar can be customized as well to suit the color scheme and editing needs of the reseller and their target market.

Targeting the Resellers

The company claims that the install takes just 15 minutes for end users, and that the commercial install is only slightly more complicated. It will work with most hosting panels such as Plesk, cPanel and even home-grown panel solutions.

According to the developers, the 3.0 release simplifies installation for the commercial version and updates the configuration system so that a reseller can easily add/remove languages, change logos and add design templates for the end users.

"Make It Zimple"

On the client end, there is no question that Zimplit trades functionality for simplicity, but for the reseller market the "Make it Zimple" philosophy has its advantages. For what it trades in CMS functionality, Zimplit gains in ease of installation and use.

Clients with minimal web content management needs only need to pick a template and upload a resulting ZIP file. Updating their site is then as easy as logging in and using the intuitive editing toolbar, familiar to the most casual Adobe Photoshop or MS Word user.

Zimplit's own demo site and tutorials are attractively designed, with pleasing colors and a playful tone that fits well with a target audience of kindergartens, smaller businesses and casual end-users in need of some reassurance as they embark into uncharted territory. This is an encouraging sign for the customized, re-branded demos and materials that Zimplit promises. Hopefully, they will be of a similar quality.

Trading Scalability for Simplicity

Of course, as a Micro CMS, Zimplit doesn't scale well with increasing CMS demands. According to recent forum posts, there is no support for multi-language installations, and dynamic template selection is still being implemented. And, as previously mentioned in one of our first looks at the community version of Zimplit CMS, while the exclusion of a database simplifies installation for clients, storing site data exclusively in HTML may be taking the quest for ease of use too far.

As long as the focus remains on the Micro CMS market however, Zimplit has an undeniably attractive product for resellers looking to expand their offerings. And the developers at Krabi & Mask seem committed to improving their product. The forums are active with responses to enquiries, and an update of the UI hot on the heels of the 3.0 release is set for the end of October.

Zikula 1.2.2 Release announcement

We are proud to announce the release of Zikula 1.2.2 which solves a few small issues. For full details see the changelog. If you haven't already upgraded to Zikula 1.2.0 you can also upgrade straight to this version from 1.1.x.

Download links:

Zikula 1.2.2
Zikula-1.2.2.zip (5.51 MB)
MD5: ed7e9bd5634540fc7bebebc7f9b7db25
SHA1: 1480443d43934baffa9c51ff23a65d4168b2b71c

Zikula-1.2.2.tar.gz (4.31 MB)
MD5: 726eda3576d1f495a5e693c9e302fc6a
SHA1: 12605f12ca4ac16c371952f1c69e2be32519a4d2

Patch Files
Zikula-1.2.1_Zikula-1.2.2-patch.zip (645.6 kB)
MD5: aa422f728451299f5a51735830c6aac0
SHA1: fabf1df0ef9ea46912ced9b484139c94bee644a0

Zikula-1.2.1_Zikula-1.2.2-patch.zip (370.43 kB)
MD5: 36efbd96c58957d94924ec895b8ad3fa
SHA1: 616490eb5cfa081b1fdb2aefe418d2f75874b62a

Changelog link:

http://code.zikula.org/core/browser/tags/Zikula-1.2.2/docs/CHANGELOG.txt?format=txt

XOOPS 2.4.4 FINAL Is Released

The XOOPS Development Team is pleased to announce that a new release of the #1 CMS System hosted on SourceForge - XOOPS 2.4.4 Final is available for download.

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

Updates upon community:

- Added: Frameworks/textsanitizer (culex)
- Added: New logger for deprecated API (trabis)
- Fixed: Functions for getting and setting system and module configs, no cleaning should be made (trabis)
- Fixed: Changing © into @ in some config values (trabis)
- Fixed: Notifications box not including comments language (trabis)
- Fixed: Profile module Field weight: > 9 incorrect display (trabis)
- Improved: Cache file 'system_modules_active' is automatically created without need to update system module (trabis)

Updates from Sourceforge trackers:

- Fixed bug #2928289 : XOOPS object behaviour modified (trabis/ghia)

Added Language defines:

- language/english/logger.php _LOGGER_DEPRECATED

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.4.zip:
Md5: 74a664ac2b6973bcd4315faf0bbceeb1
Sha1: d1b6d1f241edf2232fde9cfaaeda2e48545ed320

xoops-2.4.4.tar.gz:
Md5: 2ed6fc93c62c0a23ddc4d5d436775ea4
Sha1: 332565d3ebd483940803ffeb93827fc45f1de8bf

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.x (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.

WOX (World of XOOPS) Newsletter # 29 (February 2010)

As always, as the first thing in each newsletter we wanted to express our gratitude to all of you who have donated money to XOOPS Foundation! We truly appreciate your trust and support! 

What a great start of 2010 - January was an extremely busy month. We've released XOOPS 2.4.4 and XOOPS 2.5.0 Alpha.  

Unfortunately, we also lost a member of our community - Marcello Brandao, who lost his battle with cancer. In appreciation of his vast contributions to XOOPS and saddened by his untimely death, the XOOPS Council decided to induct Marcello Brandao into XOOPS Hall of Fame.

We have also filed our deposition in court in Netherlands in a lawsuit against our former Project Manager, Herko Coomans, for return of XOOPS funds and Intellectual Property back to the XOOPS Community. We very much appreciate the support from the XOOPS community - already over 190 XOOPS Community members signed the petition for the court in Netherlands in support of it, and and if you didn't sign yet, please sign it today

Highlights of the last month:

Xaraya Core release 1.2.0

Major changes:

  • Minimum PHP requirement increased to 4.4.7.
  • New Installer theme. Xaraya_Classic can now be uninstalled, as it is no longer tied to install and upgrade processes.
  • All templates renamed to .xt file extension. Templates in non-core modules named .xd are still supported.
  • Support for JavaScript frameworks added in base/xarjavascriptapi.
  • jQuery added as default JS framework in Base module, with several plugins.
  • Code to upgrade from 1.1.x and 1.2.0-b1 added
  • Xaraya can now send 4xx and 5xx HTTP response headers in applicable situations
  • $modName is deprecated in xarSecGenAuthKey() and xarSecConfirmAuthKey()
  • PHP functions deprecated in 5.3 no longer used.
  • New config var XAR_BL_VERSION_NUM added
  • Themes are now installable only if their bl_version is compatible
  • Module vars now used to toggle admin_capable and user_capable; those columns in modules DB table are now read only except during module upgrade.

General fixes and improvements:

  • Upgrade ADODB to 4.991.
  • base/xarversionsapi changed to revolve around unified version number format (See RFC44, Section 6).
  • xarModURL() can now produce https URLs when requested.
  • Tango (http://tango.freedesktop.org/) added to the base module and used throughout the core modules. Additional Tango-style icons created as needed.
  • Module icons now live at [module]/xarimages/[modname].png. Tango-style PNG icons for core modules added at this location. Old-style admin.gif icons still supported.
  • Several javascript files replaced with jQuery code and/or plugins:
    • base/calendar.js
    • base/checkall.js
    • base/confirmlink.js
    • base/formcheck.js
    • base/orderitem.js
    • base/toggle.js
    • base/xmlhttprequest.js
  • DD Calendar property now uses jQuery plugin ui.datepicker.
  • DD OrderSelect property uses custom jQuery code.
  • Tree displays in Roles and Privileges now use jQuery TreeView plugin.
  • Inline JavaScript event handlers in core modules reduced from 171 to 5 (4 are in unused files).
  • Other UI enhancements made possible with JS framework (jQuery).
  • In menus, the module category "Global" has been renamed to "System".
  • Several new classes added to theme CSS:
    • .xar-items: Applied wherever data items are displayed in a table.
    • .xar-item-actions: Applied to the table cell which contains the action (modify, delete, etc) links for each item, typically the right-most cell.
    • .xar-item-controls: Applied to parent elements of inputs used to control or filter displayed items. Examples are the horizontal tables displayed at the top of the UI in many admin-list functions.
    • .xar-form-footer: Applied to parent elements of buttons used to control a form (at the bottom of the form).
    • .xar-form-section: Applied to div elements to separate sections of a form.
    • .xar-icon: Applied to icon img elements or their immediate parent, such as links.
    • .xar-icon-disabled: Applied to icon img elements or their immediate parent when the represented action is not allowed.
  • JS plugins can now live in modules other than the framework's host module
  • JS plugin registration is now automated
  • Modules can now specify expanded dependency info
  • Themes are now checked for BlockLayout version compatibility
  • Reformatted info templates for modules and themes
  • Custom Object list template for privileges
  • Plain and Tabbed views removed from Roles admin
  • Base encode shorturls: skip encoding for systemexit and rawexit functions to allow usage of the correct error template
  • Additional icons: item-list, move, go-up-left, go-up-right, go-down-left, go-down-right
  • Improvements to blocks modify instance template
  • JS-driven drag-and-drop implemented where order of items can be set: DD properties, blockgroup members
  • Replace inappropriate fieldset tags with h3/h4 and div.xar-form-section
  • Added timepicker extession to jQuery UI Datepicker
  • Changed about.xt in Xaraya_Classic to advise users that this theme can be uninstalled#

 

Important changes / bug fixes://bugs.xaraya.com