The Dashboard module provides a splash page for the CMS in SilverStripe 4 with configurable widgets that display relevant information. Panels can be created and extended easily. The goal of the Dashboard module is to provide users with a launchpad for common CMS actions such as creating specific page types or browsing new content.
Images and videos about this module can be found in this blog post.
No included panels at the moment. These could be upgraded and brought back from the SS3 version of this module:
- Recently edited pages
- Recently uploaded files
- RSS Feed
- Quick links
- Section editor
- Google Analytics
- Weather
- Install the contents of this repository in the root of your SilverStripe project in a directory named "dashboard".
- Run /dev/build?flush=1
Dashboard panels have their own MVC architecture and are easy to create. In this example, we'll create a panel that displays recent orders for an imaginary website. The user will have the option to configure the panel to only show orders that are shipped.
First, create a class for the panel as a descendant of DashboardPanel. We'll include the database fields that define the configurable properties, and create the configuration fields in the getConfiguration() method.
mysite/code/RecentOrders.php
<?php
use SilverStripe\Forms\TextField;
use SilverStripe\Forms\CheckboxField;
class DashboardRecentOrdersPanel extends UncleCheese\Dashboard\DashboardPanel {
private static $db = [
'Count' => 'Int',
'OnlyShowShipped' => 'Boolean'
];
private static $icon = "mysite/images/dashboard-recent-orders.png";
public function getLabel() {
return _t('Mysite.RECENTORDERS','Recent Orders');
}
public function getDescription() {
return _t('Mysite.RECENTORDERSDESCRIPTION','Shows recent orders for this fake website.');
}
public function getConfiguration() {
$fields = parent::getConfiguration();
$fields->push(TextField::create("Count", "Number of orders to show"));
$fields->push(CheckboxField::create("OnlyShowShipped","Only show shipped orders"));
return $fields;
}
public function Orders() {
$orders = Order::get()->sort("Created DESC")->limit($this->Count);
return $this->OnlyShowShipped ? $orders->filter(['Shipped' => true]) : $orders;
}
}The panel object will look for a template that matches its class name.
mysite/templates/Includes/DashboardRecentOrdersPanel.ss
<div class="dashboard-recent-orders">
<ul>
<% loop Orders %>
<li><a href="$Link">$OrderNumber ($Customer.Name)</a></li>
<% end_loop %>
</ul>
</div>Run /dev/build?flush=1, and you can now create this dashboard panel in the CMS.
The best place to inject CSS and JavaScript requirements is in the inherited PanelHolder() method of the DashboardPanel subclass.
mysite/code/DashboardRecentOrdersPanel.php
<?php
public function PanelHolder() {
Requirements::css("mysite/css/dashboard-recent-orders.css");
return parent::PanelHolder();
}The Dashboard module comes with an API for creating charts using the Google API.
mysite/code/DashboardRecentOrdersPanel.php
<?php
public function Chart() {
$chart = DashboardChart::create("Order history, last 30 days", "Date", "Number of orders");
$result = DB::query("SELECT COUNT(*) AS OrderCount, DATE_FORMAT(Date,'%d %b %Y') AS Date FROM \"Order\" GROUP BY Date");
if($result) {
while($row = $result->nextRecord()) {
$chart->addData($row['Date'], $row['OrderCount']);
}
}
return $chart;
}mysite/code/DashboardRecentOrdersPanel.ss
$ChartYou can create your own templates for either of these panel types which will override the default templates. Due to the naming structure the custom templates will be specific to that partiular panel, thus you can have a seperate template for each ModelAdmin / GridField panel.
You can access all the properties of your model in the template as normal along with a EditLink method which will contain the CMS edit link for that item.
For model admin panels, create a templated called DashboardModelAdminPanel_ModelAdminClass_ModelAdminModel.ss and place it in your mysite/templates/Includes folder. eg; DashboardModelAdminPanel_MyAdmin_Product.ss
A gridfield panel uses a similar convention, DashboardGridFieldPanel_PageClassName_GridFieldName.ss
eg; DashboardGridFieldPanel_ContactPage_Submissions.ss
You need to add your Google Analytics config information to the project config.yml:
DashboardGoogleAnalyticsPanel:
email: [XXXXX]@developer.gserviceaccount.com
profile: 123456
key_file_path: google_oauth.p12 To locate your profile ID, visit the Google Analytics website, login and select the website. At the end of the URL will be fragment similar to this:
#report/visitors-overview/a5559982w55599512p12345678
/a[6 digits]w[8 digits]p[8 digits]
The 8 digits that follow the "p" are your profile ID. In the example above, this would be 12345678.
NOTE: To use the Google Analytics panel, you have to enable access for less secure apps in the account permissions section of https://www.google.com/settings/security.
For more information about settting up a developer account and obtaining a key file, visit https://github.com/erebusnz/gapi-google-analytics-php-interface#instructions-for-setting-up-a-google-service-account-for-use-with-gapi
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent