tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-10-22 14:05:37 +02:00
Code Issues Projects Releases Wiki Activity

DOCS 2.4 : disables broken external links

Browse Source
This commit is contained in:
David Alexander 2016-01-16 21:14:48 +13:00
parent df1a32fba7
commit 613836de51
42 changed files with 181 additions and 181 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/en/changelogs/2.2.0.md
View File

@ -22,7 +22,7 @@ js/css changes.
// after
<div class="Actions">
See http://open.silverstripe.com/changeset/43562
See `http://open.silverstripe.com/changeset/43562`
### Form Security Token
@ -142,7 +142,7 @@ Sitemap.php
* Translatable, for multilingual content
* New third party libraries
* PHP OpenID (http://openidenabled.com/php-openid/)
* Browscap (http://garetjax.info/projects/browscap/)
* Browscap (http://browscap.org/)
* Plotr (http://www.solutoire.com/plotr/)
* SWFUpload (http://profandesign.se/swfupload/)
* Improved classes

20
docs/en/changelogs/2.3.0.md
View File

@ -21,7 +21,7 @@ Basic auth isn't enabled by default on test sites. If you need this, put this i
### /silverstripe and /cms no longer work as aliases to /admin
Removed certain URL aliases for CMS interface to allow for common page URLs like "silverstripe" or "cms". Please use
/admin as the main URL to access the CMS. See http://open.silverstripe.com/ticket/3267
/admin as the main URL to access the CMS. See `http://open.silverstripe.com/ticket/3267`
### SiteTree Access tab now lets you select multiple groups
@ -29,7 +29,7 @@ In order to do this, `SiteTree->ViewersGroup` and `SiteTree->EditorsGroup` have
to many_many relations.
Your group-assignements for "Who can view this page" and "Who can edit this page" should be automatically migrated upon
calling `dev/build`. See [#2847](http://open.silverstripe.com/ticket/2847)
calling `dev/build`. See [#2847] `http://open.silverstripe.com/ticket/2847`
### Newsletter moved into new module
@ -47,7 +47,7 @@ If you **don't** require the functionality, it's safe to delete these database t
#### auth_openid removed from default installation
The auth_openid module has been removed from default installation. Please install the module separately from
[silverstripe.org](http://silverstripe.org/auth-openid-module/)
[silverstripe.org] `http://silverstripe.org/auth-openid-module/`
### GenericDataAdmin and RelatedDataEditor moved into new module
@ -87,7 +87,7 @@ If you **don't** require the User Defined Form functionality, it's safe to delet
### PostBackup
PostBackup has been moved into a module. See [postbackup
module](http://open.silverstripe.com/browser/modules/postbackup/trunk).
module] `http://open.silverstripe.com/browser/modules/postbackup/trunk`.
### /db/build/?flush=1 is now called /dev/build
@ -134,7 +134,7 @@ To this:
### Decorators
* Renamed DataObjectDecorator->extraDBFields() to extraStatics() (see
[r65065](http://open.silverstripe.com/changeset/65065))
[r65065] `http://open.silverstripe.com/changeset/65065`)
* DataObjectDecorator->updateCMSFields() is now called from DataObject->getCMSFields(), instead of only SiteTree
instances
@ -162,7 +162,7 @@ FormField::performDisabledTransformation() must return new form fields, e.g., cl
* '''$Top''' in templates has changed its behaviour; if you call $Top from inside a template that is rendered
separately (eg, a Form template), it will point to the top element of that template execution (in this case, the Form
object) rather than the top element of the outermost template (which would presumably be the page in question). This
was a bug that we have fixed, but some people may rely on it. See http://open.silverstripe.com/ticket/2781
was a bug that we have fixed, but some people may rely on it. See `http://open.silverstripe.com/ticket/2781`
* A `<legend>` element has been added before any `<fieldset>` in all SilverStripe forms. SearchForm.ss and Form.ss are
where it has been added. This now validates the form HTML for W3C compliance. Please verify that your forms visually
@ -218,7 +218,7 @@ _config.php:
:::php
Validator::set_javascript_validation_handler('none');
See http://open.silverstripe.com/changeset/69688
See `http://open.silverstripe.com/changeset/69688`
## New Features
@ -1067,9 +1067,9 @@ See http://open.silverstripe.com/changeset/69688
* ![rev:65827] Added error messages to flash uploader panel, to be consistent with the image uploader one
* ![rev:65582] Using actual classname in DataObjectSet->debug()
* ![rev:65581] Added unit tests for FieldSet->insertBefore()/insertAfter()
* ![rev:65513] Using currently used content languages for options in the TinyMCE spellchecker (see http://open.silverstripe.com/ticket/2498#comment:2)
* ![rev:65513] Using currently used content languages for options in the TinyMCE spellchecker (see `http://open.silverstripe.com/ticket/2498#comment:2`)
* ![rev:65508] Added language tables for tinymce_ssbuttons Plugin, incl. German translation
* ![rev:65495] Calling UpgradeSiteTreePermissionSchemaTask from SiteTree->requireDefaultRecords as a temporary workaround for missing migration infrastructure. This means that upgrading the schema for 2.3 can be done without manual task triggers, just the usual dev/build (see http://open.silverstripe.com/ticket/2847#comment:4)
* ![rev:65495] Calling UpgradeSiteTreePermissionSchemaTask from SiteTree->requireDefaultRecords as a temporary workaround for missing migration infrastructure. This means that upgrading the schema for 2.3 can be done without manual task triggers, just the usual dev/build (see `http://open.silverstripe.com/ticket/2847#comment:4`)
* ![rev:65494] Added DatabaseTest
* ![rev:65464] Better CLI output for browsing dev/tests
* ![rev:65463] Allowing strings instead of arrays in ModelAdmin::$managed_models to make it less error-prone for beginners
@ -2131,4 +2131,4 @@ See http://open.silverstripe.com/changeset/69688
* ![rev:59897] r52080, r52101, r52102 (merged from branches/roa)
* ![rev:59890] r52079 (merged from branches/roa)
* ![rev:59876] Merged [rev:46959]: ComplexTableField.ss now includes server-generated values in summary row cells.
* ![rev:59875] Merged [rev:46289]: Spaces in SCRIPT_FILENAME are now replaced with underscores.
* ![rev:59875] Merged [rev:46289]: Spaces in SCRIPT_FILENAME are now replaced with underscores.

2
docs/en/changelogs/2.3.2.md
View File

@ -25,7 +25,7 @@ They need to be changed to the following (respectively):
Here's an example of how the default Blackcandy theme was changed:
[http://open.silverstripe.org/changeset/75917/themes/blackcandy/branches/2.3/blackcandy/css/typography.css](http://open.silverstripe.org/changeset/75917/themes/blackcandy/branches/2.3/blackcandy/css/typography.css)
`http://open.silverstripe.org/changeset/75917/themes/blackcandy/branches/2.3/blackcandy/css/typography.css`
#### Translatable Datamodel

22
docs/en/changelogs/2.4.0.md
View File

@ -63,25 +63,25 @@ are going to be removed for the next major release.
| Class name | | Comment |
| ---------- | | ------- |
| `AjaxFormAction` | | |
| `BankAccountField` | | moved to [formfields_nz](http://open.silverstripe.org/browser/modules/formfields_nz) module |
| `CalendarDateField` | | use `DateField` with ''setConfig('showcalendar', true)'', moved to [legacydatetimefields](http://open.silverstripe.org/browser/modules/legacydatetimefields/trunk) module |
| `CompositeDateField`, `DMYDateField` | | use `DateField` with ''setConfig('dmyfields', true)'', moved to [legacydatetimefields](http://open.silverstripe.org/browser/modules/legacydatetimefields/trunk) module |
| `BankAccountField` | | moved to [formfields_nz] `http://open.silverstripe.org/browser/modules/formfields_nz` module |
| `CalendarDateField` | | use `DateField` with ''setConfig('showcalendar', true)'', moved to [legacydatetimefields] `http://open.silverstripe.org/browser/modules/legacydatetimefields/trunk` module |
| `CompositeDateField`, `DMYDateField` | | use `DateField` with ''setConfig('dmyfields', true)'', moved to [legacydatetimefields] `http://open.silverstripe.org/browser/modules/legacydatetimefields/trunk` module |
| `ConfirmedFormAction` | | |
| `DMYDateField` | | |
| `DropdownTimeField` | | use `TimeField` with ''setConfig('showdropdown', true)'', moved to [legacydatetimefields](http://open.silverstripe.org/browser/modules/legacydatetimefields/trunk) module |
| `DropdownTimeField` | | use `TimeField` with ''setConfig('showdropdown', true)'', moved to [legacydatetimefields] `http://open.silverstripe.org/browser/modules/legacydatetimefields/trunk` module |
| `Email_Template` | | use `Email` instead |
| `GhostPage` | | |
| `GSTNumberField` | | moved to [formfields_nz](http://open.silverstripe.org/browser/modules/formfields_nz) module |
| `GSTNumberField` | | moved to [formfields_nz] `http://open.silverstripe.org/browser/modules/formfields_nz` module |
| `HiddenFieldGroup` | | |
| `PDODatabase` | | |
| `PermissionDropdownField` | | |
| `PopupDateTimeField` | | use `DatetimeField`, moved to [legacydatetimefields](http://open.silverstripe.org/browser/modules/legacydatetimefields/trunk) module |
| `PopupDateTimeField` | | use `DatetimeField`, moved to [legacydatetimefields] `http://open.silverstripe.org/browser/modules/legacydatetimefields/trunk` module |
| `ReportField` | | |
| `TypeDropdown` | | |
Some date/time field implementations were completely refactored, and their old implementations moved to the
[legacydatetimefields](http://open.silverstripe.org/browser/modules/legacydatetimefields/trunk) module:
[legacydatetimefields] `http://open.silverstripe.org/browser/modules/legacydatetimefields/trunk` module:
| Class name | | Comment |
| ---------- | |------- |
@ -159,7 +159,7 @@ completely drop a database.
### Registering reports through SS_Report::register()
Removed `ReportAdmin->getReportClassNames()` in favour of `SS_Report::register()` to add custom reports to the CMS
(see [r98175](http://open.silverstripe.org/changeset/98175), [r98215](http://open.silverstripe.org/changeset/98215))
(see [r98175] `http://open.silverstripe.org/changeset/98175`, [r98215] `http://open.silverstripe.org/changeset/98215`)
:::php
// in your _config file
@ -227,7 +227,7 @@ TinyMCE entities back into UTF8 for database storage.
The MySQL character set for SilverStripe used to be the database default (often "latin1", sometimes "utf8"). While all
textual database columns created by SilverStripe have been storing their content as "utf8" already in earlier releases,
MySQL fulltext search might not return the desired results with special characters (see
[#3582](http://open.silverstripe.org/ticket/3582)).
[#3582] `http://open.silverstripe.org/ticket/3582`).
For new installations with a MySQL database backend, this will be set automatically to "utf8" by the installer in
@ -431,7 +431,7 @@ from the EditableFormField table.
* [rev:96792] Added new onRenameLinkAsset() handler to static publishing for better link rewriting. (from r89014)
* [rev:96778] Files and images section warns if you are deleting a file that is linked to
* [rev:96752] Recognise HTTP_X_FORWARDED_HOST header and use that in place of HTTP_HOST (from r93148)
* [rev:96668] Change to TreeDropdownField, giving it filtering behaviour as described in ticket http://open.silverstripe.org/ticket/3007 . Its disabled by default for legacy compatibility, but enabled for HtmlEditorField so that link editor is filterable for local links, via an extra boolean parameter on TreeDowndownField.
* [rev:96668] Change to TreeDropdownField, giving it filtering behaviour as described in ticket `http://open.silverstripe.org/ticket/3007` . Its disabled by default for legacy compatibility, but enabled for HtmlEditorField so that link editor is filterable for local links, via an extra boolean parameter on TreeDowndownField.
* [rev:96440] Add onLoad callback handler CMSLoadFunctions
* [rev:96049] Added Date::Rfc3339() for returning an RFC 3339 valid date format (from r96010)
* [rev:95418] added delete all link to page comments. Patch via #4427. Thanks walec51
@ -857,4 +857,4 @@ from the EditableFormField table.
* [rev:98944] testing framework needs to be reset to a clean state after each test: now also nested urls and redirection state will be reverted
* [rev:98897] Fixed strpos() check in BASE_URL check
* [rev:98895] Installer now opens if mod_rewrite is disabled. Using index.php instead of rewriting the URL didn't quite work with the new BASE_URL, so we need to take this case into account as well
* [rev:98869]
* [rev:98869]

12
docs/en/changelogs/2.4.1.md
View File

@ -15,12 +15,12 @@
## Upgrading
See [API Changes](http://open.silverstripe.org/wiki/ChangeLog/2.4.1-rc1?version=2#APIChanges).
See [API Changes] `http://open.silverstripe.org/wiki/ChangeLog/2.4.1-rc1?version=2#APIChanges`.
### Security: File->setName() and File->Filename handling
Setting properties on *File* and *Image* are not reflected on the filesystem until *write()* is called. This was a
necessary change to fix a security vulnerability around File->setName() and file extension validation. This
vulnerability requires a user to be logged-in to the CMS (see [#5693](http://open.silverstripe.org/ticket/5693)).
vulnerability requires a user to be logged-in to the CMS (see [#5693] `http://open.silverstripe.org/ticket/5693`).
This means that CMS users with access to "Files & Images" can no longer rename uploaded files to invalid extensions in
2.4.1. In SilverStripe 2.3.8, this restriction only applies when *AssetAdmin::$apply_restrictions_to_admin* is set to
@ -79,7 +79,7 @@ modules and folders you might have created in your own project.
Fixed password encryption when saving members through the "Add Member" dialog in the "Security" admin. The saving
process was disregarding password encyrption and saving them as plaintext
([#5772](http://open.silverstripe.org/ticket/5772)). The issue was introduced in 2.4.0 - if you have created any new
([#5772] `http://open.silverstripe.org/ticket/5772`). The issue was introduced in 2.4.0 - if you have created any new
members through "Add Member" since then (not the inline member table), please re-encrypt all existing passwords using
this task:
@ -118,7 +118,7 @@ The new behaviour has three states:
* NULL: Don't affect the outcome
To clarify: Leaving existing decorators unchanged might mean that you allow actions that were previously denied (See
[r104669](http://open.silverstripe.org/changeset/104669)).
[r104669] `http://open.silverstripe.org/changeset/104669`).
// In mysite/_config.php
:::php
@ -153,7 +153,7 @@ To clarify: Leaving existing decorators unchanged might mean that you allow acti
This feature was disabled for a while, and has now been removed from the source tree as well. Please please use
thirdparty modules instead, e.g. "[silverstripe-pixlr](http://github.com/nyeholt/silverstripe-pixlr)"
([r104987](http://open.silverstripe.org/changeset/104987)).
([r104987] `http://open.silverstripe.org/changeset/104987`).
### URL Transliteration
@ -493,4 +493,4 @@ existing pages when their title is changed.
* [rev:104667] Added explicit bash handler to sake
* [rev:104442] Multi-use redemption page created
<code>./sscreatechangelog --version 2.4.1 --branch branches/2.4 --stopbranch tags/2.4.0</code>
<code>./sscreatechangelog --version 2.4.1 --branch branches/2.4 --stopbranch tags/2.4.0</code>

4
docs/en/changelogs/2.4.3.md
View File

@ -16,7 +16,7 @@ Your development environment, or production web host may be running PHP as FastC
there is a regression in 2.4.3 which will break your site. There are two ways to resolve this problem:
- Don't upgrade to 2.4.3 for now, until 2.4.4 is released
- Patch the assets/.htaccess file like this: http://open.silverstripe.org/changeset/113809
- Patch the assets/.htaccess file like this: `http://open.silverstripe.org/changeset/113809`
This does **NOT** affect IIS, or other web servers that don't understand .htaccess files.
@ -347,4 +347,4 @@ You can manually enable security tokens, either globally or for a specific form.
* [rev:111040] API-CHANGE: remove include which is not required.
* [rev:111038] ENHACENEMENT: Change behaviour of the !MenufestBuilder to use spl_autoload_register instead of traditional __autoload.
<code>sscreatechangelog --version 2.4.3 --branch branches/2.4 --stopbranch tags/2.4.2</code>
<code>sscreatechangelog --version 2.4.3 --branch branches/2.4 --stopbranch tags/2.4.2</code>

52
docs/en/changelogs/2.4.4.md
View File

@ -20,7 +20,7 @@ There is a bug in 2.4.4 which breaks open_basedir restriction.
The issue has been fixed in the development 2.4 branch, but you'll need to patch your existing copy of SilverStripe
2.4.4 if this affects you. The error usually occurs when you try logging into the CMS.
It can be fixed by patching your working copy with this change: http://open.silverstripe.org/changeset/115314
It can be fixed by patching your working copy with this change: `http://open.silverstripe.org/changeset/115314`
### Security: SQL information disclosure in MySQLDatabase
@ -47,8 +47,8 @@ Andrew Lord, Nathaniel McHugh
#### Patches
* trunk: http://open.silverstripe.org/changeset/114782
* 2.4: http://open.silverstripe.org/changeset/114783
* trunk: `http://open.silverstripe.org/changeset/114782`
* 2.4: `http://open.silverstripe.org/changeset/114783`
### Security: XSS in controller handling for missing actions
@ -85,8 +85,8 @@ Tim Suter, Andrew Horton (http://security-assessment.com)
#### Patches
* trunk: http://open.silverstripe.org/changeset/114444
* 2.4: http://open.silverstripe.org/changeset/114751
* trunk: `http://open.silverstripe.org/changeset/114444`
* 2.4: `http://open.silverstripe.org/changeset/114751`
### Security: SQL injection with Translatable extension enabled
@ -118,9 +118,9 @@ Pavol Ondras
#### Patches
* trunk: http://open.silverstripe.org/changeset/114515
* 2.4: http://open.silverstripe.org/changeset/114516
* 2.3: http://open.silverstripe.org/changeset/114517
* trunk: `http://open.silverstripe.org/changeset/114515`
* 2.4: `http://open.silverstripe.org/changeset/114516`
* 2.3: `http://open.silverstripe.org/changeset/114517`
### Security: Version number information disclosure
@ -134,7 +134,7 @@ The files are:
sapphire/silverstripe_version
cms/silverstripe_version
See http://open.silverstripe.org/ticket/5031
See `http://open.silverstripe.org/ticket/5031`
See http://secunia.com/advisories/42346/
#### Solution
@ -151,9 +151,9 @@ Robert Mac Neil
#### Patches
* trunk: http://open.silverstripe.org/changeset/114774 http://open.silverstripe.org/changeset/114770
* 2.4: http://open.silverstripe.org/changeset/114774 http://open.silverstripe.org/changeset/114771
* 2.3: http://open.silverstripe.org/changeset/114776 http://open.silverstripe.org/changeset/114772
* trunk: `http://open.silverstripe.org/changeset/114774` `http://open.silverstripe.org/changeset/114770`
* 2.4: `http://open.silverstripe.org/changeset/114774` `http://open.silverstripe.org/changeset/114771`
* 2.3: `http://open.silverstripe.org/changeset/114776` `http://open.silverstripe.org/changeset/114772`
### Security: Weak entropy in tokens for CSRF protection, autologin, "forgot password" emails and password salts
@ -185,13 +185,13 @@ Andrew Horton (http://security-assessment.com)
#### Patches
* trunk: http://open.silverstripe.org/changeset/114497 http://open.silverstripe.org/changeset/114498
http://open.silverstripe.org/changeset/114503 http://open.silverstripe.org/changeset/114504
http://open.silverstripe.org/changeset/114505
* 2.4: http://open.silverstripe.org/changeset/114499 http://open.silverstripe.org/changeset/114500
http://open.silverstripe.org/changeset/114506 http://open.silverstripe.org/changeset/114507
* 2.3: http://open.silverstripe.org/changeset/114501 http://open.silverstripe.org/changeset/114502
http://open.silverstripe.org/changeset/114509
* trunk: `http://open.silverstripe.org/changeset/114497` `http://open.silverstripe.org/changeset/114498`
`http://open.silverstripe.org/changeset/114503` `http://open.silverstripe.org/changeset/114504`
`http://open.silverstripe.org/changeset/114505`
* 2.4: `http://open.silverstripe.org/changeset/114499` `http://open.silverstripe.org/changeset/114500`
`http://open.silverstripe.org/changeset/114506` `http://open.silverstripe.org/changeset/114507`
* 2.3: `http://open.silverstripe.org/changeset/114501` `http://open.silverstripe.org/changeset/114502`
`http://open.silverstripe.org/changeset/114509`
### Security: HTTP referer leakage on Security/changepassword
@ -227,9 +227,9 @@ Andrew Lord
#### Patches
* trunk: http://open.silverstripe.org/changeset/114758
* 2.4: http://open.silverstripe.org/changeset/114760
* 2.3: http://open.silverstripe.org/changeset/114763
* trunk: `http://open.silverstripe.org/changeset/114758`
* 2.4: `http://open.silverstripe.org/changeset/114760`
* 2.3: `http://open.silverstripe.org/changeset/114763`
### Security: CSRF protection bypassed when handling form action requests through controller
@ -267,9 +267,9 @@ Ingo Schommer
#### Patches
* trunk: http://open.silverstripe.org/changeset/115182 http://open.silverstripe.org/changeset/115185
* 2.4: http://open.silverstripe.org/changeset/115189 http://open.silverstripe.org/changeset/115188
* 2.3: http://open.silverstripe.org/changeset/115200 http://open.silverstripe.org/changeset/115191
* trunk: `http://open.silverstripe.org/changeset/115182` `http://open.silverstripe.org/changeset/115185`
* 2.4: `http://open.silverstripe.org/changeset/115189` `http://open.silverstripe.org/changeset/115188`
* 2.3: `http://open.silverstripe.org/changeset/115200` `http://open.silverstripe.org/changeset/115191`
## Changelog
@ -361,4 +361,4 @@ Ingo Schommer
### Other
* [rev:114464] FIX: Revert last commit
* [rev:114463] FIX: Revert last commit
* [rev:114463] FIX: Revert last commit

12
docs/en/changelogs/beta/2.4.0-beta1.md
View File

@ -80,7 +80,7 @@
* [rev:96792] Added new onRenameLinkAsset() handler to static publishing for better link rewriting. (from r89014)
* [rev:96778] Files and images section warns if you are deleting a file that is linked to
* [rev:96752] Recognise HTTP_X_FORWARDED_HOST header and use that in place of HTTP_HOST (from r93148)
* [rev:96668] Change to TreeDropdownField, giving it filtering behaviour as described in ticket http://open.silverstripe.org/ticket/3007 . Its disabled by default for legacy compatibility, but enabled for HtmlEditorField so that link editor is filterable for local links, via an extra boolean parameter on TreeDowndownField.
* [rev:96668] Change to TreeDropdownField, giving it filtering behaviour as described in ticket `http://open.silverstripe.org/ticket/3007` . Its disabled by default for legacy compatibility, but enabled for HtmlEditorField so that link editor is filterable for local links, via an extra boolean parameter on TreeDowndownField.
* [rev:96440] Add onLoad callback handler CMSLoadFunctions
* [rev:96049] Added Date::Rfc3339() for returning an RFC 3339 valid date format (from r96010)
* [rev:95418] added delete all link to page comments. Patch via #4427. Thanks walec51
@ -222,7 +222,7 @@
* [rev:97980] #5009: Removed inappropriate field-detection change on multienums with no default
* [rev:97937] missing comma
* [rev:97935] can't upload swf file in admin/assets (open ticket #4999)
* [rev:97926] remove the possibility that Director::isDev() could be recursively called when putting isDev=1 in $_GET, addressed in ticket #4978 (http://open.silverstripe.org/ticket/4978)
* [rev:97926] remove the possibility that Director::isDev() could be recursively called when putting isDev=1 in $_GET, addressed in ticket #4978 (`http://open.silverstripe.org/ticket/4978`)
* [rev:97912] Allowing translations of VirtualPage by not copying over original Locale property (see #5000)
* [rev:97911] If a Group doesn't have any specific TRANSLATE_`<locale>` edit rights, but has general CMS access (CMS_ACCESS_CMSMain, CMS_ACCESS_LeftAndMain, ADMIN), then assign TRANSLATE_ALL permissions as a default. Necessary to avoid locking out CMS editors from their default language (see #4940 and 4941)
* [rev:97909] Don't let a user's theme break the CMS.
@ -235,7 +235,7 @@
* [rev:97755] add custom search function, so the search catches also the Titles (search uses DataObject::get, which bypasses the getMenuTitle function)
* [rev:97746] allow only 2 and 4 digit years.
* [rev:97731] Use BASE_PATH and BASE_URL instead of data from $_SERVER.
* [rev:97730] fix front-end validation for DYMCalendarDateField, addressed in open ticket #4967(http://open.silverstripe.org/ticket/4967).
* [rev:97730] fix front-end validation for DYMCalendarDateField, addressed in open ticket #4967(`http://open.silverstripe.org/ticket/4967`).
* [rev:97728] Don't rely on the current working directory for any file access; use BASE_PATH.
* [rev:97727] Don't rely on the current directory for any logic.
* [rev:97673] the anchor dropdown now works in IE. Also fixes other anchor-related problems as described in ticket #4961
@ -405,8 +405,8 @@
* [rev:94002] fix some missing langs/en.js loading.
* [rev:93984] add proper language link broken
* [rev:93965] Changed paths according to moved thirdparty dependencies. This bit change is merged from r92613.
* [rev:93955] fix bug that can't find tinymce_ssbuttons under sapphire/thirdpaty. this is a change merged from r92853 http://open.silverstripe.org/changeset/92853#file3
* [rev:93950] fix bug that can't find tinymce_ssbuttons under sapphire/thirdpaty. this is a change merged from r92853 http://open.silverstripe.org/changeset/92853#file3
* [rev:93955] fix bug that can't find tinymce_ssbuttons under sapphire/thirdpaty. this is a change merged from r92853 `http://open.silverstripe.org/changeset/92853#file3`
* [rev:93950] fix bug that can't find tinymce_ssbuttons under sapphire/thirdpaty. this is a change merged from r92853 `http://open.silverstripe.org/changeset/92853#file3`
* [rev:93935] merge r92502 from trunk for HtmlEditorConfig.php, merge r93934 from trunk for HtmlEditorField.js, merge r92500 from trunk for sapphire/thirdpart/tinymce-advcode/editor_plugin_src.js, aiming to solve the conflict of folder name tinymce-advcode.
* [rev:93860] Fixed incorrect hasDatabaseField() in SearchFilter::getDbName() - use hasOwnTableDatabaseField() instead
* [rev:93777] Fixed SearchContextTest failure
@ -729,4 +729,4 @@
* [rev:96779] admin section via URL (from r87320)
* [rev:96777] javascript syntax fixes (from r86396)
* [rev:96712] MERGE merged back a whole bunch of defect fixes from trunk (from r87846)
*
*

2
docs/en/howto/index.md
View File

@ -13,4 +13,4 @@ the language and functions which are used in the guides.
## Feedback
If you have a topic you would like covered in these how to's please ask for it on our [Bug Tracker](http://open.silverstripe.org)
If you have a topic you would like covered in these how to's please ask for it on our [Bug Tracker] `http://open.silverstripe.org`

16
docs/en/index.md
View File

@ -1,22 +1,22 @@
This website documents high-level features of the [SilverStripe open source platform](http://www.silverstripe.org), aimed
at developers.
at developers.
Please read our [guide to contributing documentation](misc/contributing#writing-documentation) if you want to help out!
### Overview
* [Getting started](http://silverstripe.org/getting-started/) | [Feature Overview](http://silverstripe.org/introduction/) | [Demo](http://demo.silverstripe.org/)
* [Download and Installation](installation/) | [Upgrading](/installation/upgrading) | [Requirements](/installation/server-requirements) | [Changelog](http://open.silverstripe.org/wiki/ChangeLog) | [Roadmap](http://open.silverstripe.com/roadmap)
* [API documentation](http://api.silverstripe.org/current) | [Official english book](http://www.silverstripe.org/silverstripe-book) | [Official german book](http://www.silverstripe.org/das-silverstripe-buch)
* [Getting started](http://silverstripe.org/getting-started/) | [Feature Overview] `http://silverstripe.org/introduction/` | [Demo](http://demo.silverstripe.org/)
* [Download and Installation](installation/) | [Upgrading](/installation/upgrading) | [Requirements](/installation/server-requirements) | [Changelog] `http://open.silverstripe.org/wiki/ChangeLog` | [Roadmap] `http://open.silverstripe.com/roadmap`
* [API documentation](http://api.silverstripe.org/current) | [Official english book] `http://www.silverstripe.org/silverstripe-book` | [Official german book] `http://www.silverstripe.org/das-silverstripe-buch`
### Getting support
[Forum](http://www.silverstripe.org/forums/) | [IRC channel](http://silverstripe.org/irc) | [End user docs](http://userhelp.silverstripe.com) | [Core mailinglist](https://groups.google.com/forum/#!forum/silverstripe-dev)
[Forum](http://www.silverstripe.org/forums/) | [IRC channel](https://irc.silverstripe.org) | [End user docs](http://userhelp.silverstripe.com) | [Core mailinglist](https://groups.google.com/forum/#!forum/silverstripe-dev)
### Level 1: Building your first SilverStripe website
* [Introduction to PHP5 (zend.com)](http://devzone.zend.com/node/view/id/627)
* [Introduction to PHP5 (zend.com)] `http://devzone.zend.com/node/view/id/627`
* [Tutorials](tutorials)
* [Building a basic site](tutorials/building-a-basic-site)
* [Extending a basic site](tutorials/extending-a-basic-site)
@ -59,5 +59,5 @@ Please read our [guide to contributing documentation](misc/contributing#writing-
* [Coding Conventions](misc/coding-conventions)
<div class="hint" markdown="1">
Looking for the old DokuWiki installation? See [doc.silverstripe.org/old](http://doc.silverstripe.org/old).
</div>
Looking for the old DokuWiki installation? See [doc.silverstripe.org/old] `http://doc.silverstripe.org/old`.
</div>

4
docs/en/installation/common-problems.md
View File

@ -2,7 +2,7 @@
From time to time, things will go wrong. Here's a few things to try when you're confused.
See ["8 Common SilverStripe Errors Explain (and solved!) (leftandmain.com)"](http://www.leftandmain.com/silverstripe-tips/2010/09/08/8-common-silverstripe-errors-explained-and-solved/)
See ["8 Common SilverStripe Errors Explain (and solved!) (leftandmain.com)"] `http://www.leftandmain.com/silverstripe-tips/2010/09/08/8-common-silverstripe-errors-explained-and-solved/`
for more common problems.
## The output shows only "Website Error"
@ -71,4 +71,4 @@ needs to create/have write-access to:
* The main installation directory (for creating .htaccess file and assets directory)
* The mysite folder (to create _config.php)
* After the install, the assets directory is the only directory that needs write access.
* Image thumbnails will not show in the CMS if permission is not given
* Image thumbnails will not show in the CMS if permission is not given

4
docs/en/installation/from-source.md
View File

@ -256,7 +256,7 @@ or as flat files through tickets or emails).
## Manual installation of other modules ##
Modules listed on [silverstripe.org/modules](http://silverstripe.org/modules) can be hosted
Modules listed on [silverstripe.org/modules] `http://silverstripe.org/modules` can be hosted
in any version control system (typically subversion or git). Please read the module
page for source code locations and installation instructions. The general process of
[module installation](/topics/modules) is documented as well.
@ -285,4 +285,4 @@ See [piston.rubyforge.org](http://piston.rubyforge.org/import.html).
* [Contributing: Submitting patches](/misc/contributing)
* [Pro git - free online book](http://progit.org/book/)
* [Git cheat sheet - github.com](https://github.com/guides/git-cheat-sheet)
* [Git - SVN Crash Course - git.or.cz](http://git.or.cz/course/svn.html)
* [Git - SVN Crash Course - git.or.cz](http://git.or.cz/course/svn.html)

4
docs/en/installation/server-requirements.md
View File

@ -23,7 +23,7 @@ Our web-based [PHP installer](/installation) can check if you meet the requireme
* MySQL 5.0+
* PostgreSQL 8.3+ (requires ["postgresql" module](http://silverstripe.org/postgresql-module))
* SQL Server 2008. (requires ["mssql" module](http://silverstripe.org/microsoft-sql-server-database/))
* Support for [Oracle](http://www.silverstripe.org/oracle-database-module/) and [SQLite](http://silverstripe.org/sqlite-database/) is not commercially supported, but is under development by our open source community.
* Support for [Oracle] `http://www.silverstripe.org/oracle-database-module/` and [SQLite](http://silverstripe.org/sqlite-database/) is not commercially supported, but is under development by our open source community.
* One of the following web server products:
* Apache 1.3+ with mod_rewrite and "AllowOverride All" set
* IIS 5.x+ (Version 7.5+ and URL Rewrite Module recommended)
@ -46,4 +46,4 @@ SilverStripe CMS is designed to work well with Firefox 3.0+ and Internet Explore
## End user requirements ##
SilverStripe CMS is designed to make excellent, standards-compliant websites that are compatible with a wide range of industry standard browsers and operating systems. A competent developer is able to produce websites that meet W3C guidelines for HTML, CSS, JavaScript, and accessibility, in addition to meeting specific guildelines, such as e-government requirements.
SilverStripe CMS is designed to make excellent, standards-compliant websites that are compatible with a wide range of industry standard browsers and operating systems. A competent developer is able to produce websites that meet W3C guidelines for HTML, CSS, JavaScript, and accessibility, in addition to meeting specific guildelines, such as e-government requirements.

4
docs/en/misc/coding-conventions.md
View File

@ -435,5 +435,5 @@ See [security](/topics/security) for conventions related to handing security per
## License
Parts of these coding conventions were adapted from [Zend Framework](http://framework.zend.com/manual/en/coding-standard.overview.html),
which are licensed under BSD (see [license](http://framework.zend.com/license)).
Parts of these coding conventions were adapted from [Zend Framework] `http://framework.zend.com/manual/en/coding-standard.overview.html`,
which are licensed under BSD (see [license](http://framework.zend.com/license)).

24
docs/en/misc/contributing.md
View File

@ -15,7 +15,7 @@ See our [high level overview on silverstripe.org](http://silverstripe.org/contri
If you have discovered a bug in SilverStripe, we'd be glad to hear about it -
well written bug reports can be half of the solution already!
Our bugtracker is located on [open.silverstripe.org](http://open.silverstripe.org/) (create a [new ticket](http://open.silverstripe.org/newticket)).
Our bugtracker is located on [open.silverstripe.org] `http://open.silverstripe.org/` (create a [new ticket] `http://open.silverstripe.org/newticket`).
## Submiting Bugfixes and Enhancements
@ -24,7 +24,7 @@ We're not perfect, and need your help - for example in the form of patches for o
### Setup your project for contributions
In contrast to running a SilverStripe website, you can't use the standard download archive for this purpose.
Our [module list on silverstripe.org](http://silverstripe.org/modules) lists the repository locations alongside
Our [module list on silverstripe.org] `http://silverstripe.org/modules` lists the repository locations alongside
the archive downloads, typically using a version control system like "git" or "[subversion](subversion)".
General guidelines:
@ -41,7 +41,7 @@ step.
* It's better to submit multiple patches with separate bits of functionality than a big patch containing lots of
changes
* Document your code inline through [PHPDoc](http://en.wikipedia.org/wiki/PHPDoc) syntax. See our
[API documentation](http://api.silverstripe.org/trunk) for good examples.
[API documentation] `http://api.silverstripe.org/trunk` for good examples.
* Also check and update documentation on [doc.silverstripe.org](http://doc.silverstripe.org). Check for any references to functionality deprecated or extended through your patch. Documentation changes should be included in the patch.
* We will attribute the change to you whereever possible (git does this automatically for pull requests)
* If you get stuck, please post to the [forum](http://silverstripe.org/forum) or for deeper core problems, to the [core mailinglist](https://groups.google.com/forum/#!forum/silverstripe-dev)
@ -75,10 +75,10 @@ package your changes as a "patch" file. Please read the [official Subversion boo
Please don't submit patch files for modules on git, as they cause us more work.
To submit a patch, [register](http://open.silverstripe.com/register) or [login](http://open.silverstripe.org/login) on open.silverstripe.org, and attach the patch to an appropriate ticket.
To submit a patch, [register] `http://open.silverstripe.com/register` or [login] `http://open.silverstripe.org/login` on `open.silverstripe.org`, and attach the patch to an appropriate ticket.
Please include in the comment the revision number that the patch is applicable for and a brief outline of what you fixed and how.
[Submit a patch (requires account on open.silverstripe.org)](http://open.silverstripe.com/newticket?field_type=patch&field_owner=ischommer&attachment=1)
[Submit a patch (requires account on `open.silverstripe.org`)] `http://open.silverstripe.com/newticket?field_type=patch&field_owner=ischommer&attachment=1`
You can create a patch file through the svn diff-command on the command-line.
More info in the [svn redbook](http://svnbook.red-bean.com/en/1.1/ch03s05.html#svn-ch-3-sect-5.3.2).
@ -94,7 +94,7 @@ Some gotchas when using subversion and the patch format:
* Create patches relative to the working copy (*sapphire/main.php* instead of */Users/myuser/sapphire/main.php*)
* Remember the shortcomingsof *svn diff*: Please document moved files and created/deleted directories separately
The "[Patches: Core](http://open.silverstripe.com/report/101)" and "[Patches: Modules](http://open.silverstripe.com/report/102)" reports will let you see where all the patches are at.
The "[Patches: Core] `http://open.silverstripe.com/report/101`" and "[Patches: Modules] `http://open.silverstripe.com/report/102`" reports will let you see where all the patches are at.
### Commit Messages
@ -114,7 +114,7 @@ Some examples:
Further guidelines:
* Each commit should form a logical unit - if you fix two unrelated bugs, commit each one separately
* If you are fixing a ticket from our [bugtracker](http://open.silverstripe.com), please append `(fixes #<ticketnumber>)`
* If you are fixing a ticket from our [bugtracker] `http://open.silverstripe.com`, please append `(fixes #<ticketnumber>)`
* If your change is related to another changeset, reference it with `r<revisionnumber>`.
* Please mention the changed classes and methods in your comment - the message should be understandable on its own without browsing any sourcecode
@ -136,7 +136,7 @@ you agree that is can be used in distributions and derivative works of SilverStr
## Reporting Security Issues
Report security issues to [security@silverstripe.com](mailto:security@silverstripe.com). Please don't file security
issues in our [bugtracker](http://open.silverstripe.org). In the event of a confirmed vulnerability in SilverStripe
issues in our [bugtracker] `http://open.silverstripe.org`. In the event of a confirmed vulnerability in SilverStripe
core, we will take the following actions:
* Acknowledge to the reporter that we’ve received the report and that a fix is forthcoming. We’ll give a rough
@ -167,7 +167,7 @@ Note: Smaller edits can be performed in the github.com web interface on your for
every page view should have an "edit this file" button.
The [doc.silverstripe.org](http://doc.silverstripe.org) website itself is powered by a
SilverStripe project that uses the ["sapphiredocs" module](https://github.com/silverstripe/silverstripe-sapphiredocs)
SilverStripe project that uses the ["sapphiredocs" module] `https://github.com/silverstripe/silverstripe-sapphiredocs`
to convert Markdown formatted files into searchable HTML pages with index lists.
### Repositories
@ -275,7 +275,7 @@ on placing HTML blocks inside Markdown.
Documentation is kept alongside the source code, typically in a module subdirectory like `sapphire/docs/en/`.
Each language has its own subfolder, which can duplicate parts or the whole body of documentation.
German documentation would for example live in `sapphire/docs/de/`.
The [sapphiredocs](https://github.com/silverstripe/silverstripe-sapphiredocs) module that drives
The [sapphiredocs] `https://github.com/silverstripe/silverstripe-sapphiredocs` module that drives
[doc.silverstripe.org](http://doc.silverstripe.org) automatically resolves these subfolders into a language dropdown.
### Further reading
@ -288,10 +288,10 @@ The [sapphiredocs](https://github.com/silverstripe/silverstripe-sapphiredocs) mo
The content for UI elements (button labels, field titles) and instruction texts shown in the CMS and
elsewhere is stored in the PHP code for a module (see [i18n](/topics/i18n)). All content can be extracted as a "language file"
which is then uploaded to [translate.silverstripe.org](http://translate.silverstripe.org). This website provides
which is then uploaded to [translate.silverstripe.org] `http://translate.silverstripe.org`. This website provides
an online editor for translators (like you!). Every now and then, translations will be merged back into
the codebase from there, and released alongside other PHP code.
SilverStripe is already translated in over 60 languages, and we're relying on native speakers
to keep these up to date, and of course add new languages. Please [register](http://translate.silverstripe.org/apply)
to keep these up to date, and of course add new languages. Please [register] `http://translate.silverstripe.org/apply`
a free translator account to get started, even if you just feel like fixing up a few sentences.

2
docs/en/misc/index.md
View File

@ -12,5 +12,5 @@ sections.
## Feedback
If you have a topic you would like covered in the misc section please ask for it on our [Bug Tracker](http://open.silverstripe.org)
If you have a topic you would like covered in the misc section please ask for it on our [Bug Tracker] `http://open.silverstripe.org`

16
docs/en/misc/module-release-process.md
View File

@ -7,7 +7,7 @@ If you do, we would love to host your module and have you become an official mod
Please read our ["Contributing to SilverStripe"](http://silverstripe.org/contributing-to-silverstripe/) overview.
Once you have created a module, login at [silverstripe.org](http://silverstripe.org) and
[submit your module](http://silverstripe.org/modules/manage/add)
[submit your module](http://addons.silverstripe.org/)
It's very important to us that users of SilverStripe can come to expect a level of quality from the core product and any
modules running on it. In order to provide this, we require certain things from module maintainers.
@ -32,7 +32,7 @@ Each line of code you write should be version controlled, in version control sys
available for opensource projects, including wiki and bugtracker functionality
(e.g. [Google Code for Subversion](http://code.google.com) or [Github for Git](http://github.com)).
* Add your module to [silverstripe.org/modules](http://silverstripe.org/modules) (and keep the version compatibility information current)
* Add your module to [silverstripe.org/modules] `http://silverstripe.org/modules` (and keep the version compatibility information current)
* Follow our [coding-conventions](coding-conventions)
* Write unit tests and functional tests covering code bundled with the module - see [testing-guide](/topics/testing)
* Ensure your code is [localizable](/topics/i18n) and [translatable](/topics/translation)
@ -52,7 +52,7 @@ your modules page on silverstripe.org
Both Google Code and github.com provide their own bugtracker - we encourage you to use any built-in tools that come with
your version control hoster. Most Silverstripe-maintained modules have their bugtracker on
[open.silverstripe.org](http://open.silverstripe.org).
[open.silverstripe.org] `http://open.silverstripe.org`.
Providing bugtracking is a major form of communicating with your users in an efficient way, and will provide a good overview
of outstanding work and the stability of your code to an interested user.
@ -111,7 +111,7 @@ that you can link from the `README.md` file. Example:
tutorial.md
howto-search-mymodule.md
The ["sapphiredocs" module](http://open.silverstripe.org/browser/modules/sapphiredocs/trunk) can be used
The ["sapphiredocs" module] `http://open.silverstripe.org/browser/modules/sapphiredocs/trunk` can be used
to list and render content inside a `docs/` folder (although it is not required, Markdown is designed
to be readable in plain text as well).
@ -120,8 +120,8 @@ to be readable in plain text as well).
In return for all your hard work in putting a high-quality module on the site, the SilverStripe project has the following
options to support you:
* Use of [trac](http://open.silverstripe.org) to keep your bugs and feature requests organised
* Advertising of your module on the http://silverstripe.org/modules/ modules page once it has reached a beta stage and shown
* Use of [trac] `http://open.silverstripe.org` to keep your bugs and feature requests organised
* Advertising of your module on the http://addons.silverstripe.org/add-ons modules page once it has reached a beta stage and shown
to meet our requirements above.
* We might showcase your module on our blog and/or newsletter, when it's first released and/or when a major version with
significant new features is released. We'll work with you to publicise it on other blogs too (it helps if you deliver
@ -189,7 +189,7 @@ export to a tar.gz.
* See [Producing OSS: "Announcing Releases"](http://producingoss.com/en/testing-and-releasing.html#release-announcement)
* Update your [documentation](module-release-process#documentation) in the sourcecode, wiki and README
* Add your release to the [silverstripe.org/modules](http://silverstripe.org/modules) listing
* Add your release to the [silverstripe.org/modules] `http://silverstripe.org/modules` listing
* Announce the release on [silverstripe-announce](http://groups.google.com/group/silverstripe-announce). Include a
[changelog](module-release-process#changelogs), the download link and instructions for filing bug reports.
* If this release is a major release, our [marketing guys](http://silverstripe.com/contact/) will strive to announce it
@ -238,5 +238,5 @@ trunk.
* [Module Development](/topics/module-development)
* [Documentation Guide](contributing#writing-documentation)
* [Contributing to SilverStripe](http://silverstripe.org/contributing-to-silverstripe/)
* [Submit your Module](http://silverstripe.org/modules/manage/add)
* [Submit your Module] `http://silverstripe.org/modules/manage/add`
* [subversion](subversion)

10
docs/en/misc/release-process.md
View File

@ -9,13 +9,13 @@ The current maintainer responsible for planning and performing releases is Ingo
## Release Planning
Our most up-to-date release plans are typically in the [roadmap](http://open.silverstripe.com/roadmap).
Our most up-to-date release plans are typically in the [roadmap] `http://open.silverstripe.com/roadmap`.
New features and API changes are typically discussed on the [core
mailinglist](http://groups.google.com/group/silverstripe-dev). They are prioritized by the core team as tickets on
[open.silverstripe.org](http://open.silverstripe.com/).
[open.silverstripe.org] `http://open.silverstripe.com/`.
Release dates are usually not published prior to the release, but you can get a good idea of the release status by
reviewing the [release milestone](http://open.silverstripe.com/roadmap) on open.silverstripe.org. Releases will be
reviewing the [release milestone] `http://open.silverstripe.com/roadmap` on `open.silverstripe.org`. Releases will be
announced on the [release announcements mailing list](http://groups.google.com/group/silverstripe-announce).
Releases of the *cms* and *sapphire* modules are coupled at the moment, they follow the same numbering scheme. Module
@ -97,7 +97,7 @@ How to deprecate an API:
* Update the deprecated code to throw an `E_USER_NOTICE` error, with a message starting with the string 'DEPRECATED:'.
In time, we may use that string to identify deprecation errors, so please ensure that you add this string to the notice level error.
* Make sure that the old deprecated function works by calling the new function - don't have duplicated code!
* Mark in which release the function was deprecated (find out next release in the [roadmap](http://open.silverstripe.com/roadmap)), so we can determine when to finally remove it.
* Mark in which release the function was deprecated (find out next release in the [roadmap] `http://open.silverstripe.com/roadmap`), so we can determine when to finally remove it.
Here's an example for replacing `Director::isDev()` with a (theoretical) `Env::is_dev()`:
:::php
@ -113,4 +113,4 @@ Here's an example for replacing `Director::isDev()` with a (theoretical) `Env::i
* Deprecated as of in 2.2.2
* Still deprecated in 2.2.3
* Still deprecated in 2.2.4
* Removed from 2.3.0
* Removed from 2.3.0

8
docs/en/misc/ss-markdown.md
View File

@ -17,9 +17,9 @@ and HTML output should still be readable with our custom markup unparsed.
While most of the Markdown syntax is parseable by all common implementations,
the special syntax is relying on a custom SilverStripe project that powers `http://doc.silverstripe.org`.
The website a standard SilverStripe installation with the [sapphiredocs](https://github.com/silverstripe/silverstripe-sapphiredocs/)
module installed (see module [README](https://github.com/silverstripe/silverstripe-sapphiredocs/blob/master/README.md) and
[documentation](https://github.com/silverstripe/silverstripe-sapphiredocs/tree/master/docs/en)).
The website a standard SilverStripe installation with the [sapphiredocs] `https://github.com/silverstripe/silverstripe-sapphiredocs/`
module installed (see module [README] `https://github.com/silverstripe/silverstripe-sapphiredocs/blob/master/README.md` and
[documentation] `https://github.com/silverstripe/silverstripe-sapphiredocs/tree/master/docs/en`).
## Syntax
@ -112,4 +112,4 @@ Of course, the `sapphiredocs` code is BSD licensed - we're looking forward to yo
## Related ##
* [contributing](contributing#writing-documentation): The doc.silverstripe.org website has certain styling and writing conventions
* [contributing](contributing#writing-documentation): The doc.silverstripe.org website has certain styling and writing conventions

12
docs/en/misc/subversion.md
View File

@ -1,7 +1,7 @@
## Subversion
Subversion [website](http://subversion.tigris.org) is a **version control system**.
You can browse our Subversion "code repository" [here](http://open.silverstripe.com/browser), however we now use GIT to
Subversion [website](http://subversion.apache.org/) is a **version control system**.
You can browse our Subversion "code repository" [here] `http://open.silverstripe.com/browser`, however we now use GIT to
manage our modules (see [Contributing](contributing)).
This page only describes SilverStripe-specific information on how to handle subversion. For a general introduction,
@ -10,7 +10,7 @@ please read the [Official Subversion Book](http://svnbook.red-bean.com/) (availa
Start with the ["Basic Usage" chapter](http://svnbook.red-bean.com/en/1.5/svn.tour.html).
### Clients
Make sure you have an updated [subversion client](http://subversion.tigris.org/links.html#clients) installed.
Make sure you have an updated [subversion client](http://subversion.apache.org/) installed.
Subversion 1.5 or higher is required for features such as relative externals and merge tracking.
### Checkout / Download
@ -106,10 +106,10 @@ Here is a step-by-step guide on how to work with SVN on your own site. It overs
introduction. NOTE: you will need SSH and SVN installed and available on your server.
* Install LAMP / WAMP and an SVN application (Tortoise SVN on Windows)
* Buy an SVN repository: http://www.SVNrepository.com/ OR set one up on your own server or look at freeby alternatives.
* Buy an SVN repository: http://www.svnrepository.com/ OR set one up on your own server or look at freeby alternatives.
* Go to your SVN repository server and create a new repository - I would recommend to name it after the site you are about to setup, e.g. myfirstsite.com.
* Create / go to web folder on local LAMP/WAMP
* SVN "checkout" your empty repository (e.g. http://sunny.SVNrepository.com/SVN/myaccountname/myfirstsite.com).
* SVN "checkout" your empty repository (e.g. `http://sunny.SVNrepository.com/SVN/myaccountname/myfirstsite.com`).
* SVN "propedit" SVN:externals, add the following SVN property to the root directory:
SVN:externals (also add your own general modules here, etc... etc... this should be a long list):
@ -172,4 +172,4 @@ where 1234567 is the revision of your repository that you want to use
### Related
* [contributing](contributing)
* [release process](release-process)
* [release process](release-process)

6
docs/en/reference/advanced-templates.md
View File

@ -357,7 +357,7 @@ However, if you want, you can call `obj()` and `val()` yourself.
Fragment links are links with a "#" in them. A frequent use-case is to use fragment links to point to different
sections of the current page. For example, we might have this in our template.
For, example, we might have this on http://www.example.com/my-long-page/
For, example, we might have this on `http://www.example.com/my-long-page/`
:::ss
<ul>
@ -367,8 +367,8 @@ For, example, we might have this on http://www.example.com/my-long-page/
So far, so obvious. However, things get tricky because of we have set our `<base>` tag to point to the root of your
site. So, when you click the first link you will be sent to http://www.example.com/#section1 instead of
http://www.example.com/my-long-page/#section1
site. So, when you click the first link you will be sent to `http://www.example.com/#section1` instead of
`http://www.example.com/my-long-page/#section1`
In order to prevent this situation, the SSViewer template renderer will automatically rewrite any fragment link that
doesn't specify a URL before the fragment, prefixing the URL of the current page. For our example above, the following

6
docs/en/reference/bbcode.md
View File

@ -31,6 +31,6 @@ BBCode can be enabled in comments by adding the following to _config.php
- [email]you@yoursite.com[/email]
- [email=you@yoursite.com]Email[/email]
- [ulist][*]unordered item 1[/ulist]
- [img]http://www.website.com/image.jpg[/img]
- [url]http://www.website.com/[/url]
- [url=http://www.website.com/]Website[/url]
- [img]`http://www.website.com/image.jpg`[/img]
- [url]`http://www.website.com/`[/url]
- [url=`http://www.website.com/`]Website[/url]

4
docs/en/reference/director.md
View File

@ -50,8 +50,8 @@ See [controller](/topics/controller) for examples and explanations on how the ru
SilverStripe comes with certain rewrite rules (e.g. for *admin/assets*).
* [sapphire/_config.php](http://open.silverstripe.org/browser/modules/sapphire/trunk/_config.php)
* [cms/_config.php](http://open.silverstripe.org/browser/modules/cms/trunk/_config.php)
* [sapphire/_config.php] `http://open.silverstripe.org/browser/modules/sapphire/trunk/_config.php`
* [cms/_config.php] `http://open.silverstripe.org/browser/modules/cms/trunk/_config.php`
## Links

2
docs/en/reference/execution-pipeline.md
View File

@ -58,7 +58,7 @@ controller object and then call `[api:Controller::run()]`.
**See:** The API documentation of `[api:Director]` for information about how Director parses URLs and hands control over to a controller object.
In general, the URL is build up as follows: page/action/ID/otherID - e.g. http://www.mysite.com/mypage/addToCart/12.
In general, the URL is build up as follows: page/action/ID/otherID - e.g. `http://www.mysite.com/mypage/addToCart/12`.
This will add an object with ID 12 to the cart.
When you create a function, you can access the ID like this:

2
docs/en/reference/modeladmin.md
View File

@ -111,5 +111,5 @@ customized for each `[api:DataObject]`'s search results using `$summary_fields`.
## Related
* `[api:SearchContext]`
* [genericviews Module](http://silverstripe.org/generic-views-module)
* [genericviews Module] `http://silverstripe.org/generic-views-module`
* [Presentation about ModelAdmin at SupperHappyDevHouse Wellington](http://www.slideshare.net/chillu/modeladmin-in-silverstripe-23)

6
docs/en/reference/restfulservice.md
View File

@ -7,8 +7,8 @@
returned from the web service. Further it supports caching of the response, and you can customize the cache interval.
To gain the functionality you can either create a new `[api:RestfulService]` object or create a class extending the
RestfulService (see [flickrservice](http://silverstripe.org/flickr-module/) and
[youtubeservice](http://silverstripe.org/youtube-gallery-module/) modules).
RestfulService (see [flickrservice] `http://silverstripe.org/flickr-module` and
[youtubeservice] `http://silverstripe.org/youtube-gallery-module/` modules).
## Examples
@ -177,4 +177,4 @@ Put something like this code in mysite/templates/Layout/HomePage.ss:
## API Documentation
`[api:RestfulService]`
`[api:RestfulService]`

2
docs/en/reference/searchcontext.md
View File

@ -13,7 +13,7 @@ In case you need multiple contexts, consider namespacing your request parameters
the $fields constructor parameter.
`[api:SearchContext]` is mainly used by `[api:ModelAdmin]`, our generic data administration interface. Another
implementation can be found in generic frontend search forms through the [genericviews](http://silverstripe.org/generic-views-module) module.
implementation can be found in generic frontend search forms through the [genericviews] `http://silverstripe.org/generic-views-module` module.
## Requirements

2
docs/en/reference/sitetree.md
View File

@ -233,7 +233,7 @@ as-is, and instead make another method, such as ChildProducts(), to get the data
### Dynamic Grouping
Something that has been talked about [here](http://www.silverstripe.com/site-builders-forum/flat/15416#post15940) is the
Something that has been talked about [here] `http://www.silverstripe.com/site-builders-forum/flat/15416#post15940` is the
concept of "dynamic grouping". In essence, it means adding navigational tree nodes to the tree that don't correspond to
a database record.

6
docs/en/reference/staticpublisher.md
View File

@ -121,7 +121,7 @@ Put this in mysite/_config.php. This will create static content in a "cache/" s
**sitedir** with the a subdirectory that you would like to serve the site from (for example, in your dev environment).
[View .htaccess
example](http://open.silverstripe.com/browser/modules/cms/trunk/code/staticpublisher/htaccess_example_rsyncsingleserver)
example] `http://open.silverstripe.com/browser/modules/cms/trunk/code/staticpublisher/htaccess_example_rsyncsingleserver`
* **New for 2.4:** In 2.4, we use a simple PHP script, static-main.php, to control cache lookup. This make the
.htaccess update simpler.
@ -238,7 +238,7 @@ It will serve requests from the cache, statically, if the cache file exists. Re
subdirectory that you would like to serve the site from (for example, in your dev environment).
[View .htaccess
example](http://open.silverstripe.com/browser/modules/cms/trunk/code/staticpublisher/htaccess_example_rsyncmultiservers)
example] `http://open.silverstripe.com/browser/modules/cms/trunk/code/staticpublisher/htaccess_example_rsyncmultiservers`
## Cache Control
@ -257,7 +257,7 @@ To enable cache control, specify "php" instead of "html" in the RsyncMultiHostPu
And use this slightly different .htaccess file. Make sure that index.php can be used as a directory index!
[View .htaccess
example](http://open.silverstripe.com/browser/modules/cms/trunk/code/staticpublisher/htaccess_example_rsyncwithphp)
example] `http://open.silverstripe.com/browser/modules/cms/trunk/code/staticpublisher/htaccess_example_rsyncwithphp`
## Deployment

10
docs/en/reference/urlvariabletools.md
View File

@ -10,8 +10,8 @@ core.
Append the option and corresponding value to your URL in your browser's address bar. You may find the [Firefox UrlParams extension](https://addons.mozilla.org/en-US/firefox/addon/1290) useful in order to debug a POST requests (Like Forms).
http://yoursite.com/page?option_name=value
http://yoursite.com/page?option_1=value&option_2=value
`http://yoursite.com/page?option_name=value`
`http://yoursite.com/page?option_1=value&option_2=value`
## Templates
@ -79,9 +79,9 @@ Redirections](reference/director/#redirection) for more information and examples
| Site URL | | Action |
| -------- | | ------ |
| http://yoursite.com**/dev/build** | | Rebuild the entire database and manifest, see below for additional URL Variables |
| http://yoursite.com**/admin/publishall/** | | Publish all pages on the site |
| http://yoursite.com**/anypage/images/flush** | | Creates new images for the page by deleting the resized ones and going back to the original to create new resized one |
| `http://yoursite.com`**/dev/build** | | Rebuild the entire database and manifest, see below for additional URL Variables |
| `http://yoursite.com`**/admin/publishall/** | | Publish all pages on the site |
| `http://yoursite.com`**/anypage/images/flush** | | Creates new images for the page by deleting the resized ones and going back to the original to create new resized one |
### /dev/build

4
docs/en/topics/configuration.md
View File

@ -8,7 +8,7 @@ itself.
This lack of a configuration-GUI is on purpose, as we'd like to keep developer-level options where they belong (into
code), without cluttering up the interface. See this core forum discussion ["The role of the
CMS"](http://www.silverstripe.com/core-team-discussion/flat/2723) for further reasoning.
CMS"] `http://www.silverstripe.com/core-team-discussion/flat/2723` for further reasoning.
In addition to these principle, some settings are
* Author-level configuration like interface language or date/time formats can be performed in the CMS "My Profile" section (`admin/myprofile`).
@ -75,4 +75,4 @@ See [security](/topics/security) and [permission](/reference/permission)
## See Also
[Config Cheat sheet](http://www.ssbits.com/a-config-php-cheatsheet/)
[Config Cheat sheet](http://www.ssbits.com/a-config-php-cheatsheet/)

2
docs/en/topics/css.md
View File

@ -91,4 +91,4 @@ See [typography](/reference/typography) for more information.
## Related ##
* [javascript](javascript)
* ["Compass" module](http://silverstripe.org/compass-module/): Allows writing CSS in SASS/LESS syntax, with better code management through mixins, includes and variables
* ["Compass" module] `http://silverstripe.org/compass-module/`: Allows writing CSS in SASS/LESS syntax, with better code management through mixins, includes and variables

4
docs/en/topics/i18n.md
View File

@ -16,7 +16,7 @@ This page aims to describe the low-level functionality of the i18n-API. It targe
* want to make their PHP-code (e.g. form labels) i18n-ready
Please note that this project scope currently **doesn't include full support for format conversion in dates or
currencies**. Check our [roadmap](http://open.silverstripe.com/roadmap).
currencies**. Check our [roadmap] `http://open.silverstripe.com/roadmap`.
## Usage
@ -325,4 +325,4 @@ Example Translation Table (mymodule/javascript/lang/de_DE.js)
## Links
* [http://www.i18nguy.com/](http://www.i18nguy.com/)
* [balbus.tk i18n notes](http://www.balbus.tk/internationalize)
* [balbus.tk i18n notes] `http://www.balbus.tk/internationalize`

2
docs/en/topics/index.md
View File

@ -33,4 +33,4 @@ It is where most documentation should live, and is the natural "second step" aft
## Feedback
If you have a topic you would like covered in these section please ask for it on our [Bug Tracker](http://open.silverstripe.org)
If you have a topic you would like covered in these section please ask for it on our [Bug Tracker] `http://open.silverstripe.org`

16
docs/en/topics/javascript.md
View File

@ -123,7 +123,7 @@ Main advantages over simpler jQuery plugins are:
* Constructor/Destructor hooks
* Focus management and mouse interaction
See the [official developer guide](http://jqueryui.com/docs/Developer_Guide) and other
See the [official developer guide] `http://jqueryui.com/docs/Developer_Guide` and other
[tutorials](http://bililite.com/blog/understanding-jquery-ui-widgets-a-tutorial/) to get started.
Example: Highlighter
@ -503,12 +503,12 @@ Documentation in JavaScript usually resembles the JavaDoc standard, although the
flexibility of the language it can be hard to generate automated documentation, particularly with the predominant usage
of closure constructs in jQuery and jQuery.entwine.
To generate documentation for SilverStripe code, use [JSDoc toolkit](http://code.google.com/p/jsdoc-toolkit/) (see
[reference of supported tags](http://code.google.com/p/jsdoc-toolkit/wiki/TagReference)). For more class-oriented
JavaScript, take a look at the [jsdoc cookbook](http://code.google.com/p/jsdoc-toolkit/wiki/CookBook). The `@lends`
To generate documentation for SilverStripe code, use [JSDoc toolkit] `http://code.google.com/p/jsdoc-toolkit/` (see
[reference of supported tags] `http://code.google.com/p/jsdoc-toolkit/wiki/TagReference`). For more class-oriented
JavaScript, take a look at the [jsdoc cookbook] `http://code.google.com/p/jsdoc-toolkit/wiki/CookBook`. The `@lends`
and `@borrows` properties are particularly useful for documenting jQuery-style code.
JSDoc-toolkit is a command line utility, see [usage](http://code.google.com/p/jsdoc-toolkit/wiki/CommandlineOptions).
JSDoc-toolkit is a command line utility, see [usage] `http://code.google.com/p/jsdoc-toolkit/wiki/CommandlineOptions`.
Example: jQuery.entwine
@ -566,7 +566,7 @@ Example: jQuery.entwine
It is important to verify that your code actually does what it says, and the best way to ensure this are **automated
tests**. For jQuery, we use two different tools with different uses: **unit testing** with
[QUnit](http://docs.jquery.com/QUnit) (also used by the jQuery team for the core libraries), and **behaviour driven
testing** with [JSpec](http://visionmedia.github.com/jspec/). There are overlaps between the two solutions, if in doubt
testing** with [JSpec] `http://visionmedia.github.com/jspec/`. There are overlaps between the two solutions, if in doubt
start with JSpec, as it provides a much more powerful testing framework.
Example: QUnit test (from [jquery.com](http://docs.jquery.com/QUnit#Using_QUnit)):
@ -579,7 +579,7 @@ Example: QUnit test (from [jquery.com](http://docs.jquery.com/QUnit#Using_QUnit)
});
Example: JSpec Shopping cart test (from [visionmedia.github.com](http://visionmedia.github.com/jspec/))
Example: JSpec Shopping cart test (from [visionmedia.github.com] `http://visionmedia.github.com/jspec/`)
describe 'ShoppingCart'
before_each
@ -646,4 +646,4 @@ afraid to experiment with using other approaches.
* [css](css)
* [Unobtrusive Javascript](http://www.onlinetools.org/articles/unobtrusivejavascript/chapter1.html)
* [Quirksmode: In-depth Javascript Resources](http://www.quirksmode.org/resources.html)
* [behaviour.js documentation](http://open.silverstripe.org/browser/modules/sapphire/branches/2.4/thirdparty/behaviour/README.md)
* [behaviour.js documentation] `http://open.silverstripe.org/browser/modules/sapphire/branches/2.4/thirdparty/behaviour/README.md`

6
docs/en/topics/modules.md
View File

@ -33,8 +33,8 @@ instead make it easier for developers to build other applications.
## Finding Modules
* [Official module list on silverstripe.org](http://silverstripe.org/modules)
* [Subversion repository on open.silverstripe.org](http://open.silverstripe.org/browser/modules)
* [Official module list on silverstripe.org] `http://silverstripe.org/modules`
* [Subversion repository on open.silverstripe.org] `http://open.silverstripe.org/browser/modules`
## Installation
@ -49,7 +49,7 @@ guidelines.
### Download
To install a module you need to download the tar.gz file from the [modules page](http://www.silverstripe.org/modules) and extract this tar.gz to the root folder mentioned
To install a module you need to download the tar.gz file from the [modules page] `http://www.silverstripe.org/modules` and extract this tar.gz to the root folder mentioned
above.
Note some times the folders extracted from the tar.gz contain the version number or some other folders. You need to make

8
docs/en/topics/search.md
View File

@ -16,7 +16,7 @@ A working implementation of searchable DataObjects can be seen in the `[api:Mode
SilverStripe does not have a built-in method to search through file content (e.g. in PDF or DOC format).
You can either extract any textual file content into the `[File](api:File)->Content` property, or use a
dedicated search service like the [sphinx module](http://silverstripe.org/sphinx-module).
dedicated search service like the [sphinx module] `http://silverstripe.org/sphinx-module`.
## Related
@ -24,6 +24,6 @@ dedicated search service like the [sphinx module](http://silverstripe.org/sphinx
* `[api:RestfulServer]`
* [Tutorial: Site Search](/tutorials/site-search)
* [SearchContext](/reference/searchcontext)
* [genericviews module](http://silverstripe.org/generic-views-module)
* [sphinx module](http://silverstripe.org/sphinx-module)
* [lucene module](http://silverstripe.org/lucene-module)
* [genericviews module] `http://silverstripe.org/generic-views-module`
* [sphinx module] `http://silverstripe.org/sphinx-module`
* [lucene module] `http://silverstripe.org/lucene-module`

6
docs/en/topics/theme-development.md
View File

@ -218,12 +218,12 @@ Maybe even a nice link saying Website Powered by SilverStripe to show your suppo
A bunch of resources feel free to use to make your template awesome
* [http://kuler.adobe.com](http://kuler.adobe.com) - Kuler is a great color scheming tool
* [http://blog.html.it/layoutgala/](http://blog.html.it/layoutgala/) - 40 super cool CSS layouts for you to use
* `[http://blog.html.it/layoutgala/]` `http://blog.html.it/layoutgala/` - 40 super cool CSS layouts for you to use
* [http://designmeltdown.com](http://designmeltdown.com) - Great gallery of websites. Browse through and get inspired.
* [http://validator.w3.org/](http://validator.w3.org/) - Your template must pass 'or get near' validation.
* [http://famfamfam.com/lab/icons/](http://famfamfam.com/lab/icons/) - free, beautiful icons.
* [http://cssremix.com](http://cssremix.com) - Another CSS site gallery for inspiration.
* [http://www.maxdesign.com.au/presentation/process/](http://www.maxdesign.com.au/presentation/process/) - a good process for creating a design
* `[http://cssremix.com]` `http://cssremix.com` - Another CSS site gallery for inspiration.
* `[http://www.maxdesign.com.au/presentation/process/]` `http://www.maxdesign.com.au/presentation/process/` - a good process for creating a design
## Reference

6
docs/en/topics/themes.md
View File

@ -6,7 +6,7 @@ Themes can be used to kick start your SilverStripe projects, and generally make
## Downloading
Head to the [ Themes ](http://www.silverstripe.org/themes) area of the website to check out the wide range of themes
Head to the [ Themes ] `http://www.silverstripe.org/themes` area of the website to check out the wide range of themes
the community has built. Each theme has a page with links you can use to preview and download it. The theme is provided
as a .tar.gz file.
@ -38,6 +38,6 @@ click it -> Add to Archive (again) -> Then use the archive format GZIP.
## Links
* [Themes Listing on silverstripe.org](http://silverstripe.org/themes)
* [Themes Forum on silverstripe.org](http://www.silverstripe.org/themes-2/)
* [Themes Listing on silverstripe.org] `http://silverstripe.org/themes`
* [Themes Forum on silverstripe.org]`http://www.silverstripe.org/themes-2/`
* [Themes repository on github.com](http://github.com/silverstripe-themes)

6
docs/en/topics/translation.md
View File

@ -349,7 +349,7 @@ Example:
### Enabling the _t() function in templates
If you're looking to use [the _t() function](http://doc.silverstripe.com/doku.php?id=i18n#the_t_function) in template
If you're looking to use [the _t() function] `http://doc.silverstripe.com/doku.php?id=i18n#the_t_function` in template
files, you'll need to [set the i18n locale](/topics/translation#setting_the_i18n_locale) first.
(The reasoning is as follows: Translatable doesn't set the i18n locale. Historically these were two separate systems,
@ -404,8 +404,8 @@ This should e.g. enable you to use `$Locale.Nice` in template code.
## Related
* [translate.silverstripe.org](http://translate.silverstripe.org): Starting point for community-driven translation of the Silverstripe UI
* [translate.silverstripe.org] `http://translate.silverstripe.org`: Starting point for community-driven translation of the Silverstripe UI
* [i18n](i18n): Developer-level documentation of Silverstripe's i18n capabilities
* `[api:Translatable]`: DataObject-interface powering the website-content translations
* ["Translatable ModelAdmin" module](http://silverstripe.org/translatablemodeladmin-module/): An extension which allows
* ["Translatable ModelAdmin" module] `http://silverstripe.org/translatablemodeladmin-module/`: An extension which allows
translations of `[api:DataObject]`s inside `[api:ModelAdmin]`

16
docs/en/topics/widgets.md
View File

@ -2,8 +2,8 @@
## Introduction
[Widgets](http://silverstripe.org/widgets) are small pieces of functionality such as showing the latest Comments or Flickr Photos. They normally display on
the sidebar of your website. To check out a what a [Widget](http://silverstripe.org/widgets) can do watch the
[Widgets] `http://silverstripe.org/widgets` are small pieces of functionality such as showing the latest Comments or Flickr Photos. They normally display on
the sidebar of your website. To check out a what a [Widget] `http://silverstripe.org/widgets` can do watch the
[Widget video](http://silverstripe.com/assets/screencasts/SilverStripe-Blog-DragDrop-Widgets.swf) and try out the
[demo site](http://demo.silverstripe.org/)
@ -12,9 +12,9 @@ the sidebar of your website. To check out a what a [Widget](http://silverstripe.
### Downloading and Contributing Widgets
* To download widgets visit [Widgets section](http://silverstripe.org/widgets)
* To download widgets visit [Widgets section] `http://silverstripe.org/widgets`
* Upload widgets you want to share to
[http://silverstripe.org/widgets/manage/add](http://silverstripe.org/widgets/manage/add). Make sure you read the
`[http://silverstripe.org/widgets/manage/add]` `http://silverstripe.org/widgets/manage/add`. Make sure you read the
packaging instructions at the bottom of the page about how to make your widget package.
@ -281,7 +281,7 @@ widget forms in other controller subclasses, have a look at *ContentController->
*ContentController::$url_handlers*.
</div>
See an [alternative recipe for SilverStripe 2.3 or earlier](http://doc.silverstripe.org/old/recipes/widget-forms-2.3).
See an [alternative recipe for SilverStripe 2.3 or earlier] `http://doc.silverstripe.org/old/recipes/widget-forms-2.3`.
## But what if I have widgets on my blog currently??
@ -322,7 +322,7 @@ For a widget to be put in our official widget database they must follow this con
You should have a folder called widget_YourName in the top level (the one with sapphire, cms..) with all your files. See
the example below. Your widget **MUST** have at least 1 Template file, 1 PHP file, the README File
[(Example)](http://open.silverstripe.com/browser/modules/widgets/twitter/trunk/README)and an _config.php file for
[(Example)] `http://open.silverstripe.com/browser/modules/widgets/twitter/trunk/README` and an _config.php file for
configuration. If you dont need any config options for the widget to work then you still need an _config.php by you can
make it blank
@ -352,5 +352,5 @@ This way, the CMS remains an application designed for content authors, and not d
* Ensure when you "unzip" the compressed file it has everything the "widgets_YourName" folder with everything inside
it.
* If made official, it will be given these locations at silverstripe.com:
* SVN location: http://svn.silverstripe.com/open/modules/widgets/flickr/trunk
* Official download: http://www.silverstripe.com/assets/downloads/widgets/widgets_flickr-0.1.1.tar.gz
* SVN location: `http://svn.silverstripe.com/open/modules/widgets/flickr/trunk`
* Official download: `http://www.silverstripe.com/assets/downloads/widgets/widgets_flickr-0.1.1.tar.gz`

6
docs/en/tutorials/building-a-basic-site.md
View File

@ -474,7 +474,7 @@ things.
## Books on SilverStripe
* [Official book on SilverStripe in English](http://www.silverstripe.org/silverstripe-book).
* [Official book on SilverStripe in German](http://www.silverstripe.org/das-silverstripe-buch).
* [Official book on SilverStripe in English] `http://www.silverstripe.org/silverstripe-book`.
* [Official book on SilverStripe in German] `http://www.silverstripe.org/das-silverstripe-buch`.
![](_images/silverstripe-cms-book-front-cover-design-june2009preview.jpg)
![](_images/silverstripe-cms-book-front-cover-design-june2009preview.jpg)