Call of Duty World at War – Theme by Mr. Theme

Links

• Live Demo
• Download

A Travel Theme by Mr. Theme Design.

Links

• Live Demo
• Download

What’s new?

Fixed

• #244: $HTTP_SERVER_VARS replaced with $_SERVER in checklogin.php (vaughan)
• #245: $HTTP_SERVER_VARS replaced with $_SERVER in common.php (vaughan)
• #246: <>\/ specialchars were being stripped from password fields unneccessarily. changed from stopXSS to filter_var() (and use FILTER_SANITIZE_URL) which sanitizes and only allows characters that can be used in a URL (which is applicable for passwords) (vaughan)
• #246: SMTPAuth not working – xoopsmultimailer was setting authentication type to ssl (which is correct, but other issues with phpmailer prevent it) (skenow)

Changed

• Updated HTMLPurifier Library from 3.2.0 to 3.3.0 (various bugfixes in the library including a bugfix in youtube filter). (vaughan)

For a complete list of changes, read the changelog.

Where do I get it?

You can download the latest release from our file release system on SourceForge. The download packages allows you to either do a fresh installation, or upgrade from an earlier version of ImpressCMS or XOOPS.

What else do I need?

With this release, we are moving farther into only supporting stable versions of PHP5.  The current stable release of PHP is 5.2.8 and 5.2.7 has been removed from distribution because of several critical flaws.

    * PHP: 5.2.0+(5.2.7 is NOT recommended!)
    * MySQL: MySQL server 4.1.0+ – With UTF-8 Support
    * Web server: Any server supporting the required PHP version (Apache highly recommended)
    * Special characters require UTF-8 support from hosting providers.
    * 16MB PHP Memory

ImpressCMS Community Site

The trio’s new paper was initially based in Redman’s Court, near George Street. Ten years later, John Fairfax (pictured left) began his family’s 149-year long control of the paper. The bankrupt Englishman had published the Leamington Spa Sketch Book before migrating to New South Wales in 1838.

Other Information

• Pagerank 8.0
• Alexa Rank 782

NEPTUNE Canada offers a unique and exciting approach to ocean science. Traditionally, ocean scientists have relied on infrequent ship cruises or space-based satellites to carry out their research. But NEPTUNE Canada will change this. We’re building the world’s first regional-scale underwater ocean observatory that plugs directly into the Internet. People everywhere will be able to ‘surf the seafloor,’ and ocean scientists will be able to run deep-water experiments from labs and universities anywhere around the world.

Other Information

• PageRank 7.0
• Alexa Rank 6,646,227

History

dotCMS was initially developed as a Java alternative to the PHP CMSes on the market, as well as to provide a counterpoint to high cost, enterprise applications. It is the result of over 5 years of development by dotMarketing, Inc, which also developed and released the open source project management tool dotProject. In order to achieve compliance with JSR-168 portlet specification dotCMS was built upon the Liferay portal, though has since forked Liferay at version 3.2.2. dotCMS 1.0 was initially open sourced and made available in 2005 under the dotMarketing Public License. In 2006, dotCMS released version 1.2 which included the structured content engine. In 2007 dotCMS released version 1.5, which included a new user interface and permissions. In October, 2007 dotCMS 1.5 was the runner up for Packt Publishing’s “Best New Open Source CMS” award, followed in 2008 by a second place finish for Packt’s “Best Other Open Source CMS (best non PHP CMS)”. In February 2008, dotCMS users held the first annual “Open Minds” conference in Coconut Grove, Florida. Currently, dotMarketing continues to develop and improve features within dotCMS, such as the social calendar and WebDav integration.

Community

dotCMS has an active and engaged community. There is an annual users conference, a listserv, IRC channel, and Ning and Facebook groups. dotMarketing has also began work on an official community web site, which will be home to a new documentation system a la PHP.net, allowing users to comment and provide examples of code usage, as well as collaborate. The current user base includes deployments by thousands of companies, news organizations, universities, individuals, and more. More information regarding the dotCMS community can be found on the dotCMS website.

Open Minds Conference

The first annual Open Minds Conference was held February 7-10 in Miami, FL. This event was designed to bolster excitement in the community, and provide a venue for users to meet, collaborate, and network. Topics ranged from introductory installation sessions, to more advanced talks on setting up development environments, and was attended by more than 60 participants from 20 institutions. The second annual conference is scheduled for February 4-6, 2009, and will remain in Miami.

IRC Channel

For users familiar with IRC, you can visit the dotCMS channel on Freenode. If you do not have an IRC client, or are unfamiliar with their usage, dotMarketing has provided a web page based client. Either way will allow you to chat with other users and experts on the usage of dotCMS.

Technologies

