Block component update

Hi,

Is it possible to block component update in certain set of pages?

If so how can we do this?

Thanks

Find more posts tagged with

Comments

Off hand, the only way I can think of to do this would be to disassociate the component from that which is being updated - like using a copy or some such.

Presumably you're talking about using the SitePublisher menu option to update components on multiple pages at once.

The bigger question is: Why do you want to do this?
Is it a permanent thing or do you only want to block it temporarily and then bring it back in sync later?

If it's a permanent thing - then the copy idea makes more sense: have to versions of the component, one that gets updated and one that does not, and then use the one that does not get updated where you don't want it to be updated. Of course this requires a bit of forethought, or you'll have to replace components on a page-by-page basis (or perhaps template basis) to use the one that doesn't get updated... but the question remains: Why?

dharshak

Hey Ghoti,

We are managing multiple sites. My requirement is to update the component in some sites and not to update the component in other sites for temporary purpose.

Creating a new component means I need to remove the existing component, add the new component and to change the datum values. Which would be a time consuming task.

So do we have any optimal solution to achieve this requirement.

Thanks,
Dharshak Sagar

Adam Stoller

I don't think there's any optimal solution, but I'll defer to those who have more experience with SP components.

nipper

You are trying to use the product in ways it was really not designed for.

Best approach is to either create a second component as Ghoti suggested or to try to change the component that can have both behaviors (old and new) in the same version. You would need some flag to let the component decide which is the appropriate behavior.

Rick Poulin

You would need some flag to let the component decide which is the appropriate behavior.

...or just make your XSL backwards compatible (i.e. detect whether a newly added datum exists before attempting to use it). This will ensure that if people don't update component on pages, it'll still keep rendering properly.

If your sites are actually using the component in different ways such that a new page with a newer version of the component would be a problem, then you're either doing component reuse incorrectly, or you're hardcoding too much into your rendering logic.