Useful when you need to name credits, licence and source links for any asset used on your SilverStripe site.

https://github.com/ivoba/silverstripe-file-credits
https://packagist.org/packages/ivoba/silverstripe-file-credits
https://addons.silverstripe.org/add-ons/ivoba/silverstripe-file-credits

Deprecated: SilverStripe\Config\Collections\MemoryConfigCollection implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /var/www/html/vendor/silverstripe/config/src/Collections/MemoryConfigCollection.php on line 13

Unfortunatly we can’t control the error_reporting from SilverStripe since it is set in the kernel of the framework.
So we are forced to hack the Kernel which is rather unfortunate.

In the SilverStripe Slack channel someone proposed to use composer-patch which will apply a patch to a given vendor dependency during composer install.
This is quite cool because you don’t need to fork the dependency and take care of getting upstream changes.

So i went this path down and it looks like in this gist:
https://gist.github.com/ivoba/d8c4379236149a8c42e1922ae98a93e3

Basically you have to install composer patch:

composer require cweagans/composer-patches

Create the patch and add the patch file to your project.
You can create a patch by cloning the package i.e. silverstripe/framework into IntelliJ / PHPStorm, apply the change and under Git -> Patch create the patch file.

Then add it to composer.json so the patch can be applied on next composer install.

"extra": {
       "patches": {
            "silverstripe/framework": {
                "Fix SilverStripe deprecations error_reporting for PHP 8.1": "./fix-deprecation-error_reporting.4.10.4.patch"
            }
       }
    }

Now we have patched the error_reporting and the deprecation warnings are supressed.
Once SilverStripe fully supports PHP8.1 we then can remove this patch.

php -S localhost:8000 ./framework/main.php

Now you can call http://localhost:8000 to check your SilverStripe website.

Or, a bit more verbose, use https://github.com/assertchris/silverstripe-serve
which is a nice wrapper around this.

In case you also need a vanilla database with default pages, you can add the environment file in mysite/_config.php:

require_once('conf/ConfigureFromEnv.php');

create the file ./_ss_environment.php:

define('SS_DATABASE_SERVER', 'localhost');
define('SS_DATABASE_USERNAME', 'root');
define('SS_DATABASE_PASSWORD', '');
define('SS_DATABASE_NAME', 'SS_Mysite');
define('SS_DEFAULT_ADMIN_USERNAME', 'admin');
define('SS_DEFAULT_ADMIN_PASSWORD', 'admin');

and run in the console:

framework/sake dev/build flush=1

If your user is allowed to create databases (for dev purposes on the local machine i simply use the root user) you will now have a new database with default pages.

When the project gets into serious development phase i would recommend to setup a real environment setup with apache/nginx with f.e docker. (Post on this is coming soon :))

Its the missing LinkField, you might look for.
There are some more addons for a LinkField out there, but this one is the best.
No wonder, the author is SilverStripe employee.

It features:

• external links
• link validation
• link a page from your site
• link a file from your assets
• oEmbed links
• the addon is translated, currently only for german, but add your own, its easy!

Handling in the backend is very comfortable as you can see here:

It took me some time to evaluate all LinkField addons and to find the right one, so maybe it saves you some time.

Integrating the Blog in Silverstripe (which indeed would have made things simpler) was not  an option at the time. The usage of loads of WordPress plugins would’ve made a rewrite a major task, which was out of the budget.

The blog was integrated in the same page layout as the rest of the website. So ideally it would at least share the same Templates for header, footer etc. and would integrate the sites navigation built by Silverstripe.

But how to use the pre-rendered Silverstripe template .ss files in a WordPress theme?

The following worked fine for me, using Silverstripe 3.0:

In the functions.php of the wordpress theme i added this code to init a silverstripe controller:

//init silverstripe
require_once '[path-to-silverstripe-root-folder]/framework/core/Core.php';
require_once '[path-to-silverstripe-root-folder]/framework/model/DB.php';
//init the Database connection
DB::connect($databaseConfig);
//fetch some page, it that case i used the 404 ErrorPage
$SSPage = DataObject::get_by_id('Page', 4);
//init a the controller and cache it as a global variable
$SSctrl = new ContentController($SSPage);
//add the controller to the stack, so it becomes available as the current controller for the template
$SSctrl->pushCurrent();

and also some helper functions to get the actual templates

function get_Silverstripe_Header()
{
    global $SSctrl;
    //render the controller with the includes/Header.ss template
    return $SSctrl->renderWith('Header');
}

function get_Silverstripe_Footer()
{
    global $SSctrl;
    //..or any other template, like the footer
    return $SSctrl->renderWith('Footer');
}

…and then just use these in the templates:

<?php echo get_Silverstripe_Header() ?>

Of course this is no way limited to WordPress. It just an idea how to access Silverstripe Templates outside of Silverstripe code.

So here are some more as a JSFiddle:

http://jsfiddle.net/HMkad/2/embedded/result/

If you’d like to extend the collection just edit the markup in the fiddle.
And add something like this:

<li>
  <p>
    <strong>?showqueries=1</strong> - List all SQL queries executed
  </p>
  <a data-param="showqueries=1" href="#">
    SS:showqueries=1
  </a>
</li>

…or this:

 <li>
   <p>
    <strong>dev/build</strong> - Rebuild the entire database and manifest
   </p>
   <a data-param="dev/build" href="#">
     SS:dev/build
   </a>
</li>

Have fun!

If you want to rename a menu item in the SilverStripe Admin Area, because f.e. you find “Security” or “Sicherheit”(since we are german ;)) a too harsh wording and you prefer “Members” or “Benutzer”:
simply override the translation!

