Opengraph module for Silverstripe
This module provides a complete implementation of each of the Open Graph types as documented at http://ogp.me/, (*1)
Open Graph object types may be applied to any Page or DataObject by applying the appropriate interface., (*2)
For instance, if your page represents a music album you would implement the IOGMusicAlbum interface., (*3)
By default, the module will attempt to classify pages as the og:website type, and automatically
generate appropriate meta tags for it. This is all that most websites require to adequately interact
with Facebook., (*4)
Credits and Authors
Requirements
Installation Instructions
composer require "tractorcow/silverstripe-opengraph" "4@dev"
- Ensure the namespace is defined in your template with
<html $OGNS>
- If you need to add a prefix attribute to the
<head /> tag then you should do this directly
in your template.
- If you are working with video files, you might want to install https://github.com/tractorcow/silverstripe-mediadata
alongside this to extract video dimension for opengraph tags.
Configuration
The main configuration options for this module can be found in OpenGraph.yml., (*5)
Override these in your own mysite/_config/OpenGraph.yml or mysite/_config.php, (*6)
---
Name: myopengraphsettings
After: '#opengraphsettings'
---
TractorCow\OpenGraph\OpenGraph:
application_id: 'SiteConfig'
admin_id: 'SiteConfig'
default_locale: 'en_US'
default_tagbuilder: 'TractorCow\OpenGraph\ObjectBuilders\OpenGraphBuilder'
- Set application_id to either
SiteConfig (to be set in the CMS) or a literal facebook app id
- Set admin_id to either
SiteConfig (to be set in the CMS) or a literal facebook admin_id
- The default_locale is the literal value to use as the locale tag (if i18n doesn't have a locale set)
- The default_tagbuilder is the name of the class to use to generate tags (unless a type has one
specified explicitly). See below under [Adding new types, [^adding-new-types]] for details.
Any value above can be set to an empty string to disable it completely. E.g., (*7)
---
Name: myopengraphsettings
After: '#opengraphsettings'
---
TractorCow\OpenGraph\OpenGraph:
application_id: ''
admin_id: ''
How to do stuff
Implementing Open Graph object properties
To get specific information on each of the fields an opengraph object can have, check
out the various implementations of each in the src/Interfaces/ObjectTypes folder,
or in the _config/OpenGraphTypes.yml file for the list of
types and their respective interfaces., (*8)
The basic opengraph object has a set of required properties (as defined by
TractorCow\OpenGraph\Interfaces\ObjectTypes\IOGObjectRequired)
and additionally a set of optional properties (as defined by TractorCow\OpenGraph\Interfaces\ObjectTypes\IOGObjectExplicit)., (*9)
Since most of the field values are generated by the page extension class OpenGraphPageExtension
automatically, you don't need to explicitly implement either of these. These should however
should be used as a guide to what can be specified., (*10)
For example, if you wanted to override the getOGImage property (og:image meta tag) you would implement the
following in your page classe:, (*11)
class MyPage extends Page {
function getOGImage() {
return $this->Thumbnail();
}
}
By implementing these properties explicitly in your page classes, you can override the default properties
defined in the OpenGraphPageExtension., (*12)
Setting open Graph default image
The Open Graph image is a required property and should be supplied a default image.
You can set the path to the default image in the yml config, (*13)
TractorCow\OpenGraph\Extensions\OpenGraphObjectExtension:
default_image: 'app/images/logo.png'
theme_name_default_image: 'app/images/theme-logo.png'
Note that you can specify a different image for each theme by prefixing the default_image config name with the theme name (replace everything that is not a letter with an _).
This is useful if you want to set a different default image on sub sites., (*14)
Adding new types
If you wish to add a new og:type you will need to:
* Create an interface that extends IOGObject that defines the fields (if any)
that your object will publish
* Extend the OpenGraphBuilder class and override the BuildTags function
to generate the actual HTML for the tags in your interface
* Implement your interface on pages of the new type
* Register your object type with the following code:, (*15)
TractorCow\OpenGraph\OpenGraph::register_type('type-name', IOGMyObjectInterface, MyObjectTagBuilder);
Or better still, do this directly in yaml as below, (*16)
TractorCow\OpenGraph\OpenGraph:
types:
'type-name':
interface: IOGMyObjectInterface
tagbuilder: MyObjectTagBuilder
Creating a custom tag builder
In order to add an opengraph meta tag to your page, you need to write the code that
describes how to translate an object into a piece of html. This can be done by
implementing this in PHP with a TagBuilder object., (*17)
Note that there are two objects for every request; The entity being viewed (Page or DataObject)
and the application (SiteConfig). Each has their own set of tags., (*18)
E.g., (*19)
class MyObjectTagBuilder extends OpenGraphBuilder {
public function BuildTags(&$tags, $object, $config) {
parent::BuildTags($tags, $object, $config);
$this->appendTag($tags, 'appnamespace:nameofthetag', $object->getOGNameOfTheTag());
}
}
Our interface might look something like, (*20)
interface IOGMyObjectInterface extends IOGObject {
function getOGNameOfTheTag();
}
You can decorate the OpenGraphBuilder object instead of extending it if you need
to add additional tags to all object types., (*21)
The example below shows how to add extra fields from the Page and SiteConfig
to the set of OpenGraph tags., (*22)
TractorCow\OpenGraph\ObjectBuilders\OpenGraphBuilder::add_extension('OpenGraphBuilderExtension');
class OpengraphBuilderExtension extends Extension {
function updateApplicationMetaTags(&$tags, $siteconfig) {
$this->owner->AppendTag($tags, 'og:application-name', $siteconfig->Title);
}
function updateDefaultMetaTags(&$tags, $page) {
$this->owner->AppendTag($tags, 'og:page-menu-name', $page->MenuTitle);
}
}
Disabling Open Graph for a single page (or page type)
If you need to disable Open Graph for any page then a null value for getOGType()
will disable tag generation., (*23)
NonOGPage extends Page {
function getOGType() {
return null;
}
}
Using DataObjects as pages
See https://github.com/tractorcow/silverstripe-opengraph/wiki/Using-DataObjects-as-Pages
for how to extend your DataObject with TractorCow\OpenGraph\Extensions\OpenGraphObjectExtension., (*24)
- Add the
TractorCow\OpenGraph\Extensions\OpenGraphObjectExtension extension to your object
- Implement
AbsoluteLink on your object
- Implement
MetaTags on your object, making sure to call $this->extend('MetaTags', $tags);
- Make sure the actual page type being viewed delegates the meta tag generation to your dataobject
Need more help?
Message or email me at damian.mooyman@gmail.com or, well, read the code!, (*25)
License
Copyright (c) 2013, Damian Mooyman
All rights reserved., (*26)
All rights reserved., (*27)
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:, (*28)
- Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
- The name of Damian Mooyman may not be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE., (*29)
Apologies
I went a bit crazy with this module! Good old interfaces eh?, (*30)
Wallogit.com
