Bridge for Kapost driven content authoring, provides support for basic content pages. But also provides a flexible api to allow for custom content types.
- Ed Chipman (UndefinedOffset)
- SilverStripe Framework 3.1+
- phpxmlrpc ~4.0
composer require webbuilders-group/silverstripe-kapost-bridge
If you prefer you may also install manually:
- Download the module from here https://github.com/webbuilders-group/silverstripe-kapost-bridge/archive/master.zip
- Extract the downloaded archive into your site root so that the destination folder is called kapost-bridge, opening the extracted folder should contain _config.php in the root along with other files/folders
- Run dev/build?flush=all to regenerate the manifest
- Download phpxmlrpc's latest ~4.0 release and include in your SilverStripe install note that since you're installing manually you may run into some issues.
The documentation for the module (including how to add custom types and the extension points) can be found here.
The Publish Twice Rule (Kapost Analytics)
In order for Kapost Analytics to work properly you need to have the full url. Unfortunately since we cannot know the end published url before the Kapost Object is converted (or the url changes because of the changes in Kapost) we need to publish from Kapost again after you convert the object in SilverStripe. This will allow SilverStripe to let Kapost know the next time it tries to publish what the actual published url is from SilverStripe instead of the cms url. Technically you could also simply update the url in Kapost as well instead of publishing again after converting but if you do it does not change automatically with the next publish.
KapostAdmin: extra_conversion_modes: (empty) #Array of name's for extra conversion modes (see documentation for information on how to define these) kapost_base_url: null #Set this to a string of the base url for your Kapost account for example https://example.kapost.com/ KapostService: check_user_agent: true #If set to true when the service is called the user agent of the request is checked to see if it is Kapost's XML-RPC user agent authenticator_class: "MemberAuthenticator" #Authenticator to be used for authenticating the Kapost account authenticator_username_field: "Email" #Field the authenticator is expecting the username to be in kapost_media_folder: "kapost-media" #Assets folder to place the Kapost attached media assets duplicate_assets: "snart_rename" #What to do with duplicate assets valid options smart_rename, rename, overwrite, ignore see bellow for more information preview_token_expiry: 10 #Preview token expiry window in minutes, once this time elapses the Kapost content author must click preview again or they will receive a 404 message on the site. preview_data_expiry: 20 #Preview data expiry window, time in minutes that the preview's data lasts in the database. This time window is approximate as data can live past this point as the clean up happens when a conversion completes or when a new object arrives. database_charset: "UTF-8" #This should be set to the encoding for the database connection you are using. Matching this to your database connection character set will give the best chance of no encoding issues. By default it is set to the default MySQLDatabase.connection_charset value which is UTF-8. filter_kapost_threads: false #The default HTML content field in Kapost allows for inline commenting, this flag allows for toggling of filtering out the html flag for Kapost's WYSIWYG. KapostConversionHistory: expires_days: 30 #Number of days that conversion history records are kept
Making Pages Managed through Kapost Readonly
In some cases you may want to have the Page editing section of the cms have pages marked as readonly when their content came from Kapost. There are are a couple of fields by default that are made editable URL Segment and Extra Meta Additional fields you want editable by the cms admin can be added to the config option
YourPageType.non_readonly_fields. As well Kapost includes a script tag in any WYSYWIG field to avoid confusing your analytics in Kapost and any potential collisions with the CMS's UI you should make any HTML fields safe via the config option
YourPageType.make_safe_wysiwyg_fields by default the Content field is included. To enable the readonly conversion on the CMS's page editing section you need to add the bellow to your config. Note this only applies to the Content tab, the Settings tab is unaffected.
CMSPageEditController: extensions: - "KapostPageEditControllerExtension"
In addition you can also make the page's settings readonly by adding the
KapostPageSettingsControllerExtension extension to the
CMSPageSettingsController. By default only CanViewType, ViewerGroups, CanEditType, and EditorGroups are editable if this extension is applied. If you want to whitelist additional fields as editable in the cms add the field's name to the
YourPageType.non_readonly_settings_fields configuration option for your page type.
CMSPageSettingsController: extensions: - "KapostPageSettingsControllerExtension"
Handling Duplicate Assets
Kapost sends an attached asset everytime a page is published, so there are three options for handling files with a duplicate name under the KapostService.duplicate_assets configuration option.
smart_renameVerifies the file is the same as the existing file and instead uses that file using a sha1 hash of both the incoming and existing file, otherwise it renames the file to make it unique.
renameRename the asset until a unique name is found.
overwriteOverwrite the existing file with the new file, _be warned you may end up overwriting an asset you don't want overwritten.
ignoreThe service simply ignores the asset and tells Kapost that there was an error explaining to rename the file and try again.