Posts tagged "cms"

SoftPraise released by JoomlaPraise

This theme is designed to showcase any type of product or web software. That is what JoomlaPraise say on their website so I am not going to disagree with them, but don't be put off thinking it is only for a product of piece of software.

But, it is released and you can go have a play and look here.

Features:

5 Color Themes!

At JoomlaPraise our job is to make you look good. We also want your software to have a great presentation. The SoftPraise template comes with five customizable themes to get your software website up and running. Click on the themes below to see the different styles SoftPraise can offer your website.

Source Artwork

SoftPraise includes layered vectory PNG artwork for Adobe Fireworks. We've done some extensive documentation that explains how to customize each element of the SoftPraise template. From gradients to button to background colors the source artwork will help make your website unique.

16 Module Positions

The Softpraise template comes with sixteen module positions to help customize your user experience. Go module crazy and get your software noticed.

iPad Fireworks PNG Included (Exclusive!)

The vector artwork for the iPad is included, so you can showcase any software or site on it!

 

More from JoomlPraise later this month, until then click here to see what else they have.

New theme released from RocketTheme: Kinetic

New Gantry powered theme time from the guys over at RocketTheme and it comes packed as you would expect but with more emphasis this month on styling.

You get the usual styling for the RocketTheme extensions and the eight style variations the theme comes with, each with three variables, but this month you also get twenty different module variations on top of the over 60 module positions that are available to use.

I say over and don't put a specific number on it, because with the Gantry Framework, you get to add as many more as you want when you want from the backend of Joomla.

Some, but not all of the features are listed here:

  • Gantry Framework 2.0
  • 8 Style Variations - 3 Detail Levels
  • 5 Showcase Variations [Gantry Configurable]
  • RTL Support
  • RT Extensions Styling
  • Custom Typography
  • Javascript Form Styling
  • Fusion Menu & SplitMenu
  • 20 Module Variations
  • Over 60 Module Positions
  • FF3.5, Opera, Safari 4, IE7,8 Compatible
  • Limited IE6 Support
  • W3C XHTML 1.0 Transitional. W3C CSS 3 Valid

For a demo, more information or to join the RocketTheme club, just click here.

NOTICE: Kinetic is a Joomla 1.5 only template.

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

WebsiteBaker 2.8.1 Stable released

After showcasing three release candidates during the last weeks the developer team is proud to present the final and stable release. In WebsiteBaker 2.8.1 several minor bugs have been fixed and some modules have been updated to new versions.

Here's an overview about some changes:

  • updated and optimized backend template
  • preparation for multilingual websites
  • updated FCKeditor to version 2.6.5
  • updated jQuery framework to version 1.4.1 (you can find version 1.3.2 still within the
    installation files)
  • updated YUI framework to version 2.80r4
  • updated EditArea to version 0.8.2
  • updated droplet module to version 1.0.2
  • updated news module to version 3.5


In addition to a full installion of WebsiteBaker 2.8.1 upgrades are possible from WebsiteBaker 2.7.0 or later.

The Download is available here

TYPO3 Version 4.3 Released

The TYPO3 Association released the newest version of their outstandingly successful Open Source project TYPO3. TYPO3 has been downloaded over 4.1 million times – making it one of the world’s leading Enterprise Open Source projects.

The latest TYPO3 version 4.3 comes packed with numerous brand new features and improvements. Highlights include the completely new Frontend editing module and the integration of Extbase and Fluid. Additionally, TYPO3’s already excellent security features have been improved even further.

ELGA LabWater, a subsidiary company of Veolia Water launches website in 7 languages

The new ELGA LabWater website has been launched, with all pages rendered in English, French, German, Spanish, Portuguese, Japanese and Chinese.

The site uses Tribiq's Advanced Visitor Language Support (AVLS) system, part of the Tribiq CMS Enterprise suite of products.

AVLS allows the pages of the website to be synchronized and kept in sync across several different languages. It also contains tools to allow site content to be exported, translated in an offline environment, and imported back into the site.

Not only is the central version-controlled content supported in all languages, but also all the occasional phrases which appear around the site.

Tribiq CMS has complete UTF-8 support which is essential for languages with extended character sets such as Chinese and Japanese, so these are stored and rendered correctly across the site.

Domain mappings and auto language detection

The ELGA LabWater site makes use of the power of Tribiq CMS's abilities to route incoming visitors to the correct pages based on various available data.

For example, while the URL www.elgalabwater.com goes to the English website home page, the URL elgalabwater.de routes visitors to the German home page.

In addition, the site performs auto-detection of visitors' browser settings, so as to determine which language to use. This helps ensure that customers immediately see a page in their own language, without having to make a choice.

Interactive Features

The site contains Flash-based interactive world maps, so that visitors can locate their country and find a local contact.

There is also a sophisticated product selector (implemented equally in all languages) which lets visitors enter their requirements, and which then recommends the ideal system based on some business rules.