Download the PHP package heyday/silverstripe-slices without Composer
On this page you can find all versions of the php package heyday/silverstripe-slices. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download heyday/silverstripe-slices
More information about heyday/silverstripe-slices
Files in heyday/silverstripe-slices
Package silverstripe-slices
Short Description Provides a Slice extension to DataObject subclasses with custom templates
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package silverstripe-slices
Content Slices for SilverStripe
Content management in "slices" configured via YAML; separate content components, each with their own template, fields and visual settings that can be created and arranged by a user in the CMS.
- Usage
- Templates
- Adding Slices to Page
- Subclassing Slice
- Using Slices on a sub class of a Page/SiteTree
- Customising CMS fields
- Example config
- Compatibility
Usage
It's best to use silverstripe-slices with lots of generic fields on the base slice class, since this allows templates to share fields and be configured in YAML without creating a class for each slice. silverstripe-adaptivecontent works well for this (and used to be integrated with this module).
Templates
Each slice type/template has it's own template file with the name [BaseSliceClass]_[TemplateName]. These should go in themes/[theme]/templates/[MyProject]/DataObjects/Slices to separate them from the other templates in your site.
Adding Slices to Page
This module comes with an extension for easily setting up Slices on Page:
In templates, all slices can be rendered using this:
Subclassing Slice
Subclassing Slice is a normal use case, however note that when subclassing it, you'll need to override the method getBaseSliceClass method in your "base" slice subclass (the one you point to in a has_many from Page) for the slice to save correctly:
This is due to the the module needing a "default" class to fall back to when the className key has not been set in a template config.
You also need to extends the Extension
And update the configuration accordingly.
Using Slices on a sub class of a Page/SiteTree
In case you want to use the slices on a custom page type, you will also need to override the has_one relation to match your sub class.
Let's say you have a custom page type named GenericPage.
You need to add the following Extension:
Then udpate the configuration:
Customising CMS fields
Adding and modifying fields in YourBaseSlice::getCMSFields is an expected use case. Note that things configured in the slices YAML configuration will be overriden if, for example, you replace a field with something custom. In this case, you can re-apply the slices config with the following at the end of your getCMSFields function:
Example config
Compatibility
This module requires at least SilverStripe 4 and PHP 5.6.
