When a post is cloned the source ( master ) stores the IDs of the target post in post meta data keyed by _oik_clone_ids.
Information is stored for each target server
While this indicates whether or not the post has been cloned, it doesn't indicate whether or not the cloned version is out of date with respect to the source.
We need to store the update time as well.
Then, after the source has been updated, we can tell which targets have also been updated.
This information is required in order to be able to clone sets of updates... the complete network of posts that are required to produce consistent content and links.
Proposed solution
Store the update time as a Unix timestamp indicating the time the update was performed. This may be later than the last modified date of the post.
This value is to be passed to the server and stored in the targets post meta data.
When a post is cloned the source ( master ) stores the IDs of the target post in post meta data keyed by _oik_clone_ids. Information is stored for each target server
While this indicates whether or not the post has been cloned, it doesn't indicate whether or not the cloned version is out of date with respect to the source. We need to store the update time as well. Then, after the source has been updated, we can tell which targets have also been updated. This information is required in order to be able to clone sets of updates... the complete network of posts that are required to produce consistent content and links.
Proposed solution
Store the update time as a Unix timestamp indicating the time the update was performed. This may be later than the last modified date of the post. This value is to be passed to the server and stored in the targets post meta data.