symphonycms / symphony-1.7

Symphony is a PHP & MySQL based CMS that utilises XML and XSLT as its core technologies.

Symphony CMS

• Version: 3.0.0
• Date: 27th March 2020
• Release notes
• Changelog
• Github repository
• MIT Licence

Contents

• Overview
• Server requirements
• Responsible Security Disclosure

Quick links

• Installing
• Updating from LTS
• Contributing
• Documentation TOC

Overview

Symphony is a PHP & MySQL based CMS that utilises XML and XSLT as its core technologies. This repository represents version 3.0.0 and is considered stable.

Useful places:

• The Symphony website
• The Symphony forum
• Symphony Extensions
• DEV chat room
• HELP chat room

Server requirements

• PHP 5.6 or 7.0-7.3
• PHP’s LibXML module, with the XSLT extension enabled (--with-xsl)
• MySQL 5.7 or above is recommended
• A webserver (known to be used with Apache, Litespeed, Nginx and Hiawatha)
• Apache’s mod_rewrite module or equivalent
• PHP’s built in json functions, which are enabled by default in PHP 5.2 and above; if they are missing, ensure PHP wasn’t compiled with --disable-json
• PHP’s zlib module
• PHP’s pdo_mysql module

Responsible Security Disclosure

Please follow the guideline for security bug disclosure.

symphony-1.7's Issues

Licence & Readme

Symphony 1.7 has been published here on Github under its original licence although the terms of service state:

By setting your repositories to be viewed publicly, you agree to allow others to view and fork your repositories.

Each file contains the following statement:

###
#
# Symphony web publishing system
#
# Copyright 2004 - 2006 Twenty One Degrees Pty. Ltd. This code cannot be
# modified or redistributed without permission.
#
# For terms of use please visit http://21degrees.com.au/products/symphony/terms/
#
###

The given link returns a 404 error as the 21 Degrees website now redirects to chaoticpattern.com.

@allen: There are certainly sites around that are still using version 1.7 so it would be nice if either the licence could be changed (MIT as the later versions of the system?) or at least be clarified. This would give users give the ability to publish their PHP 5.3 compatibility updates without fearing to break a licence.

However you decide to handle this, I'd like to suggest to replace the comment above with something like this (adding the the licence and terms to the readme):

/**
 * Symphony web publishing system
 * 
 * Copyright 2004–2006 Twenty One Degrees Pty. Ltd.
 *
 * @version 1.7
 * @licence [link to readme]
 */

What about moving Symphony 1.7 to the symphonycms organisation and retiring this account?

See this discussion in the forum: http://getsymphony.com/discuss/thread/94981/