dotCMS is a standards based CMS written in the JAVA programming language, and comes bundled with the Apache Tomcat Application Server. It is database agnostic and can run on PostgreSQL, MySQL, MSSQL or Oracle. It is capable of integrating with user’s authentication scheme’s, such as Active Directory or LDAP, and will support operation in a clustered or load balanced environment. It leverages a number of standards based open source projects such as:

• Apache Struts Web Framework
• Apache Lucene Search Engine
• Apache Velocity Templating Language
• Liferay Portal
• EXT Javascript Framework
• Apache Tomcat Application Server
• OSCache distributed caching system
• Hibernate Object Relational Mapping

Structured Content

The driving concept behind content stored within dotCMS is that it is addressed through a system of structures. Structures are administrated through a back end portlet where fields are assigned to them. Fields are named and given a content type and then ordered. Each structure can then be permissioned and used when creating content, and allows different types of content with consistent components to be referenced for display on the front end. A “web page content” structure could be assigned a title and body, for instance, while “events” have titles, dates, times, locations, descriptions, links, etc. Structures therefore allow the CMS to tailor itself to the content demands of the institution using it, because they can create and define structures that are specific to their needs. Those structures can then be created through relationships, allowing content from one structure to be associated content items in another. There is no limit to the number of structures one can use within dotCMS.

Other information

• Developed by  dotCMS Development Group
• Latest release  1.6.5a / 04 December 2008;
• Written in  Java
• OS  Cross-platform
• Type  Content Management System
• License  GNU General Public License v2
• Website  http://www.dotcms.org/

Plone is released under the GNU General Public License (GPL) and is designed to be extensible. Major development is conducted periodically during special meetings called Plone Sprints. Additional functionality is added to Plone with Products, which may be distributed through the Plone website or otherwise. The Plone Foundation owns and protects all copyrights and trademarks. Plone also has legal backing from the council of the Software Freedom Law Center.

The name Plone is an homage to the Warp Records band Plone, whose music is both simple and playful. The logo represents collaboration with three dots together in a group.

MediaWiki’s “Monobook” layout is based partially on the Plone style sheets.

History

The Plone project was begun in 1999, by Alexander Limi, Alan Runyan, and Vidar Andersen. It was made as a usability layer on top of the Zope Content Management Framework. The first version was released in 2001. The project quickly grew into a community, receiving plenty of new add-on products from its users. The increase in community led to the creation of the annual Plone conference in 2003, which is still running today. In addition, “sprints” are held, where groups of developers meet to work on Plone, ranging from a couple days to a week. In March 2004, Plone 2.0 was released. This release brought more customizable features in Plone, and enhanced the add-on functions. In May 2004, the Plone Foundation was created for the development, marketing, and protection of Plone. The Foundation has ownership rights over the Plone codebase, trademarks, and domain names. Even though the foundation was set up to protect ownership rights, Plone remains open source. In March 12, 2007, Plone 3 was released. This new release brought inline editing, an upgraded visual editor, and strengthened security, among many other enhancements. Up to September 2007, there have been over 200 developers contributing to Plone’s code. Plone won two Packt Open Source CMS Awards.

Design

Plone is built on the Zope application server, which is written in Python. Plone is made such that all information stored in Plone is stored in Zope’s built-in transactional object database (ZODB). Plone comes with installers for Windows, Mac OS X, and Linux, along with other operating systems. New updates are released regularly on Plone’s website. Plone is available in over 35 languages. Its interface follows the government standard WAI-AAA and U.S. section 508, which allows people with sight disabilities to properly access and use Plone. A major part of Plone is its use of skins and themes. When working with Plone, templates can be used to customize a website’s look. These templates are written with Cascading Style Sheets. In addition, Plone comes with a user management system called Pluggable Authentication Service. Introduced in Plone 2.5, “PAS” is used to properly sort actions from different users to their respective folders or accounts. PAS is also used to search for users and groups in Plone. Most importantly, PAS covers the security involved for users, requiring authentication in order to login to Plone. This gives users an increase in both security and organization with their content. A large part of Plone’s changes have come from its community. Since Plone is open source, the members of the Plone community regularly make alterations or add-ons to Plone’s interface, and make these changes available to the rest of the community via Plone’s website.

Community

Since its release, many of Plone’s updates and add-ons have come from its community. Events called Plone “sprints” consist of members of the community coming together for a week and helping improve Plone. The Plone conference is also attended and supported by the members of the Plone community. In addition, Plone has an active IRC channel to give support to users who have questions or concerns. Up through 2007, there have been over one million downloads of Plone. Plone’s development team has also been ranked in the top 2% of the largest open source communities.

Strengths and weaknesses

