Content event handlers

The ImageVault addon connects to some of the existing CMS content event handlers to make sure any media references are published and for warming up media properties. These event handlers are written to be as non-blocking and performant as possible so they should not impact performance. For specific use cases, when it's certain you don't need them, they can be disabled through configuration.

Publishing Content

When CMS content is about to be published (PublishingContent), ImageVault will go through any long string properties in the content (recursively searching through any blocks in the published content as well) to identify any internal media URLs and publish them. For example, when working with TinyMCE properties in edit mode, ImageVault media that is inserted in the draft will use internal/protected URLs. Later when that content is published, this event handler updates any internal media URLs with corresponding public URLs and also updates the publishing information for the media.

Published Content

When CMS content has been published (PublishedContent), if the published content is a PageType, ImageVault will do a HTTP GET request to the newly published page. This triggers an update in ImageVault with publishing information for any media properties used, in order to see where media files are used. This request will also pre-populate cached media information, reducing API calls for future requests.

If you don't want this "ping back" you can disable the event handler by setting ImageVault:Optimizely:Common:DisablePingOnPublish to true. Note that this will delay any publishing information until the page gets its first request.

Disable all event handlers

For advanced use cases, all ImageVault content event handlers can be disabled by setting DisableContentEventHandlers to true.

Note: This should only be used when none of the above event handlers are required, for example if the TinyMCE ImageVault addon is disabled and the ping/warmup can be delayed until first page load.