I've seen some discussion on this but never a solution. Anybody any ideas?

I'm trying to create a site using master pages that allows the user to alter the master page layout and have this propergate to all pages using this master page. However I also have web parts in the individual content pages but this should not propergate to other pages but still be customisable by the user on a per page basis.

The problem implementng this is because personalisation is on a per page basis and web parts has no concept of master pages. Essentially a page is a page and personalisation is store on this basis.I can part solve this by writing a custom personalisation provider to effectively share the personalisation across pages by overriding the page url when storing personalisation data. However this still leaves the problem of having content page web parts remaining uneffected as they are part of the same page.

Ideally I need to seperate the personalisation behaviour from the master page and the content page but can't figure how this could be acheived.

Ideas much appreciated.

I'll try to be a bit clearer than my original post:

I'm trying to have zones in the master page have seperate personalisation to zones in the content page. Therefore being able to keep all master content the same across the whole site, although can still be customised by a site admin.

Hi,

Do you mean your webpart will be existed in MasterPage and content page, and you want to separate them? If so, I think what you can try is shaing web parts across mulitple pages by creating a custom PersonalizationProvider. So in this way, you can separate the zones in Masterpage with those in content page.

Here?s a link for you to refer which concerns on how to create this kind of custom personalization provider, maybe it?s helpful to you.

http://www.simple-talk.com/dotnet/asp.net/web-parts-in-asp.net-2.0/

This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet. 

Thanks.

I've looked at this article before and it goes part way to the solution. What is does is basically duplicate web part content across a number of pages, or group of. It doesn't provide any seperation between the master and content pages. This is because these are effectively merged at run time so any changes made on the master page or content page will be rolled out to all other pages.

The goal is to:

1. Have a site that uses master pages and content pages. A site administrator can login and alter web part content on the master section of the page and have this propergate to all pages. An example would be to drap a site menu web part onto the header of the master page. This first part is simple enough to do with the referenced article.

2. Individual content pages on the site also need to be customisable. An example would be a product page on an ecommerce site. The web admin could drap product images, titles and description onto the page as required. But web parts in the content part of the page should not propergate to other pages.

The only option I can think of is to put master page content inside a user control and at runtime check if the zone is inside this user control. If so then user the generic personalisation. If the content is not in this user container control then get personalisation data for the individual page. I expect this would be interesting / difficult to code and sounds like a lot of effort.