master page across multiple site collections

Question

I've got a branding feature, deployed in multiple site collections, including the master and system master pages.

The goal is that if a power user does some changes to one of these master pages, these changes are propagated throughout all site collections.

I've read some suggestions about using a module to deploy the pages centrally, but that still doesn't meet my requirements because file is unghosted when edited with SPD, and changes are not propagated.

Anyone has any deployment strategy suggestion to cater for this requirement?

Answer 1

The best approach is to use main master page (with only test pages attached) placed in a document library, and track changes to the file made using SPD and if any changes are made - update ghosted master page in file system accordingly, all other master pages are deployed via modules and are ghosted versions of one in files system. After changing file system master page you need to make recycle of app pools to apply changes to all master pages.

Tracking changes can be implemented via event receiver. Making it a little configurable, you can use this approach with several master pages.

Answer 2

Just an idea... Maybe you could create a webpart that you deploy on central admin. This webpart has for example a combobox where you can select the masterpage. And when selected a new one, you change all sites in all sitecollections of the selected web application (or farm) to the selected masterpage.