Social media sharing previews and customisation for Silverstripe

Fund package maintenance!

Installs: 27 964

Dependents: 1

Suggesters: 0

Security: 0

Stars: 29

Watchers: 6

Forks: 11

Open Issues: 7


v4.2.2 2024-04-02 19:07 UTC

This package is auto-updated.

Last update: 2024-05-02 19:23:32 UTC


When URLs are shared on social media a rich preview of the content may be generated to give the URL context. The goal of this module is to encourage CMS users to be aware of how their content will appear when shared, and give them tools to customise this appearance.

CMS Preview Example



See the Packagist listing and composer installation instructions.

  1. $ composer require jonom/silverstripe-share-care
  2. Flush manifests by visiting /dev/build

How to use

View rich share previews in the CMS

With the module installed you should find a Share tab on all pages which shows you roughly what each page will look like when shared on social media. The preview is based upon the output of the Opengraph module, so your configuration of that module will be reflected here.

To add share previews to other DataObject classes, just add the ShareCare extension to them. Example:

Name: mysharecare
After: 'opengraphextensions'
    - JonoM\ShareCare\ShareCare

See the Silverstripe documentation for more info on extensions.

Customise the appearance of content on social media

You can configure the Opengraph module to generate open graph tags however you like, and this is what controls the appearance of rich previews on social media (especially Facebook and Twitter). To quickly configure the Opengraph module to allow CMS users to customise the content and appearance of these previews, just add the ShareCareFields extension to your Page class (and any other classes you like).

Field example

Example configuration:

Name: mysharecare
After: 'opengraphextensions'
    - JonoM\ShareCare\ShareCareFields

This allows CMS users to customise the image, title and description that are shown when a URL is shared on social media. You can further tweak these behaviours by overriding functions on your classes. For example if each page on your website already contains a Hero Image, you may want to override getDefaultOGImage() to use this as the default image:

 * Provide a better default OG image for pages
public function getDefaultOGImage() {
	// Use hero image if available
	if ($this->HeroImageID) {
		return $this->HeroImage();
	// Fallback to website's apple-touch-icon
	if (file_exists(BASE_PATH . '/apple-touch-icon.png')) {
		return Director::absoluteURL('apple-touch-icon.png', true);

Note that og:image is a required property, so please ensure that getDefaultOGImage() will always work. If your website includes an apple-touch-icon.png file in the root you'll be covered.

Don't need that much control?

As an alternative to the ShareCareFields extension, try taking the ShareCareSingleSummary extension for a spin. This opinionated extension lets CMS users choose a single image and a single summary to be used to represent a page within the website and on search engines and social media. It puts the fields front and centre above the main content field to encourage CMS users to actually fill them out. As a bonus it also hides that pesky 'custom meta tags' field away in the Settings tab.

Summary fields

Example configuration:

Name: mysharecare
After: 'opengraphextensions'
    - JonoM\ShareCare\ShareCareSingleSummary

Twitter integration

Markup for a large image summary Twitter card will be included if a large enough image is provided. To attribute content ownership set a Twitter username in your config.yml file. Example:

  twitter_username: 'your-username'

Don't want Twitter card markup? Disable it like so:

  twitter: false

Note that Twitter will still use your open graph tags to produce a rich preview if this feature is disabled.

Control Facebook's Cache

Out of the box, this module will attempt to clear Facebook's knowledge of your site or app, after every page write. You will probably need a Facebook access token for this functionality to work (it used to be optional but now seems to be required).

See the facebook access token docs entry for instructions on obtaining and using the token.

Opt out of Facebook cache clearing

You can opt out through the config system or object methods.

Use the following config to only attempt to purge the Facebook cache on live environments.

  enable_facebook_cache_clear: false
    - live
  enable_facebook_cache_clear: true

If you need more control you can provide a doClearFacebookCache() method on your Page or DataObject class to return true or false as necessary. You may want to return the value of Config::inst()->get('JonoM\ShareCare\ShareCare', 'enable_facebook_cache_clear') as a fallback.

Share links

You can use these methods in your templates to get a convenient share URL for each service

  • $FacebookShareLink
  • $TwitterShareLink
  • $PinterestShareLink
  • $LinkedInShareLink
  • $EmailShareLink

Pinterest CMS integration

If you're making use of the ShareCareFields extension and $PinterestShareLink, you can include a Pinterest preview in the CMS and allow CMS users to set a different image for Pinterest, as tall rather than wide images are better suited to this service.

  pinterest: true

Maintainer contact

Jono Menz


If you want to boost morale of the maintainer you're welcome to make a small monthly donation through GitHub, or a one time donation through PayPal. ❤️ Thank you!

Please also feel free to get in touch if you want to hire the maintainer to develop a new feature, or discuss another opportunity.