Plone excels when compared to other content-management systems in standards conformance, access control, internationalization, aggregation, user-generated content, micro-applications, active user groups and value. It’s available on many different operating systems, due to its use of platform-agnostic underlying technologies such as Python and Zope. Plone’s Web-based administrative interface is optimized for standards, allowing it to work with most common web browsers, and uses additional accessibility standards to help users who have disabilities. All of Plone’s features are customizable, and free add-ons are available from the Plone website.

Plone has an excellent security record compared to other popular content management systems.

Plone’s weaknesses include Python and Zope experience requirements for those wishing to add or extend the feature set, making for a considerable learning curve for developers. Plone has been rated as lagging in repository services when compared to other major CMSs.

Features

These are some of the features available in Plone 3.0:

• Inline editing
• Working Copy support
• Link and reference integrity checking
• Automatic locking and unlocking
• Collaboration and sharing
• Versioning, history and reverting content
• Upgraded visual HTML editor
• Workflow capabilities
• Authentication back-end
• Full-text indexing of Word and PDF documents
• Collections
• Presentation mode for content
• Support for the search engine Sitemap protocol
• Support for multiple mark-up formats
• Wiki support
• Automatic previous/next navigation
• Rules engine for content
• Auto-generated tables of contents
• Portlets engine
• Support, development, hosting & training
• LiveSearch
• Multilingual content management
• Time-based publishing
• Human-readable URLs
• Powerful graphical page editor
• Navigation and updated site maps
• Resource compression
• Caching proxy integration
• Drag and drop reordering of content
• XML exports of site configurations
• Localized workflow configuration
• Adjustable templates on content
• Standard content types
• Content is automatically formatted for printing
• Standards-compliant XHTML and CSS
• Accessibility compliant
• RSS feed support
• Automatic image scaling and thumbnail generation
• Free add-on products
• Cross-platform
• Comment capabilities on any content
• Microformat support
• Installer packages for multiple platforms
• WebDAV and FTP support
• In-context editing
• Backup support
• Cut/copy/paste operations on content

Other Information

• Developed by  Alan Runyan, Alexander Limi, Vidar Andersen and the Plone Team
• Latest release  3.1.7 / #REDIRECT Template:Start date and age
• OS  Cross-platform
• Platform  Zope
• Type  Content management system
• License  GNU General Public License
• Website  http://plone.org/

MiaCMS is released under the terms of the GNU General Public License (GPL) Version 2. It is written with the PHP & JavaScript programming languages and uses the MySQL database. The official project site can be found at http://miacms.org, and an online demo of MiaCMS is available at Open Source CMS Demo.

Requirements

* A Web Server (ex) Apache (version 1.3.19 or above) or Windows IIS
* PHP 4.3.2+
* JavaScript
* MySQL 4.0+

MiaCMS is thoroughly tested on Linux, FreeBSD, Mac OS X and Microsoft Windows. Linux or one of the BSD’s are recommended, but anything else that can run the three pieces of software listed above should work just fine.

MiaCMS History

MiaCMS started as a fork of Mambo. Mambo is a Trademark of the Mambo Foundation, Inc. http://www.mambo-foundation.org. Mambo was originally developed by Miro International Pty Ltd in 2000. Mambo became Open Source software in April, 2001 under a GNU/GPL license. Miro assigned the copyright in Mambo to The Mambo Foundation in 2005 to ensure that Mambo remained free Open Source software owned and managed by the community. The rights to the Mambo CMS codebase, name and copyrights, are protected by the Mambo Foundation, a non-profit corporation formed to support and promote the Mambo Open Source project.

• April 2008: Four former Mambo core developers fork Mambo and form MiaCMS. The founding members are Chad Auld, Ozgur Cem Sen, Richard Ong, and Al Warren. The reasons behind the fork can be found on the project’s main site here. The initial fork is based on a Mambo 4.6.3 SVN snapshot just prior to their 4.6.4 release.
• May 2008: The first release, MiaCMS 4.6.4, is launched. It’s code name is Flourish. Here are the release notes for 4.6.4.
• June 2008: The 2nd release, MiaCMS 4.6.5, is launched. It’s code name is Eclipse. Here are the release notes for 4.6.5. The project also launches it official site designs and creates the official logo.
• August 2008: A security patch was released to deal with some XSS issues in the 4.6.5 release.
• September 2008: Version 4.6.5 SP1 was released. This version was the 4.6.5 release prepacked with the SP1 patch so users would not have to install and then immediately patch. MiaCMS is also selected as a finalists in the Packt Publishing 2008 Open Source CMS Awards competition under the “Most Promising Open Source CMS” category. Another former Mambo core developer, Neil Thompson, has joined the MiaCMS core development team.
• October 2008: MiaCMS ties for 3rd place in the Packt Publishing 2008 Open Source CMS Awards competition under the “Most Promising Open Source CMS” category. One of the teams core developers, Chad Auld, is also named in Packt Publishing’s 2008 list of “Most Valued People from Open Source Content Management Systems”.

