DOCSLIB.ORG

Open Source CMS

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Open Source CMS Electronic Business in the Global Economy: Content Management Systems for the Personalization of Web Applications Open source CMS Term paper University of Fribourg Department of informatics Information Systems group Prof. Dr. Petra Schubert (from FHBB) June 2005: David Bächler Jeff Dicken Juchstr. 31 Rue François d’Alt 5 1712 Tafers 1700 Fribourg [email protected] [email protected] e-Business: [email protected] open source CMS [email protected] Table of contents Management Summary ______________________________________________________2 1 Introduction______________________________________________________________3 2 What is a CMS?___________________________________________________________4 2.1 CMS in general______________________________________________________________ 4 2.2 Separation Content – Design ___________________________________________________ 5 2.3 Personalization ______________________________________________________________ 5 2.4 Authorization _______________________________________________________________ 5 2.5 Multi – Channel _____________________________________________________________ 6 2.6 Maintenance ________________________________________________________________ 6 2.7 Simple Use__________________________________________________________________ 6 2.8 Must/Should/Nice to have _____________________________________________________ 6 2.8.1 Must have_______________________________________________________________________ 6 2.8.2 Should have _____________________________________________________________________ 8 2.8.3 Nice to have _____________________________________________________________________ 8 3 Open source vs. closed source________________________________________________9 3.1 Costs ______________________________________________________________________ 9 3.2 Development ________________________________________________________________ 9 3.3 Performance/Stability ________________________________________________________ 9 3.4 Security ____________________________________________________________________ 9 3.5 Support/Maintenance_________________________________________________________ 9 4 Personalization __________________________________________________________10 4.1 Personalization of the software ________________________________________________ 10 4.2 Personalization of the website _________________________________________________ 10 4.3 Personalization without a CMS________________________________________________ 11 5 Existing open source CMS _________________________________________________12 5.1 Overview __________________________________________________________________ 12 5.2 Comparison________________________________________________________________ 13 5.2.1 Typo3 _________________________________________________________________________ 13 5.2.2 eZ Publish _____________________________________________________________________ 14 5.2.3 Midgard CMS___________________________________________________________________ 14 5.2.4 Mambo ________________________________________________________________________ 15 5.2.5 OpenCms ______________________________________________________________________ 15 5.2.6 Plone _________________________________________________________________________ 16 5.2.7 Metadot _______________________________________________________________________ 16 5.3 Use of open source CMS _____________________________________________________ 17 6 Conclusion______________________________________________________________18 References________________________________________________________________19 Appendix 1: Comparison table _______________________________________________20 Appendix 2: Screenshots (Mambo) ____________________________________________21 page 1 e-Business: [email protected] open source CMS [email protected] Management Summary The first part is the introduction where the use of content management systems (CMS) is explained as well as the precise meaning of open source. Part 2 „What is a CMS?“ provides detailed information about a CMS and its important points like separation of content and design, personalization, authorization, multi- channel, maintenance, simple use. In the next part, a comparison between open and closed source CMS is done, focusing on costs, development, performance/stability, security, personalization, support/maintenance. Different aspects of personalization on the software and user side will be discussed in part 4. In part 5 a comparison of 7 different open source CMS is presented: Typo3, eZ Publish, Midgard CMS, Mambo, OpenCms, Plone and Metadot. The last part will be a conclusion about the information provided in the paper. page 2 e-Business: [email protected] open source CMS [email protected] 1 Introduction The standard websites are no longer of interest to the companies. The webmaster used to be the person who uploaded the new files and updated the older ones. Members of the different parts of the company sent files to the webmaster who had to combine them. This was not easy to manage and now with Content Management Systems (CMS), this problem is solved. Everybody can manage his own part which improves the work on the website. The user does not need to have any knowledge about programming languages to use a CMS. More details will be provided in part 2 „What is a CMS? “. The three main points of open source are: - the user does not have to pay for the software - the source code is provided totally - he can modify parts of the source code and use it under the same license But is the use really free? The standard software product can be downloaded without costs but the personal adaptation has to be done by a person with appropriate knowledge. Often the user does not have the right knowledge to do everything by himself. After this part, installation and server costs appear. There are also software updates which have to be done from time to time. Do professional open source content management systems really exist? And are there a lot of companies that use them? The (open source) CMS market is very fragmented. In the last part several CMS that claim to be professional will be tested and compared. page 3 e-Business: [email protected] open source CMS [email protected] 2 What is a CMS? 2.1 CMS in general Definition A content management system (CMS) is a software for the administration of contents of a website or from other information offers. Idea By a content management system one understands a system for the administration of contents regarding the web content lifecycle (create, control and publish). The main feature is the separation of design and content. Additionally, CMS can serve as document management systems. Distinction CMS are often confounded with portal systems or web content management systems, which do the interaction between the user and the Website. Pure CMS must not have necessarily something to do with webpublishing. Due to the common mechanisms, web content management systems (WCMS) and CMS are often regarded as the same. With a WCMS however, contrary to a pure CMS, the emphasis is on the webpublishing. If one speaks today of a CMS, then a web content management system is usually meant. Already hundreds of different WCMS/web portals exist. There are more than 100 under the open source license. Requirements Content management systems control the separation of content, layout and function and make different navigation structures possible. The user should be able to serve the system also without programming knowledge. He should be able to use the system without any knowledge of HTML and/or XML. Depending on the application an user and user right management should be implemented. page 4 e-Business: [email protected] open source CMS [email protected] 2.2 Separation Content – Design 1 Figure 1: Separation Content-Design 1 The main point of a CMS is the separation between content and design. The data is usually stored in a database (XML databases are often used and become more and more popular). The big advantage is that different groups can work on the website. The programmers can change some functions and reorganize data and the designers can create different design templates. The two parts do not need to scroll through the other persons’ source code and can implement their part without knowing the rest. (See also Appendix 2: Figure 3 and 8) 2.3 Personalization See part 4.2 2.4 Authorization A login to the frontend of a CMS requires a login and password. It is possible to create some user categories with specific rights for each one; e.g. the webmaster has access to the entire site or the secretary of the finance department only sees texts from that department. So it is possible to personalize the access rights for every user. (See also Appendix 2: Figure 7) 1 Prof. Dr. Petra Schubert © 2004 FHBB/DWI page 5 e-Business: [email protected] open source CMS [email protected] 2.5 Multi – Channel The multi-channel part of the CMS includes many services like sending SMS from the page and generating outputs (prints, PDF, XML). All different forms of output are generated from the same data in the database. 2.6 Maintenance The maintenance on several levels is important for content management systems. First frequent software updates need do be done (by the technical person) in order to guarantee functionality and security. But the different users also have to be managed, fix users problems, change access rights of some persons, etc. (See also Appendix 2: Figure 6) 2.7 Simple Use An advantage is that the
Load more

