tonyair
/
silverstripe-cms
mirror of https://github.com/silverstripe/silverstripe-cms
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
3,539 Commits 28 Branches 397 Tags 24 MiB
PHP 73.3%
JavaScript 20%
Gherkin 4%
Scheme 2.1%
SCSS 0.6%
Go to file
Ingo Schommer b872714082 Added installer link to readme 2013-04-02 01:52:17 +02:00
_config FIX Dont refer to framework module in config rules 2012-08-28 15:46:33 +12:00
code BUG SilverStripeNavigator shows wrong message. 2013-03-18 15:57:20 +02:00
css Make message always visible at the top of the page 2013-03-18 16:28:28 +02:00
images BUG Visual cue that URLSegment is updating 2012-08-17 03:05:39 -05:00
javascript FIX Unset "underneath page" title when switching to "top" in "add page" 2013-03-25 23:41:21 +01:00
lang Updated translations 2013-02-26 13:27:07 +01:00
scss Make message always visible at the top of the page 2013-03-18 16:29:10 +02:00
tasks Removed direct sprintf() usage from _t() calls 2012-12-21 11:18:18 +01:00
templates Moving "edit tree" button next to "add new" (fixes #8119) 2013-01-16 00:19:56 +01:00
tests Simplified travis builds (external setup scripts) 2013-03-28 21:15:11 +01:00
thirdparty/multifile Partially revert 90a154c888 (on JS files) 2012-10-08 16:44:28 +02:00
.gitignore MINOR: gitignore of mac .DS_Store files 2011-09-28 11:44:30 +13:00
.htaccess BUGFIX Disallow web access to cms/silverstripe_version to avoid information leakage 2010-12-09 22:50:52 +00:00
.travis.yml More straightfoward travis include/exclude 2013-03-28 22:54:32 +01:00
CONTRIBUTING.md Added github-compatible contributing notes 2012-10-11 17:18:07 +02:00
README.md Added installer link to readme 2013-04-02 01:52:17 +02:00
_config.php BUGFIX: Make CMSes Director rules use new yaml config fragments system 2012-05-19 14:43:10 +12:00
composer.json Merge changes for 3.0.3 release into 3.0 2012-11-26 11:38:12 +13:00
config.rb Make compass not include line number comments 2012-07-23 22:15:42 +12:00
silverstripe_version API CHANGE silverstripe_version file now contains the plain version number, rather than an SVN path 2012-02-01 18:42:13 +01:00
web.config BUGFIX Disallow web access to cms/silverstripe_version to avoid information leakage 2010-12-09 22:50:52 +00:00

README.md

SilverStripe CMS

Build Status

PHP5 Content Management System (CMS), see http://silverstripe.org. Requires the framework module and a silverstripe-installer base project.

Installation

See installation on different platforms, and installation from source.

Bugtracker

Bugs are tracked on github.com. Please read our issue reporting guidelines.

Development and Contribution

If you would like to make changes to the SilverStripe core codebase, we have an extensive guide to contributing code.

Links

License

Copyright (c) 2007-2013, SilverStripe Limited - www.silverstripe.com
All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

    * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the 
      documentation and/or other materials provided with the distribution.
    * Neither the name of SilverStripe nor the names of its contributors may be used to endorse or promote products derived from this software 
      without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE 
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE 
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY 
OF SUCH DAMAGE.