A flexible framework for connecting other content sources to a SilverStripe site.
The External Content module forms a framework for displaying and migrating content from external sources.
<marcus (at) silverstripe (dot) com (dot) au>
Note: For a SilverStripe 2.4 compatible module, please check the 1.0.0 branch
This article assumes that you have installed the FileSystem Connector module, which provides access to content from a filesystem path.
A generic method for calling methods with parameters where the
method is actually found on a remote URL, and the return type of that method
call can be easily converted to an appropriate object. For example, imagine that
there is a "login" method that can be called on a particular URL with some
parameters, with an XML return type. A definition of this method would look like
'login' => array( 'url' => '/api/login', 'return' => 'xml', 'params' => array('u', 'pw'), 'cache' => false, ),
When the WebApiClient is created, it is passed a 'baseUrl' and a list of method
definitions like the above. Then, it is simply a matter of calling
$apiClient->call('login', array('u' => 'user', 'pw' => 'pass'))
and getting a SimpleXML object as the return type. This mechanism is used by
the AlfrescoSeaMistRepository, so refer to that module for further details.
If you're having trouble viewing pages when opening an ExternalContentPage
directly via the backend, make sure there's not two ? characters in the URL. The
SS backend assumes that a URL for an item won't have a URL in it, but at the
moment URLs are constructed in this way.
Module rating system helping users find modules that are well supported. For more on how the rating system works visit Module standards
Score not correct? Let us know there is a problem