Recommended publications
  • User Office, Proposal Handling and Analysis Software
    NOBUGS2002/031 October 11, 2002 Session Key: PB-1 User office, proposal handling and analysis software Jörn Beckmann, Jürgen Neuhaus Technische Universität München ZWE FRM-II D-85747 Garching, Germany [email protected] At FRM-II the installation of a user office software is under consideration, supporting tasks like proposal handling, beam time allocation, data handling and report creation. Although there are several software systems in use at major facilities, most of them are not portable to other institutes. In this paper the requirements for a modular and extendable user office software are discussed with focus on security related aspects like how to prevent a denial of service attack on fully automated systems. A suitable way seems to be the creation of a web based application using Apache as webserver, MySQL as database system and PHP as scripting language. PRESENTED AT NOBUGS 2002 Gaithersburg, MD, U.S.A, November 3-5, 2002 1 Requirements of user office software At FRM-II a user office will be set up to deal with all aspects of business with guest scientists. The main part is the handling and review of proposals, allocation of beam time, data storage and retrieval, collection of experimental reports and creation of statistical reports about facility usage. These requirements make off-site access to the user office software necessary, raising some security concerns which will be addressed in chapter 2. The proposal and beam time allocation process is planned in a way that scientists draw up a short description of the experiment including a review of the scientific background and the impact results from the planned experiment might have.
    [Show full text]
  • TYPO3 Security Guide
    TYPO3 Security Guide Extension Key: doc_guide_security Language: en Version: 1.0.0 Keywords: security forEditors forAdmins forDevelopers forBeginners forIntermediates forAdvanced Copyright 2011, Documentation Team <[email protected]> This document is published under the Open Content License available from http://www.opencontent.org/opl.shtml The content of this document is related to TYPO3 - a GNU/GPL CMS/Framework available from www.typo3.org Official Documentation This document is included as part of the official TYPO3 documentation. It has been approved by the TYPO3 Documentation Team following a peer-review process. The reader should expect the information in this document to be accurate - please report discrepancies to the Documentation Team ([email protected]). Official documents are kept up-to-date to the best of the Documentation Team's abilities. Guide This document is a Guide. Guides are designed to familiarize a reader with a specific topic in order to provide a working knowledge of that particular process. Readers should peruse the guide from cover to cover in order to gain a practical overview of the process. Once completed, the Guide becomes a practical reference tool that a reader will refer to as needed. Guides offer advice on how best to achieve a given task. TYPO3 Security Guide - doc_guide_security TYPO3 Security Guide Table of Contents TYPO3 Security Guide............................1 Directory indexing........................................................12 Introduction...................................................................3
    [Show full text]
  • Open Source Basierte Virtuelle Forschungsumgebungen Für Projekte in Der Ökologischen Langzeitforschung
    Open Source basierte Virtuelle Forschungsumgebungen für Projekte in der ökologischen Langzeitforschung Das „Rapid L-TER VRE“ Baukastenkonzept zur schnellen und nachhaltigen Realisierung Von der Fakultät für Umwelt und Naturwissenschaften der Brandenburgischen Techni- schen Universität Cottbus – Senftenberg zur Erlangung des akademischen Grades eines Doktors der Ingenieurwissenschaften genehmigte Dissertation vorgelegt von Diplom-Umweltingenieur Mirko Filetti aus Offenbach, am Main (Hessen) Gutachter: apl. Prof. Dr.-Ing. habil. Frank Molkenthin Gutachter: Prof. Dr. rer. nat. habil. Albrecht Gnauck Gutachter: Prof. Dr. rer. nat. habil. Gerhard Wiegleb Tag der mündlichen Prüfung: 28.06.2018 Kurzfassung Virtuelle Forschungsumgebungen (engl. virtual research environments, im Folgenden als VRE bezeichnet), sind nach allgemeinem Verständnis Plattformen auf Basis von Informations- und Kommunikationstechnologien (engl. ICT) mit ganzheitlichem Ansatz, die das wissenschaftliche Arbeiten im Team und insbesondere dessen Kommunikation und Organisation unterstützen sollen. Sie haben zum Ziel, schneller und besser zu nachvollziehbaren Ergebnissen zu gelangen und Wissen persistent verfügbar zu machen. Derzeit existiert jedoch kein VRE-Software- Framework, das „out-of-the-box“ sofort einsatzfähig oder für alle Anforderungen geeignet wäre („one size fit them all“). Projekte in der ökologischen Langzeitforschung (engl. long-term ecological research, im Folgenden als L-TER bezeichnet) sind durch den Langzeitaspekt und Raumbezug in der Regel umfangreiche Projekte
    [Show full text]
  • TYPO3 / Wordpress / Drupal
    civi listen GmbH Schwedenstr. 15a 13357 Berlin jobs@civi listen.de www. civi listen.de Freelance Entwickler*in Frontend / Backend (m/w/d) TYPO3 / Wordpress / Drupal Was wir machen Wir sind die civi listen. Wir digitalisieren die Zivilgesellschaft. Unsere Kunden verbessern die Welt und wir sorgen dafür, dass sie dabei nichts aufhält. Dafür unterstützen wir seit 2018 gemeinnützige Organisationen mit praktischen Hilfestellungen digitaler und damit effizienter zu werden. CiviCRM ist dabei eine Lösung, die wir anbieten, um Beziehungen zwischen NGOs, Stiftungen und Vereinen zu ihren Stakeholdern und Zielgruppen verbessern – vom personalisierten Mailing bis zur Organisation von Events, Kampagnen und Fundraising. Wir entwickeln Auftritte, die gut aussehen und den richtigen Ton treffen. Wir helfen Herausforderungen und Prozesse smart und zuverlässig zu bewältigen. Wen wir suchen Wir wollen unsere Kunden jederzeit flexibel mit der besten Expertise unterstützen und glauben daran, dass Akteure der Zivilgesellschaft die besten Lösungen brauchen. Zur Unterstützung unseres Teams suchen wir zum nächstmöglichen Zeitpunkt eine*n erfahrene*n Entwickler*in TYPO3 / Wordpress / Drupal (m/w/d) civi listen GmbH Sitz der Gesellschaft: Berlin 030 692 090 200 Kopf frei für Hands on. Schwedenstr. 15 a Registergericht: Berlin-Charlottenburg, HRB 218551 B jobs@civi listen.de 13357 Berlin Geschäftsführer: Patrick Förg www. civi listen.de 1/4 Deine Aufgaben Wir erstellen für unsere CiviCRM-Kunden anspruchsvolle Internetauftritte und Spezialfunktionen mit TYPO3, Wordpress,
    [Show full text]
  • An Interdisciplinary Journal
    FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITA LISM FAST CAPITALISMFast Capitalism FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM ISSNFAST XXX-XXXX CAPITALISM FAST Volume 1 • Issue 1 • 2005 CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITA LISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITA LISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITA LISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITA LISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM FAST CAPITA LISM FAST CAPITALISM FAST CAPITALISM FAST CAPITALISM
    [Show full text]
  • Next Generation Web Scanning Presentation
    Next generation web scanning New Zealand: A case study First presented at KIWICON III 2009 By Andrew Horton aka urbanadventurer NZ Web Recon Goal: To scan all of New Zealand's web-space to see what's there. Requirements: – Targets – Scanning – Analysis Sounds easy, right? urbanadventurer (Andrew Horton) www.morningstarsecurity.com Targets urbanadventurer (Andrew Horton) www.morningstarsecurity.com Targets What does 'NZ web-space' mean? It could mean: •Geographically within NZ regardless of the TLD •The .nz TLD hosted anywhere •All of the above For this scan it means, IPs geographically within NZ urbanadventurer (Andrew Horton) www.morningstarsecurity.com Finding Targets We need creative methods to find targets urbanadventurer (Andrew Horton) www.morningstarsecurity.com DNS Zone Transfer urbanadventurer (Andrew Horton) www.morningstarsecurity.com Find IP addresses on IRC and by resolving lots of NZ websites 58.*.*.* 60.*.*.* 65.*.*.* 91.*.*.* 110.*.*.* 111.*.*.* 113.*.*.* 114.*.*.* 115.*.*.* 116.*.*.* 117.*.*.* 118.*.*.* 119.*.*.* 120.*.*.* 121.*.*.* 122.*.*.* 123.*.*.* 124.*.*.* 125.*.*.* 130.*.*.* 131.*.*.* 132.*.*.* 138.*.*.* 139.*.*.* 143.*.*.* 144.*.*.* 146.*.*.* 150.*.*.* 153.*.*.* 156.*.*.* 161.*.*.* 162.*.*.* 163.*.*.* 165.*.*.* 166.*.*.* 167.*.*.* 192.*.*.* 198.*.*.* 202.*.*.* 203.*.*.* 210.*.*.* 218.*.*.* 219.*.*.* 222.*.*.* 729,580,500 IPs. More than we want to try. urbanadventurer (Andrew Horton) www.morningstarsecurity.com IP address blocks in the IANA IPv4 Address Space Registry Prefix Designation Date Whois Status [1] -----
    [Show full text]
  • The Zope Developer's Guide (2.4 Edition)
    The Zope Developer's Guide (2.4 Edition) Chris McDonough, Michel Pelletier, Shane Hathaway Zope Developer's Guide (2.4 edition) Introduction 7 Chapter 1: Components and Interfaces 8 Zope Components 8 Python Interfaces 10 Why Use Interfaces? 10 Creating Interfaces 10 The Interface Model 12 Querying an Interface 12 Checking Implementation 13 Conclusion 14 Chapter 2: Object Publishing 15 Introduction 15 HTTP Publishing 15 15 URL Traversal 16 Traversal Interfaces 17 Publishable Object Requirements 17 Traversal Methods 17 Publishing Methods 18 HTTP Responses 19 Controlling Base HREF 19 Response Headers 20 Pre-Traversal Hook 20 Traversal and Acquisition 20 Traversal and Security 22 Basic Publisher Security 22 Zope Security 22 Environment Variables 23 Testing 23 Publishable Module 23 Calling the Published Object 24 Marshalling Arguments from the Request 24 Argument Conversion 24 Method Arguments 25 Record Arguments 26 Exceptions 27 2 Zope Developer's Guide (2.4 edition) Exceptions and Transactions 27 Manual Access to Request and Response 28 Other Network Protocols 29 FTP 29 WebDAV 30 Supporting Write Locking 30 XML-RPC 31 Summary 32 Chapter 3: Zope Products 33 Introduction 33 Development Process 33 Consider Alternatives 33 Starting with Interfaces 33 Implementing Interfaces 34 Building Product Classes 35 Base Classes 35 Acquisition.Implicit 35 Globals.Persistent 36 OFS.SimpleItem.Item 36 AccessControl.Role.RoleManager 37 OFS.ObjectManager 37 OFS.PropertyManager 37 Security Declarations 38 Summary 39 Registering Products 40 Product Initialization
    [Show full text]
  • Zope Documentation Release 5.3
    Zope Documentation Release 5.3 The Zope developer community Jul 31, 2021 Contents 1 What’s new in Zope 3 1.1 What’s new in Zope 5..........................................4 1.2 What’s new in Zope 4..........................................4 2 Installing Zope 11 2.1 Prerequisites............................................... 11 2.2 Installing Zope with zc.buildout .................................. 12 2.3 Installing Zope with pip ........................................ 13 2.4 Building the documentation with Sphinx ............................... 14 3 Configuring and Running Zope 15 3.1 Creating a Zope instance......................................... 16 3.2 Filesystem Permissions......................................... 17 3.3 Configuring Zope............................................. 17 3.4 Running Zope.............................................. 18 3.5 Running Zope (plone.recipe.zope2instance install)........................... 20 3.6 Logging In To Zope........................................... 21 3.7 Special access user accounts....................................... 22 3.8 Troubleshooting............................................. 22 3.9 Using alternative WSGI server software................................. 22 3.10 Debugging Zope applications under WSGI............................... 26 3.11 Zope configuration reference....................................... 27 4 Migrating between Zope versions 37 4.1 From Zope 2 to Zope 4 or 5....................................... 37 4.2 Migration from Zope 4 to Zope 5.0..................................
    [Show full text]
  • OSS Watch National Software Survey 2008
    OSS Watch National Software Survey 2008 Ramón Casero Cañas Acknowledgements Publication information The survey was prepared and the report written by Ramón This survey report is licensed under the Creative Commons Casero Cañas (OSS Watch), and edited by Ross Gardler and Attribution-ShareAlike 2.0 England & Wales licence. Elena Blanco (OSS Watch), and Pete Cooper. OSS Watch National Software Survey 2008 However, there are many people who helped to make it pos- Ramón Casero Cañas sible. We would like to thank the ICT directors of the FE and HE institutions, who took the time to respond to the survey First edition, published February 2009. and send feedback to us; Dr Ellen Helsper (Oxford Internet Institute) for her advice, academic input and support; Randy Metcalfe, former OSS Watch Service Manager, who set us with this task and was always a source of encouragement and support; Michael Fraser, former OSS Watch Director, for his comments; Gabriel Hanganu, Stuart Yeates and Rowan Wilson (OSS Watch) for their comments, envelope stuffing, corrections and so much more; Laura Marriott and Beverley McNichols for their data collection; Jean Davis and Sally Hard- ing for envelope stuffing; Barry Cornelius, Dominic Hargreaves, Charles Hutchings, Liz Masterman, Denise McDonough, Stuart Lee, Janet McKnight, Howard Noble, Mark Norman, Catrin Radcliffe and Peter Robinson for their comments about the online questionnaire; Judy McAuliffe, Tina Dick, Leslie Ferguson, Fran Jackson, Bruce Shakespeare, Jane Truby and Wendy Simmonds for their help with administration
    [Show full text]
  • Appendix a the Ten Commandments for Websites
    Appendix A The Ten Commandments for Websites Welcome to the appendixes! At this stage in your learning, you should have all the basic skills you require to build a high-quality website with insightful consideration given to aspects such as accessibility, search engine optimization, usability, and all the other concepts that web designers and developers think about on a daily basis. Hopefully with all the different elements covered in this book, you now have a solid understanding as to what goes into building a website (much more than code!). The main thing you should take from this book is that you don’t need to be an expert at everything but ensuring that you take the time to notice what’s out there and deciding what will best help your site are among the most important elements of the process. As you leave this book and go on to updating your website over time and perhaps learning new skills, always remember to be brave, take risks (through trial and error), and never feel that things are getting too hard. If you choose to learn skills that were only briefly mentioned in this book, like scripting, or to get involved in using content management systems and web software, go at a pace that you feel comfortable with. With that in mind, let’s go over the 10 most important messages I would personally recommend. After that, I’ll give you some useful resources like important websites for people learning to create for the Internet and handy software. Advice is something many professional designers and developers give out in spades after learning some harsh lessons from what their own bitter experiences.
    [Show full text]
  • The Drupal Decision
    The Drupal Decision Stephen Sanzo | Director of Marketing and Business Development | Isovera [email protected] www.isovera.com Agenda 6 Open Source 6 The Big Three 6 Why Drupal? 6 Overview 6 Features 6 Examples 6 Under the Hood 6 Questions (non-technical, please) Open Source Software “Let the code be available to all!” 6 Software that is available in source code form for which the source code and certain other rights normally reserved for copyright holders are provided under a software license that permits users to study, change, and improve the software. 6 Adoption of open-source software models has resulted in savings of about $60 billion per year to consumers. http://en.wikipedia.org/wiki/Open-source_software www.isovera.com Open Source Software However… Open source doesn't just mean access to the source code. The distribution terms of open-source software must comply criteria established by the Open Source Initiative. http://www.opensource.org/docs/osd www.isovera.com Open Source Software Free as in… Not this… www.isovera.com Open Source CMS Advantages for Open Source CMS 6 No licensing fees - allows you to obtain enterprise quality software at little to no cost 6 Vendor flexibility - you can choose whether or not you want to hire a vendor to help you customize, implement, and support it, or do this internally. If at any point along the way you decide you don’t like your vendor, you are free to find another. 6 Software flexibility – in many cases, proprietary software is slow to react to the markets needs.
    [Show full text]
  • CMS Matrix - Cmsmatrix.Org - the Content Management Comparison Tool
    CMS Matrix - cmsmatrix.org - The Content Management Comparison Tool http://www.cmsmatrix.org/matrix/cms-matrix Proud Member of The Compare Stuff Network Great Data, Ugly Sites CMS Matrix Hosting Matrix Discussion Links About Advertising FAQ USER: VISITOR Compare Search Return to Matrix Comparison <sitekit> CMS +CMS Content Management System eZ Publish eZ TikiWiki 1 Man CMS Mambo Drupal Joomla! Xaraya Bricolage Publish CMS/Groupware 4.6.1 6.10 1.5.10 1.1.5 1.10 1024 AJAX CMS 4.1.3 and 3.2 1Work 4.0.6 2F CMS Last Updated 12/16/2006 2/26/2009 1/11/2009 9/23/2009 8/20/2009 9/27/2009 1/31/2006 eZ Publish 2flex TikiWiki System Mambo Joomla! eZ Publish Xaraya Bricolage Drupal 6.10 CMS/Groupware 360 Web Manager Requirements 4.6.1 1.5.10 4.1.3 and 1.1.5 1.10 3.2 4Steps2Web 4.0.6 ABO.CMS Application Server Apache Apache CGI Other Other Apache Apache Absolut Engine CMS/news publishing 30EUR + system Open-Source Approximate Cost Free Free Free VAT per Free Free (Free) Academic Portal domain AccelSite CMS Database MySQL MySQL MySQL MySQL MySQL MySQL Postgres Accessify WCMS Open Open Open Open Open License Open Source Open Source AccuCMS Source Source Source Source Source Platform Platform Platform Platform Platform Platform Accura Site CMS Operating System *nix Only Independent Independent Independent Independent Independent Independent ACM Ariadne Content Manager Programming Language PHP PHP PHP PHP PHP PHP Perl acms Root Access Yes No No No No No Yes ActivePortail Shell Access Yes No No No No No Yes activeWeb contentserver Web Server Apache Apache
    [Show full text]