Add a lang folder in your project folder and add the language file:
de.yml or en.yml and place your wording:

de:
  SecurityAdmin:
    MENUTITLE: Benutzer

Flush the cache, call the admin area again and you will see the menu item with changed wording.

Thanx to UndefinedOffset from IRC for the advise :)

In SilverStripe 2.4 overriding language files doesnt seem to work.
What you can do here is remove & add the menu item via config:

CMSMenu::remove_menu_item('SecurityAdmin');
CMSMenu::add_menu_item('SecurityAdmin','Benutzer','admin/security/');

Taken from the comments here: http://www.ssbits.com/snippets/2009/removing-an-item-from-the-main-cms-menu/

So we consider them as almost “readonly” sites.

These sites you can easily speed up “dramatically” with the SilverStripe builtin StaticPublisher.
The tweaks you need for this are moderate to easy.

You can read the Docs to get a glimpse of what is possible.
I will just describe the basic setup to make a site static.

Add this to your Page.php, this will tell SilverStripe what do export to the static cache:

/**
     * Return a list of all the pages to cache
     */
    public function allPagesToCache() {
        // Get each page type to define its sub-urls
        $urls = array();

        // memory intensive depending on number of pages
        $pages = SiteTree::get();

        foreach ($pages as $page) {
            $urls = array_merge($urls, (array) $page->subPagesToCache());
        }

        return $urls;
    }

    /**
     * Get a list of URLs to cache related to this page
     */
    public function subPagesToCache() {
        $urls = array();

        // add current page
        $urls[] = $this->Link();

        return $urls;
    }

Add this to your _config:

Object::add_extension("SiteTree", "FilesystemPublisher('silverstripe-cache/static/', 'html')");

I placed the cache folder in the cache dir since its already writeable and can be cleared via flush.
But this you can define yourself.
— But notice if you change this path, you also have to change $cacheBaseDir in framework/static-main.php!

Now we can fill up the cache:

http://www.example.com/dev/buildcache?flush=1

EDIT: The below part can be skipped, if you use the method pagesAffectedByChanges(), see comments below.
———————

A bit of a downside is that after you have altered the content in your backend you have to refresh your cache via the above build command.
This might be too much for a client to remember.
There for you could override the admin template:
cms/templates/Includes/CMSPagesController_ContentToolActions.ss
and add a button to call this command.

<div class="cms-actions-row">
        <a href="/dev/buildcache" target="_blank" class="ss-ui-button ss-ui-action-constructive" style="float: right">StaticPublisher</a>
	<a class="cms-page-add-button ss-ui-button ss-ui-action-constructive" data-icon="add" href="$LinkPageAdd" data-url-addpage="{$LinkPageAdd('?ParentID=%s')}"><% _t('CMSMain.AddNewButton', 'Add new') %></a>
</div>

See:

Sometimes you have to remove a customScript of a module, because you want to script it differently.

If the module author was so wise to give his customScript a ID (UserFormsValidation in this case) like they did in UserForms:

Requirements::customScript(<<<JS
    (function($) {...})(jQuery);
JS
, 'UserFormsValidation');

then you can do the following in the init function of your subclass controller:

Requirements::block('UserFormsValidation');

Easy, isnt it?

Thats great, but it has some caveats, which i like to describe while introducing the silverstripe opengraph module by Damian Mooyman.

The module is pretty well done and delivers most content prefilled. So just install it and the rest comes automatically through the $MetaTags var in your template.
In the backend you can insert some information like locality and your facebook app id.

You should further add a default 200x200px image in your config:

OpenGraphPageExtension::$default_image = '/themes/myTheme/images/og_image.png';

and add the opengraph namespace var in your html tag:

<html lang="en" $OGNS>

Thats basically it, wow!

But of course you have to do some finetuning to represent your content best.
So these questions you should ask yourself for each site where you would like to implement the metatags:

Why should you use opengraph metatags?
To have control over the content of the sharer snippets.

Where should you use opengraph metatags?
Where you can control / predict the content.
Its not always a good idea to preselect the image.
F.E when you have RichText HTML Field where the Content Manager can insert images. Then those images might be good to be shared.
But with a preselected image via the og:image tag, the facebook share box will not list the other images.
So on some pagetypes it might be better to not use the og tags and let the facebook parser do its dirty work.
This you can achieve with overwriting the getOGType function in your pagetype:

NonOGPage extends Page
{
    function getOGType() {
        return null;
    }
}

(thanx Damian)

How should you use it?
Treat your content right. So if you have a structured page type, think of which content fits and overwrite the resp. function of the module to serve the content you would like to see.
F.E. if you have multiple images and you want the user to choose from while in the share dialog then do something like that:

PageWithImages extends Page {
     function OGImage() {
        $imgs = array();
        if ($this->Images()) {
            $images = $this->Images();

            foreach ($images as $value) {
                $og_img = $value->Thumb()->CroppedImage(200, 200);
                $imgs[] = $og_img->Url;
            }
        }
        if(empty($imgs)){
            $imgs[] = Director::absoluteURL(OpenGraphPageExtension::$default_image);
        }
        return $imgs;
    }
}

Who uses the opengraph metatags?
– Facebook of course.
– Google+ seems to prefer schema.org annotation but uses opengraph as fallback and then meta tags and then content.
– Pinterest also seems to use it, partly.
Here is a interesting discussion about it:
http://stackoverflow.com/questions/6536213/are-there-tags-to-specify-the-google-1-story-format-in-google-like-og-meta-for
– and probably some more…

And at last here is the facebook debug tool to check your opengraph contents.