phpBB was started by James Atkinson as a simple UBB-like forum for his own website on June 17, 2000. Nathan Codding and John Abela joined the development team after phpBB’s CVS repository was moved to SourceForge.net, and work on 1.0.0 began. A fully functional, pre-release version of phpBB was made available in July.

phpBB 1.0.0 was released on December 9, 2000, with subsequent improvements to the 1.x codebase coming in two more major installments. The final release in the 1.x line was phpBB 1.4.4, released on November 6, 2001. During the lifetime of the 1.x series, Bart van Bragt, Paul S. Owen (former co-manager of the project), Jonathan Haase and Frank Feingold joined the team. phpBB 1.x is no longer supported and virtually no websites continue to use it.

In February 2001, phpBB 2.0.x began development entirely from scratch; the developer’s ambitions for phpBB had outgrown the original codebase. Doug Kelly joined the team shortly afterwards. After a year of development and extensive testing, phpBB 2.0.0, dubbed the “Super Furry” version, was released on April 4, 2002, three days later than intended.

Work on phpBB 3.0.x began in late 2002. It was originally intended to be released as phpBB 2.2, and the first planned feature list was announced on May 25, 2003.[4] However, as development progressed, the developers realised that phpBB 2.1.x (the development release cycle for 2.2) had eliminated virtually all compatibility with the 2.0.x line, the version number for release was changed to 3.0.0, in keeping with the Linux kernel versioning scheme. In September 2005, Paul Owen resigned as the Development Team Leader and Meik Sievertsen was promoted to the role.

In March 2007, the phpBB teams had planned to undergo a short round of server maintenance, however the server crashed during the outage, suffering a double-disk failure and causing phpBB.com to be down for the full week. (The phpBB teams indicated that phpBB, the software, was not the cause of the outage.) However, due to the unexpected outage, the teams decided to change their original plans and launch their brand new website, powered by phpBB3 and the new prosilver theme. This was a big surprise to most, as the theme had been a heavily guarded secret, never before seen by the public, and was originally not intended to be revealed until the final release of phpBB 3.0.0. Initial feedback was split, with many applauding the new theme and others criticising a number of new design decisions, particularly the decision to display the user info on the right side of the viewtopic page (phpBB2′s subSilver theme had displayed it on the left).

