[kupu-dev] Staging Addon 1.6.1 and Kupu

[Duncan Booth]

"Lynn Turner" <TurnerLC at ldschurch.org> wrote:

> 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!
> 
>  

I'm afraid I don't know anything about Staging Addon, at Oxfam we use Plone 
Multisite to provide staging (but not versioning) and that deliberately 
preserves uids specifically to avoid problems.

You (or the developer of staging addon) might be able to get somewhere by 
using the RefTextField type in kupu for your content types. That ensures 
(when you use uid linking) that you have genuine Archetypes references for 
all the objects linked from the kupu editable field. That should make it 
comparatively easy for the staging product to find affected documents and 
update them when it wants to change the uids.