Related Links
You can download PDF versions of the Content Contributor's, Administrator's, and Elements Reference documents from the support section of paperthin.com (requires login).
For technical support:
The replication process contains the following “hooks” or events for executing custom code when a particular step in the replication process (from both the authoring and target server perspective) completes.
Pre-Synchronization - CommonSpot looks in the root of your site for a file named: replication-pre-sync.cfm. If this file exists, commonspot includes it (via a cfmodule call with no attributes) right before the replication job synchronizes the target server (determines the status of the target server and the timestamp for the last replication process).
Post-Synchronization – CommonSpot looks in the root of your site for a file named replication-post-sync.cfm. If this file exists, CommonSpot includes it (via a cfmodule call with no attributes) right after the replication job synchronizes the target server but before it actually begins the packet creation process.
Pre-Transport – After CommonSpot creates the packet, and right before it begins the transport process to the target server, it looks in the root of your site for a file named: replication-pre-transport.cfm. If this file exists, it is included (via cfmodule with no attributes).
Post-Transport – After CommonSpot sends the packet to the target server, but before it instructs the target server to apply the packet, CommonSpot looks in the root directory for a file named: replication-post-transport.cfm. If the file exists, it is included (via cfmodule with no attributes).
After Replication – Once the replication process completes on the Authoring server, CommonSpot looks for the file after--replication.cfm (note double dashes) in the root of your site. If this file exists, CommonSpot executes it. The module is called through a cfmodule call with the following attributes
SiteName- The name of the site just replicated
ScopeID – The scope id for the replication process just completed
ReplicationOK – Boolean, whether or not replication completed
ReplicationErrMsg – The message appended to the replication log file
ErrorStatus – Status code for replication failure
Related Links
You can download PDF versions of the Content Contributor's, Administrator's, and Elements Reference documents from the support section of paperthin.com (requires login).
For technical support: