Had this problem a few times when removing a connected web part from a WSS v3.0 web part page using the web part menu in the browser - the deletion operation leaves behind a web part connection definition in the page, and the page then fails to render as the pre-processing notices that the target of this connection is missing.
Haven't yet traced the cause of the problem, as it occurs infrequently. I have a feeling that it is caused by custom code in other web parts on the page that attempt to fire that connnection - perhaps the connection definition is not removed because an element still uses it (even though that element was manually added in code).
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment