Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/domain7/sym-cumulus
Symphony Cumulus Tag Cloud Ensemble
https://github.com/domain7/sym-cumulus
Last synced: 1 day ago
JSON representation
Symphony Cumulus Tag Cloud Ensemble
- Host: GitHub
- URL: https://github.com/domain7/sym-cumulus
- Owner: domain7
- License: mit
- Created: 2010-10-20T05:19:34.000Z (about 14 years ago)
- Default Branch: master
- Last Pushed: 2010-10-20T05:24:47.000Z (about 14 years ago)
- Last Synced: 2024-12-30T12:45:36.110Z (11 days ago)
- Language: PHP
- Homepage: http://www.domain7.com/
- Size: 1.51 MB
- Stars: 1
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.markdown
Awesome Lists containing this project
README
# Symphony 2 #
- Version: 2.1.1
- Date: 18th Aug 2010
- Release Notes:
- Github Repository:## Synopsis
Symphony is a `PHP` & `MySQL` based CMS that utilises `XML` and `XSLT` as
its core technologies. This repository represents version "2.1.1" and is
considered stable.Visit the forum at
### Symphony Server Requirements
- PHP 5.2 or above
- PHP's LibXML module, with the XSLT extension enabled (--with-xsl)
- MySQL 4.1 or above
- An Apache or Litespeed webserver
- Apache's mod_rewrite module or equivalent## Updating From an Older Version
### Important Information
As of version `2.1`, Symphony stores passwords using the more secure
[SHA1](http://php.net/sha1) algorithm (previous versions used MD5).
When updating to 2.1, the primary user's login password will be reset
(the new password will be displayed by the updater—please note it).
**Please also note that all other users' passwords will no longer be valid
and will require a manual reset through Symphony's forgotten password feature.**
Alternatively, as an administrator, you can also change your users'
passwords on their behalf.Version `2.0.5` introduced multiple includable elements, in the Data Source
Editor, for a single field. After updating from `2.0.5` or lower, the DS
editor will seem to "forget" about any `Textarea` fields selected when you
are editing existing Data Sources. After updating, you must ensure you
re-select them before saving. Note, this will only effect Data Sources that
you edit and were created prior to `2.0.5`. Until that point, the field will
still be included in any front-end XML### Via Git
### Important Information
As of version 2.1, we are now using [GitHub's organisations feature](http://github.com/blog/674-introducing-organizations). As a result, all submodules—as well as the main Symphony 2 repo—are forks owned by the
[Symphony CMS organisation](http://github.com/symphonycms/). To fully update your
git based installation, please edit your `.git/config` and the `.git/config`
of all core extensions (`debugdevkit`, `profiledevkit`, `markdown`, `maintenance_mode`,
`selectbox_link_field`, `jit_image_manipulation` and `export_ensemble`) and change
the URL of the remote repo from `symphony` or `pointybeard` to be `symphonycms`.For example:
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = git://github.com/pointybeard/markdown.gitChange `git://github.com/pointybeard/markdown.git` to `git://github.com/symphonycms/markdown.git`
1. Pull from the master branch at `git://github.com/symphonycms/symphony-2.git`
2. Use the following command to get Extensions up to date:
git submodule init
git submodule update3. If updating from a version older than `2.0.5`, enable [Debug DevKit](http://github.com/symphonycms/debugdevkit/tree/master) and [Profile DevKit](http://github.com/symphonycms/profiledevkit/tree/master) extensions.
3. Go to `http://yoursite.com/update.php` to complete the update process.
4. You and your website are now in the future. Buy yourself a silver jumpsuit.
### Via the old fashioned way
Follow the instructions below if you are updating from Symphony version 2.0 (not from Git)
**Note:** As of 2.0.6, there is no longer a need to backup `/symphony/.htaccess`.
1. Upload `/symphony`, `index.php` & `update.php`, replacing what is already on your server.
2. If you are updating from a version older than 2.0.5, download and install the Debug DevKit and Profile DevKit:
- [Debug DevKit](http://github.com/symphonycms/debugdevkit/tree/master)
- [Profile DevKit](http://github.com/symphonycms/profiledevkit/tree/master)3. Go to `http://yoursite.com/update.php` to complete the update process.
4. Call a friend and brag that your copy of Symphony is newer than theirs.
## Installing Symphony
### Via Git
1. Clone the git repository to the location you desire using:
git clone git://github.com/symphonycms/symphony-2.git
Should you wish to make contributions back to the project, fork the master tree rather than cloning, and issue pull requests via github.The following repositories are included as submodules:
- [Markdown](http://github.com/symphonycms/markdown)
- [Maintenance Mode](http://github.com/symphonycms/maintenance_mode)
- [Select Box Link Field](http://github.com/symphonycms/selectbox_link_field)
- [JIT Image Manipulation](http://github.com/symphonycms/jit_image_manipulation)
- [Export Ensemble](http://github.com/symphonycms/export_ensemble)
- [Debug DevKit](http://github.com/symphonycms/debugdevkit/tree/master)
- [Profile DevKit](http://github.com/symphonycms/profiledevkit/tree/master)3. Run the following command to ensure the submodules are cloned:
git submodule update --init
4. _(Optional)_ If you would like the [default ensemble](http://github.com/symphonycms/workspace/tree) installed as well,
you will need to use the following command from within the Symphony 2 folder you just created:git clone git://github.com/symphonycms/workspace.git
5. Point your web browser at and provide
details for establishing a database connection and about your server environment.6. Chuckle villainously and tap your fingertips together (or pet a cat) as your installation completes.
### Via the old fashioned way
**Note: You can leave `/workspace` out if you do not want the default theme.**
1. This step assumes you downloaded a zip archive from the [Symphony website](http://symphony-cms.com).
Upload the following files and directories to the root directory of your website:- index.php
- install.php
- install.sql
- /symphony
- /workspace
- /extensions2. Point your web browser at and provide
details for establishing a database connection and about your server environment.3. Pose like you're being filmed for a dramatic close-up while your installation completes.
## Security
**Secure Production Sites: Change permissions and remove installer files.**
1. For a smooth install process, change permissions for the `root` and `workspace` directories.
cd /your/site/root
chmod -R 777 workspace2. Once successfully installed, change permissions as per your server preferences, E.G.
chmod 755 .
3. Remove installer files (unless you're fine with revealing all your trade secrets):
rm install.php install.sql workspace/install.sql update.php
4. Dance like it's 1894!