[kupu-dev] Staging Addon 1.6.1 and Kupu

[Lynn Turner]

We recently installed Staging Addon 1.6.1 on our site to have staging/versioning
of our documents (pages) created in Kupu. We configured our workflow, which
works great, except for one thing, and I was hoping that you guys could help
out. I've created an issue on the Staging Addon project page (issue #32), but
suggested that I create a patch for the fix, which I don't have time to do, nor
the expertise to do...so I turn to you.
 
We have many documents on our site, most of which link to another (or multiple)
document inside the site. We have configured the workflow to archive the old
version of a document, when a new version of it has been published. However this
does not update all the internal links that pointed to the original document,
which means that we have to manually go into the site and update all the links
that pointed to the old version and redirect them to the new version.
 
The Staging Addon developers responded the following way: 
"I suppose that you use Kupu's "resolve uids" mechanism? Is that
right? If not, you should not have this problem.    For now,
StagingAddOn only swaps ids (hence the URLs) of the old version
and the new one upon publishing. To let Kupu's "resolve uid"
feature work, we should also swap their UIDs. I had not been so
keen to do that, until now.    However, we already change all
references from the old version to the new one. Changing the UID
would be very similar and actually achieve more than what we do
now. I may implement that, someday (though if you have a patch and
tests, I will happily use them)."
 
Do any of you know how I would "swap" UIDs (between versions) so that when we
publish the new version of a document that all links that pointed to the old
version are updated and point to the new version? Would anyone have suggestions
for creating that patch? Is there an easier way to do this?
 
Thank you very much for any help you may be able to provide!

 
 
 
 
 
sincerely, 
Lynn Turner
Research Support, Family History Dept.

----------------------------------------------------------------------
NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://codespeak.net/pipermail/kupu-dev/attachments/20070515/1cf30bec/attachment.htm