Other Information

• Developed by  The MiaCMS Team
• Latest release  4.6.5 SP1 Latest releases
• Written in  PHP & JavaScript
• OS  Cross-platform
• Type  Content management system
• License  GNU General Public License v2
• Website  http://miacms.org

Fixed
* #2354713: Security issue in SESSION id (Fixation), previous fix caused problems with some users being logged out sporadically. (vaughan)< /BR>
* XSS vulnerability in blocksadmin.php $_GET['selmod'], potential (but not necessarily vulnerable) exploit in $_GET['editor']. (GiJoe/vaughan)

Improved
Changelog – Click Here

Where can I get the files?

As usual you can download all the files from our Source Forge site – Click Here
Upgrade from 1.1+:

* impresscms_1.1_to_impresscms_1.1.1_rc2.tar.gz
* impresscms_1.1_to_impresscms_1.1.1_rc2.zip

Upgrade from XOOPS or ImpressCMS 1.0 to ImpressCMS 1.1.1 RC2:

* xoops-or-impresscms_1.0_to_impresscms_1.1.1_rc2.tar.gz
* xoops-or-impresscms_1.0_to_impresscms_1.1.1_rc2.zi

New Install:

* impresscms_1.1.1_rc2.tar.gz
* impresscms_1.1.1_rc2.zip

How to upgrade to XOOPS or ImpressCMS 1.0

* Upgrading from ImpressCMS 1.1
* Upgrading from XOOPS or ImpressCMS 1.0

Full Install

If you’re making a fresh install, download the full package and perform a normal installation (instructions are contained within the package or available in our release notes).

The ImpressCMS Project was formed in late 2007 as a result of a division in the XOOPS community[1]. Many of the developers for ImpressCMS were veteran developers, designers and users with extensive experience with XOOPS and sought to establish a new community built CMS with a philosophy of openness, community contributions and continual improvements in code and features. The core platform of ImpressCMS was inherited from XOOPS, but was quickly transformed into a product distinct from its parent, yet maintaining compatibility with modules and themes originally designed for XOOPS. This compatibility allows users a choice of platforms and provides them a migration path to ImpressCMS.

The product is released under the GNU General Public License Version 2 and is available for download from the ImpressCMS website. Support is offered by the community and is open to all users of ImpressCMS

Requirements

• ImpressCMS 1.0
  • Web Server – Apache, IIS, or similar web server
  • Language – PHP version 4.3, or higher (PHP 4.2.x may work but is not officially supported)
  • Database – MySQL version 3.23, or higher
• ImpressCMS 1.1
  • Web Server – Apache, IIS, or similar web server
  • Language – PHP version 5.2, or higher (PHP 5.1.x may work but is not officially supported)
  • Database – MySQL version 4.1, or higher
  • PHP requirements – 16mb minimum memory allocation for PHP, UTF-8 & IconV support (recommended)

Features

ImpressCMS uses an open architecture, allowing webmasters to add modules into the core CMS for additional functionality. Modules exist that have been developed by an international community of developers, designers and fans and are able to handle most every task associated with the managing of web content and an online community.

Basic Features of ImpressCMS:

• Database driven
• Granular permissions for users and groups
• Complete user profiles and private messaging
• Customizable themes and templates
• Integrated comment system, with moderation options
• Integrated management for banner advertising
• Site-wide search function
• Multibyte language support – distributions are available in Brazilian Portuguese, Croatian, Dutch, English, French, German, Italian, Persian, Russian, Spanish

New Features Added in Version 1.0

These new features were introduced in the first version of ImpressCMS and were not part of a standard XOOPS installation.

• Native multilingual support allows tagging of content in various languages and users can select an appropriate language for themselves
• Completely redesigned administration interface, making it more intuitive to manage
• Ability to create custom block positions for the user side, allowing greater flexibility of design and layout
• Easy cloning of any existing block with a single click
• Completely redesigned installation wizard making it easier and more intuitive for new user to install and configure ImpressCMS; also, inline help has been added to the wizard to help the user on every step of the installation
• Many security improvements, the most important being the introduction of the Trust Path concept, placing sensitive data outside the web root. This is automatically created for you by the installation wizard
• Automatic version checker to inform the webmaster a new version is available
• Addition of a privacy policy feature customizable by the webmaster
• Users can select a custom theme and save it in their preferences
• Introductory welcome content provided for the new users as part of the installation
• Introduction of HTTP error handling page using .htaccess file
• Users can select to have their login remembered on their computer; administrators can enable/disable this feature

Other Information

• Developed by  The ImpressCMS Project
• Latest release  1.1 / 31 October 2008; 50 days ago
• Written in  PHP
• OS  Cross-platform
• Type  Content Management System
• License  GPL

Links

• Website  ImpressCMS.org