As nasty as it may sound (and it is, beleive me), extending the Content by Query class to add a few more features. One of the requirements is, on a variation push, update all items in the query results to the current variation. I worked directly with the developers at Microsoft on this who were quite helpful. To mess with changes on a customization during a variation push, you implement IWebPartVariationUpdate which has a single method Update.
Now for the fun part. The issue I think is part .Net and part MOSS. The partent class (ContentByQueryWebPart) also implements this interface and I need to basically override this to do more things. Due to the model .Net follows on overrides, the parent needs to mark this method as overrideable. Of course, this is not the case. We (Microsoft developers and I) got this to work by putting "new" into the method signature:
public new void Update(PublishingWeb ownerWeb)
That worked great for a while. Then it stopped working. The method simply does not fire any more. What changed may have been SP1. We tested this prior to that coming out then it sat there for several months before we actually got the time and money to implment the customization. What is happening now is that apparently neither Update method (parent or child class) is firing at all. Of course just dropping the OOB content by query web part on a page and do a variation push it works fine (so they fixed the primary bug we were after).
Does anyone have any suggestions on getting the Update method to fire on a variation pushe (post SP1)?
Now for the fun part. The issue I think is part .Net and part MOSS. The partent class (ContentByQueryWebPart) also implements this interface and I need to basically override this to do more things. Due to the model .Net follows on overrides, the parent needs to mark this method as overrideable. Of course, this is not the case. We (Microsoft developers and I) got this to work by putting "new" into the method signature:
public new void Update(PublishingWeb ownerWeb)
That worked great for a while. Then it stopped working. The method simply does not fire any more. What changed may have been SP1. We tested this prior to that coming out then it sat there for several months before we actually got the time and money to implment the customization. What is happening now is that apparently neither Update method (parent or child class) is firing at all. Of course just dropping the OOB content by query web part on a page and do a variation push it works fine (so they fixed the primary bug we were after).
Does anyone have any suggestions on getting the Update method to fire on a variation pushe (post SP1)?