On April 30, 2007, phpBB founder and co-Project Manager James Atkinson officially resigned from his duties towards phpBB, citing personal circumstances. With the announcement also came the announcement that phpBB was now newly independent, and that the team leaders would be collectively taking charge of the decisions in the future of the project. At the end of May, an announcement was made that Jonathan “SHS`” Stanley, the other co-Project Manager, was stepping down as well for personal reasons.

On July 7, 2007, the teams announced that phpBB had been nominated as a finalist for the SourceForge.net Community Choice Awards in the category of “Best Project for Communications”. At the end of the month, SourceForge.net announced that phpBB had won the award for “Best Project for Communications”, and in honour of the award, SourceForge.net donated $1000 in phpBB’s name to Marie Curie Cancer Care. phpBB also won a “Thingamagoop” from Bleep Labs, and “bragging rights for a full year.”

On September 6, 2007, the teams launched an official phpBB podcast. It was recorded by a rotating group of phpBB team members with occasional guests, and discussed a number of phpBB-related topics, as well as answering questions e-mailed in from listeners.

The first beta of phpBB3 was released in June 2006, and the first release candidate was released in May 2007. The phpBB3 codebase received an external security audit in September, which was done by SektionEins. Finally, phpBB 3.0.0 “Olympus” (also dubbed the Gold release) was published on December 13, 2007.

The teams launched a new phpBB weblog in July 2008. The blog is written by phpBB team members on various topics related to phpBB and provide users with a unique inside look at the activities of the phpBB teams.

The phpBB teams held their first-ever phpBB users conference in London on July 20, 2008, which was titled “Londonvasion 2008.” Londonvasion featured presentations by phpBB team members on various topics important to the phpBB community, MOD authors, and developers. Londonvasion provided a unique opportunity to socialise with members of the phpBB teams. The event also represented the first time that most members of the teams had a chance to meet each other in person.

More on PhpBB

• phpBB2 was the predecessor of the present-day phpBB3. Developed during 2001-2002, the source code was written primarily to run on PHP 3.0 and 4.0 (version 2.0.13 upped the minimum requirement to PHP 4.0.3 due to a necessary security fix), and by the time that phpBB3 was released in late 2007, …
• phpBB3 is the current stable version of phpBB. Following over three years of development and an eighteen-month beta/release candidate stage, it went gold on December 13, 2007. Some of phpBB3′s major features include: Modular design for the Admin Control Panel, Moderator Control Panel, and User Control Panel Support for multiple database management systems, …

Other Information

• Developed by  The phpBB Group
• Stable release  3.0.4  (December 12, 2008)
• Written in  PHP
• Available in  Multilingual
• Type  Internet forum
• License  GNU General Public License

Links

• Website  http://www.phpbb.com/
• Downloads
• PhpBB Mods
• PhpBB Knowledgebase
• PhpBB wiki

Incoming search terms:

• Powered by phpBB
• phpbb
• important phpbb
• powered by phpbb3 introduction to human services through the eyes of practice settings
• available powered by phpbb3
• work phpbb
• adult phpbb demo phpbb
• reference phpbb
• steves phpbb limited forum
• months phpbb

SMF was created to replace the forum software YaBB SE, which at the time was gaining a bad reputation because of problems with its Perl-based ancestor software YaBB[citation needed]. At the time, YaBB was attributed to causing resource allocation problems on many systems. YaBB SE was written as a rough PHP port of YaBB, and had many of the same resource and security problems of the older YaBB versions. Joseph Fung and Jeff Lewis of Lewis Media Inc., the owners of YaBB SE and the original owners of SMF, made the decision to convert to a new brand and name.

SMF started as a small project by username "[Unknown]" (one of the YaBB SE developers) and its main intent was to add more advanced templating to YaBB SE. The project then slowly grew to address common feature requests, efficiency problems, and security concerns. A rehaul of YaBB SE had been in development for several years, but was superseded by this then competing project. Popular interest in the new YaBB SE fork sparked a complete rewrite of the code, with security and performance in mind. This eventually became today’s Simple Machines Forum.. The first SMF release was SMF 1.0 Beta 1a, released on 30 September 2003 to Charter Members only.

On the 23rd of October 2006, Simple Machines LLC was registered in the state of Arizona, and the transfer of copyrights from Lewis Media to Simple Machines LLC was completed on the 24th of November 2006 during a three-day retreat in Tucson, AZ. This was done for the "[solidification of] the team’s commitment to continuously providing free software, without the perceived risks of corporate influence"

Future

On 8 April 2007, Simple Machines announced the introduction of their next version, SMF 2.0 [8]. SMF 2.0 has been in development alongside SMF 1.1 since December 2005. This version will have many new features, including:

• Database abstraction – with support for PostgreSQL and SQLite planned alongside that of MySQL.
• Automatic installation of packages into themes other than just the default.
• Email templates to simplify customization of forum emails.
• Moderation center including post, topic and attachment moderation – to allow approving of user content before it is made public.
• User warning system.
• Additional group functionally including group moderators and requestable/free assignable groups.
• WYSIWYG editor to provide an intuitive user interface to those users not familiar with BBCode.
• Permission improvements such as group inheritance and permission profiles to further reduce the complexity of the permissions system.
• File based caching for a performance increase on all forums regardless of whether an accelerator is installed.
• Mail queuing system to stagger the sending of emails to improve performance on large forums.
• Advanced signature settings to allow the administrator of a forum to more tightly control the contents of users signatures.
• Personal messaging improvements including ability to automatically sort incoming messages and a variety of display options.
• Improved upgrade script with better timeout protection and simpler user interface.
• Custom profile fields to enable administrators to add additional member fields from the administration center.
• Use of OpenID.

The first public beta of SMF 2.0 was released on Monday, March 17 2008.

Localization

SMF is available in over 38 languages[9], including Albanian, Arabic, Bulgarian, Catalan, Chinese, Czech, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Hungarian, Italian, Japanese, Norwegian, Persian, Polish, Portuguese, Romanian, Russian, Spanish, Swedish, Thai, Turkish and Ukrainian. It can be translated to other languages by volunteers. UTF-8 and non-UTF-8 encodings are available for all.

Modifications

SMF has a modification base repository for free modification hosting and tracking via the Simple Machines main site. Many modifications, or "mods" as they are usually called, have been created and distributed free of charge, including an arcade, profile additions, gallery, RPG system, spam filter, various SEO features, and many more. Before being listed on the SMF Mods site, the mod is validated by the SMF Team, to ensure that it complies with the SMF Coding Guidelines.

The Package Manager included in SMF is one of the flagship features. It allows an administrator to install modifications and updates to SMF without having to modify the code of the script, usually with only a few mouse clicks.

The SMF team

The Simple Machines team includes graphics, documentation, customization, localization, marketing, and management divisions. The SMF support staff and users also provide free support on the official community forums. Their duties include helping forum owners with troubleshooting and optimization.

Charter Members

People who wish to support Simple Machines with a donation of 50 USD yearly are rewarded with a Charter Membership. This grants access to a hidden section on the forum and advanced beta versions to test before they go public. Advanced support for SMF including installation and upgrades by the staff are also provided. Charter Members also get access to a private Helpdesk staffed by the Simple Machines Support Team where Charter Members can receive one-on-one support outside of the public forum.

SMF and free software

SMF is occasionally criticized for not being available under a free software license; the developers acknowledge this. Redistribution of the software, even unmodified, is not allowed without written permission. The source code is not redistributable either, although it is allowed to distribute instructions on how to modify it.

Minimum System Requirement

To run SMF, the webserver you’re hosted on must meet a few simple requirements. These are not terribly high, and as such most hosts meet them.

• Any webserver that properly supports PHP, such as Apache or Internet Information Services (IIS).
• PHP 4.1.0 or higher. The following directives are required to be set correctly in php.ini:
  • the engine directive must be On.
  • the magic_quotes_sybase directive must be set to Off.
  • the session.save_path directive must be set to a valid directory.
  • the file_uploads directive must be On.
  • the upload_tmp_dir must be set to a valid directory.
• MySQL 3.23.4 or higher.
• at least 512 kilobytes of storage space in the database, although more is highly recommended.
• about two and a half megabytes of storage space on the web server, although more is recommended.

Recommended System Requirements

However, for best performance and use, a bit more is suggested. This includes the following:

• Linux or another Unix based operating system.
• The GNU Aspell and its dictionaries for spell checking support.
• Apache with AcceptPathInfo set to On (Apache 2 and later only) for queryless URL support.
• PHP 4.3.0 or higher, with the following set in php.ini:
  • the max_input_time directive is set to a value of at least 30.
  • the post_max_size and upload_max_filesize directives are set to the size of the largest attachments you wish to be able to upload.
  • the session.use_trans_sid directive set to Off.
  • the memory_limit directive is set to at least 8M.
  • the max_execution_time directive is set to at least 15.
  • the register_globals directive is set to Off.
• MySQL 4.0.15 or higher with query caching enabled.
• GD Graphics Library 2.0 or higher.

Links

• Official Website
• Download SMF
• SMF Mods
• SMf Themes
• SMf – Powered-by

Incoming search terms:

• powered by smf
• bowser simple machine forum
• grenade powered by smf
• ones smf
• Simple Machines Forum
• tube inurl:/forums/
• change use simple machines llc
• simple machines required information applicants
• duties yabb
• daffodils simple machine forum

osCommerce was started in March 2000 in Germany by project founder and leader Harald Ponce de Leon as The Exchange Project. While osCommerce is still officially in its development stage, the current Milestone 2.2 release (Release Candidate 2a) is considered stable. As of August 2008 the osCommerce site says that there are over 14,000 ‘live’ websites using the program.  This number is almost certainly conservative, given the inclusion of osCommerce in hosting panel application installers such as Fantastico (web hosting) and its dependency on osCommerce users linking their sites into the osCommerce Live Stores listings.

The planned Milestone 3.0 is expected to be a major re-write of the program to incorporate an object-oriented backend, a template system to allow easy layout changes, and inclusion of an administration-area username and password definition during installation . An early release candidate of osCommerce 3.0 (osCommerce Online Merchant 3.0A4) has been available for download since Mar 31 2007, 03:11 AM

On 29th of October, 2008 it was announced by Harald Ponce de Leon (Project Leader) that the goal is to get v2.2 finalized and to release v3.0 Alpha 5 as soon as possible.

Oscommerce v2.2 was finalised released by oscommerceproject.org on the 11th of December 2008 due to a lack of progress by the original projects founder. Milestone 3 core seems to be considered out of date by the project & a version 4 is being discussed.

Other Information

• Developed by  Harald Ponce de Leon
• Latest release  2.2 RC 2a / 2008-01-30;
• Preview release  3.0 Alpha 5 “Vanillekipferl” / 2009-03-14;
• Written in  PHP
• OS  Cross-platform
• Type  Webshop
• License  GNU General Public License
• Website  http://www.oscommerce.com/

Incoming search terms:

• osCommerce Online Merchant Copyright © 2008 osCommerce
• intext:oscommerce online merchant v2 2 rc2a inurl:oscommerce/
• osCommerce Online Merchant Copyright © 2008 by
• Powered by osCommerce 2 2

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/

Incoming search terms:

• powered by joomla 1 5

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

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

CMS Made Simple provides a mechanism for the website administrator to create and manage “pages”, their layout, and their content. CMS Made simple is unobtrusive…. You can create a table based layout, or a fully validating XHTML/CSS layout.

CMS Made Simple makes managing the navigation in your website a breeze… you can re-organize your pages any way you want, and navigations are automatically created from your page hierarchy. This tool makes creating numerous different navigations with the entire page hierarchy, or a subset of it “simple”.

CMS Made Simple separates layout code from content code, so that editors can manage content without having to know much about how websites work, so that layouts can be easily edited and take effect on numerous pages, and can be easily shared. With CMS Made Simple you design once, and easily use that same design over and over again. Smarty (a php based templating engine) is used to provide most of the caching, templating, and logic capabilities. This basic building block also provides the ability for website administrators to virtually eliminate any duplication of code or content.

The Core package provides the ability to manage news articles, search functionality a contact form, a WYSIWYG editor (for your customers or editors) and numerous other built in functions. Additionally, there are hundreds of third party add-on tools that are quickly and easily installable to allow building websites with many different capabilities.

CMS Made Simple is built in PHP, and allows you to integrate many existing PHP scripts or PHP snippets into your website… Though you definately don’t need indepth knowledge of PHP to use CMS Made Simple.

Who should use CMS Made Simple?

If you’re an experienced web developer. If you have found that sometimes creating a simple corporate or organization website is difficult in some of the other content management systems. If you have found that other CMS’s are sometimes “overkill” for what you need. If you want to be able to hand off the content management to editors. If you want complete control over the layout and appearance of the site, and you know how to do it… If you want a simple, easy to use, yet expandable tool – then CMS Made Simple is probably for you.

CMS Made Simple is not a replacement for packages that build static websites like Dreamweaver or FrontPage, etc. These packages don’t use databases, provide little in the way of dynamic content, and usually content cannot be edited by customers.

Is CMS Made Simple really “simple”?

Yes it is. Many of our experienced users find it a simple tool for building many websites. However, that does not mean that there isn’t some learning to be done. You will at the least need to learn our vocabulary, explore the package and it’s options, play around a bit, and probably do considerable learning. Did you jump right in to HTML and learn how to do professional websites in 30 minutes. Probably not, and CMS packages (including this one) are similar. There are a few things you will need to learn.
5. What knowledge do I need?

To take advantage of CMS Made Simple, you should have at a minimum a basic understanding of:

• Creating Databases, and backing up / restoring databases.
• Working with, and transferring files to a remote host
• Manipulating permissions on remote hosts
• A basic understanding of HTML and CSS
• Diagnosing errors:

From time to time, with different hosts, problems do occur in any online application. When working with these, you need a basic understanding of how they work, and how to diagnose some problems, so that you can assist the support personnel, or perhaps identify and solve the problem on your own. This includes:

• Finding your website error logs and access logs
• The ability to understand some of the error messages or access log lines
• The ability to find, identify and to some level diagnose Javascript errors
• An ability to learn independently, and do some research on your own.

What are the system requirements?

• Web server with PHP 4.3+ (Linux/Unix, Windows 2000/XP/ME/2003, OS X)
  • (CMS Made Simple does not officially support PHP safe mode)
  • At least 16mb of available memory for PHP (This should work fine for most small to medium sized websites. However, as your site grows, or you utilize other addon modules, your memory requirements may increase.)
  • PHP tokenizer support enabled
  • At least one of ImageMagick or GD enabled
  • MySQL 3.23 or 4.0+ or PostgreSQL 7 +
  • Enough access to your server to upload files and change some permissions

Where can I get help/support?

There are numerous forms of support available for CMS Made Simple:

• The default content: – The well documented content pages, templates and stylesheets that are displayed with a new installation of CMS Made Simple are an invaluable way of introducing yourself to the package and getting to know how the package works. We encourage you to read all of this thoroughly and save this information for future reference while building your website.
• The Documentation
• Built in Help: -   Each module and tag installed in a CMS Made Simple website includes basic help and examples to assist in utilizing the the functionality.
• Public/Community support

The CMS Made Simple forum is an invaluable way of finding out information about the CMS Made Simple core, and the add-ons. There are thousands of posts by the development team and members of our community that describe the various problems our users have encountered, and how they were solved.

We attempt to keep the forum clean from distracting posts, or posts that are not directly and specifically relevant to CMS Made Simple. Additionally, in order to expedite support, we ask that all users spend the time to research, and accurately describe their issues. Therefore please read and follow the forum rules when posting.

• Commercial Support: – Paid support is available to those people with an important project that are concerned about the turn-around time that may be related to getting an issue solved. Additionally, if you would like to have somebody to call for problems that you just can’t fix, upgrade issues, backups, or any other concern, then commercial support may be an option for you.
• Paid Development: – So you’ve got the tool up and running, and you like what you see…. but your project requires some functionality that isn’t yet available for CMS… or doesn’t quite work the way you want it to. For that, the CMS Made Simple Development Team offers independent contracting services. Our in-depth knowledge of the tool, and experience in building the package and its add-on modules can ensure that you get a working, well fitting, quality tool.

Other Information

• Developer:  Ted Kulp
• Current version:  1.5.1 “San Juan”(04 December 2008)
• Operating system:  all LAMP systems, Windows and Mac
• Category:  Content Management System
• License:  GPL (free software)

Links

• Official Website
• Theme
• Modules
• Tags and Plugins
• Download

Incoming search terms:

• cms made simple remove powered by

SilverStripe offers a flexible MVC development framework known as Sapphire. Much like Ruby on Rails, but for PHP, it ensures developers are capable of extending and enhancing the functionality of the CMS and the website. More importantly, SilverStripe provides developers with complete control of the generated markup; allowing for higher, semantic standards of XHTML.

SilverStripe is released under the terms of the BSD Licence. An abundance of documentation is available from the SilverStripe help website and wiki. An online demonstration of the CMS is located at the SilverStripe demo website.

History

Prior to SilverStripe 2.x, the CMS was commercially available under a proprietary license. Development efforts for SilverStripe 2.X started in late 2005, as a complete overhaul to take advantage of object orientation and new features in PHP5. On 3 February 2007, SilverStripe 2.0.0 was released publicly as free and open source software.

Motivations and reasoning for moving towards an open source development model were the anticipated results of greater exposure, higher quality code and community contributions.

In March 2007, SilverStripe was selected for the Google Summer of Code programme. The contributions of the students who participated in the programme ultimately resulted in the 2.2 release of SilverStripe.

On 29 November 2007, SilverStripe announced they would be participating in the Google Highly Open Participation (GHOP) contest. This led to a proliferation of themes, translations and widgets that broadened the system.

Features and Add-ons

Notable features include multiple methods of organising navigation through folksonomy, a flexible data object model, multiple templates per page, a separate “Draft site” and “Published site” through staging content, asset management, image resizing, versioning control, search engine friendly URLs with meta-data, automatic sitemap generation, full text search and RSS feeds. SilverStripe supports UTF-8 and the internationalisation of character sets; the CMS is currently available in English, French, German, Spanish, Chinese, Croatian, Dutch, Polish and Portuguese.

Modules

The highly modular nature of SilverStripe has resulted in the creation of numerous pre-build modules that extend the core functionality of the CMS. A list of available modules is viewable below:

• Blog
• E-commerce
• Embargo/expiry
• External Authentication (LDAP, AD, etc)
• Flickr Gallery
• Forum
• Gallery
• Maps
• Technorati
• Youtube Gallery

Widgets

Widgets are small pieces of useful functionality that can be instantly dragged and dropped into a website. A list of available modules is viewable below:

• Built-in widgets for the blog module
• Countdown
• Del.icio.us
• Digg
• Featured Video
• Feedburner
• Feedburner Email Subscription
• Google Adsense
• Google Custom Search
• IMStatus
• LanguageChooser
• last.fm
• Links
• NASA image of the day
• New Users
• Ohloh contribution
• PayPal donation
• Popular Blog Posts
• Recent Page Comments
• Time
• TwitterStatus
• WoW Character

Themes

The SilverStripe themes directory provides a number of community-contributed, freely available themes; providing developers and website owners with the capability to instantly modify the aesthetics of their SilverStripe website.

Software Requirements

SilverStripe is a web application, requiring a compatible HTTP server and SQL database. As of version 2.2.0 (28 November 2007), the requirements for SilverStripe are as follows:

• Apache v1.3.19+ or Lighttpd with mod_rewrite support
• MySQL v4.1.X+
• PHP 5.2+ with MySQL, GD_Graphics_Library and Zlib support

Other Information

• Developed by  SilverStripe
• Latest release  2.2.3 / 31 October 2008;
• OS  Cross-platform
• Type  Content management system
• License  BSD Licence

Links

• Official website
• Online demonstration website
• Official help documentation
• Community forums
• Developer documentation wiki

Incoming search terms:

• blog comment powered by Silverstripe

Introduction

The DotNetNuke application

originally evolved out of another project, called the IBuySpy Workshop.

The IBuySpy Workshop application had been created by Shaun Walker as an enhancement to the IBuySpy Portal starter kit.

Microsoft had earlier released the IBuySpy Portal as a sample application for the .NET Framework.

Shaun Walker (the original creator) has implied that the name DotNetNuke was coined by combining the term .NET with the word “nuke” which had been popular with pre-existing frameworks such as PHP-Nuke and PostNuke. The term DotNetNuke and DNN are registered trademarks in Canada.

In September 2006, four members of the project’s board of directors formed a corporation to oversee the development of the project. The new DotNetNuke Corporation was co-founded by Shaun Walker , Joe Brinkman, Nik Kalyani  and Scott Willhite  and replaced Perpetual Motion Interactive Systems Inc. as the corporate entity behind the project.  Subsequently, the DotNetNuke Corporation announced that it would be represented by Mark F. Radcliffe from the firm of DLA Piper.

As of November 2007, the DotNetNuke application had seen over 4 million downloads throughout its 56 public releases , and is currently in its fourth edition. Version 4.0 or later requires version 2.0 of the ASP.NET Framework, but earlier versions will run on ASP.NET 1.1.

On November 25, 2008 DotNetNuke announced Series A financing from Sierra Ventures and August Capital.

Extensibility

DotNetNuke has a basic core which can be extended using pluggable modules and providers that enable additional functionality; the look and feel of individual sites can be customized using skins.

Modules

About a dozen basic modules are included with the core DotNetNuke distribution, and further modules can be downloaded from the DotNetNuke website, including e-commerce systems, photo galleries, blogs, forums, wiki and mailing list options. Additional third party modules are provided by both the open source community and proprietary commercial DNN developers.{{Fact|date=Oc

Skins and Containers

DotNetNuke has a skinning architecture which provides a clear separation between design and content, enabling a web designer to develop skins without requiring any specialist knowledge of development in ASP.NET: only knowledge of HTML and an understanding of how to prepare and package the skins themselves is required.[citation needed] Skins consist of basic HTML files with placeholders (tokens) for content, menus and other functionality, along with support files such as images, style sheets and JavaScript, packaged in a ZIP file.

Upon Microsoft’s release of the .NET Framework version 2, Microsoft had included a piece of functionality known as master pages. The principle idea behind master pages was to encourage code recycling and consistent design and aesthetics throughout a site by creating a master page with placeholders, which at runtime would be compiled and replaced by content.

Although this advancement was considered significant, DotNetNuke decided to keep its skinning engine, using the argument that to construct master pages, a web designer needed access to Microsoft’s Visual Studio, which would then put developer code at a compromisable risk (as master pages have the ability to contain VB.NET code). Bearing in mind that a significant proportion of web designers choose to use Apple’s series of hardware and operating systems, DotNetNuke decided to retain the skinning engine to retain its open-source ideals and availability to the web design community.

Like modules, compiled (“ZIPped”) skins can be uploaded and automatically installed through the administration pages. If the compiled skin does not contain an ASP.NET user control file, then the DotNetNuke skinning engine builds one based on various tokens included in the HTML file which refer to various sections, placeholders and/or modules of a DotNetNuke-produced page. A number of discussions on the DotNetNuke forums debate the differences between designing skins in “pure” HTML and Cascading Style Sheets, or creating skins in Visual Studio as ASP.NET user controls.

Since version 4.4, skin developers have been able to specify skin-level DOCTYPEs to allow them to develop skins that follow accessibility and xhtml standards.

The DotNetNuke skin system was designed to allow users to create their own skins without modifying the main page (Default.aspx), the only problem is that there will be a massive amount of errors which control every page in the site.

Criticisms

• A common complaint is that DotNetNuke’s guidelines for creating a “proper” module are cumbersome. As an example, suppose a module allows a user to add a book (an object of type “Book”) to the table “Books” in the portal’s database. The method “AddBook” would need to be defined in three separate classes. (The stored procedure for adding a book into the database must be written as well.)
• Documentation is mostly written in task-oriented form. API references are not available.
• Some of the older modules do not work as advertised, though the new release process has improved the quality of new releases.
• The platform has regular updates. With previous versions, the revisions were not always stable. This has greatly improved due to the new release process.
• There is no dynamic content localization, a very important feature for a web site with contents in languages different than English.

User Groups

The importance of a user group is not forgotten within the DotNetNuke community. DotNetNuke has grown so much in popularity and adoption, that user groups  have formed to assist local members the open source community in learning more about the DotNetNuke platform.

Other Information

• Developed by  DotNetNuke Corporation
• Latest release  4.9.0 / 10 September 2008; 102 days ago
• OS  ASP.NET / Microsoft Windows
• Type  web application framework
• License  BSD style license
• Website  http://www.dotnetnuke.com/

Incoming search terms:

• cms dotnet nuke
• cms dotnetnuke
• Plone powered web sites