Download the PHP package silverware/model-filters without Composer
On this page you can find all versions of the php package silverware/model-filters. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download silverware/model-filters
More information about silverware/model-filters
Files in silverware/model-filters
Package model-filters
Short Description SilverWare Model Filters Module.
License BSD-3-Clause
Homepage https://github.com/praxisnetau/silverware-model-filters
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 model-filters
SilverWare Model Filters Module
Extends the SilverStripe v4 ModelAdmin to support filtering of versioned data objects.
Contents
- Background
- Requirements
- Installation
- Usage
- Issues
- Contribution
- Maintainers
- License
Background
Traditionally, versioning in SilverStripe has been the sole domain of
SiteTree objects within the CMS, such as the ubiquitous Page class.
With the advent of SilverStripe v4, versioning is now used in
other areas of the CMS, such as assets.
You can add versioning to your own model classes by using the
Versioned extension. ModelAdmin supports
versioned data objects out of the box, however filtering these objects
by their status is a bit trickier.
Enter silverware/model-filters. After installation of this module,
your versioned data objects will have a status dropdown field added to
the filter form that appears within ModelAdmin, allowing the user
to filter records by their versioning status:
You can also add StatusBadges to your $summary_fields to show
the versioning status within your model admin grid field:
Requirements
Installation
Installation is via Composer:
Usage
Once installed, Versioned data objects within ModelAdmin will
be automatically detected and a status field will appear within
the filter form for each object.
In order to show status badges within the grid field for your
versioned objects, simply add StatusBadges to your $summary_fields static,
for example:
Status Field Positioning
By default, the status dropdown field will be added to the end of
your search filter fields for each versioned object. To control
where the field appears, add one of the following methods to
your ModelAdmin subclass:
You could also detect the current model class via $this->modelClass and answer a
different field name, if required:
Status Field Title
By default, the title of the status dropdown field is "Record status". The title
is obtained by calling getStatusFieldTitle() on the ModelAdmin subclass. The method
added via the extension supports i18n via the usual SilverStripe
conventions, however you can also override the method in your
ModelAdmin subclass to answer a different field title:
Issues
Please use the GitHub issue tracker for bug reports and feature requests.
Contribution
Your contributions are gladly welcomed to help make this project better. Please see contributing for more information.
Maintainers
 |
 |
|---|---|
| Colin Tucker | Praxis Interactive |
License
BSD-3-Clause © Praxis Interactive
All versions of model-filters with dependencies
silverstripe/admin Version ^1.0
silverstripe/framework Version ^4.0
silverstripe/versioned Version ^1.0