I'm not sure about the master pages not being selectable in the UI, but you can certainly set the master page to be in a sub-sites _catalogs/masterpage directory through code at least. An example of this is the OOTB meeting workspace, it uses its own master page that gets deployed to each individual meeting workspace.
Brian Farnhill Consultant Technical Consulting Phone: 02 6225 4307 Mobile: 0408 289 303 Fax: 02 6225 4334 Email: [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]> Web: www.uniqueworld.net<http://www.uniqueworld.net> Blog: pointstoshare.spaces.live.com<http://pointstoshare.spaces.live.com/> Microsoft Certified Application Developer [cid:image001.jpg@01C932A7.A3B0F3E0] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Noone Sent: Monday, 20 October 2008 11:29 AM To: listserver@ozMOSS.com Subject: [OzMOSS] Subsite directory structure Something I've been wondering but can't find an answer to. Can anyone explain why subsites (not site collections) have a _catalogs directory which appears distinct from the root site but can't actually be used? Scenario: You can create new master pages and store them in the masterpage directory but they cannot be applied to the site through Site Settings. I know the approved method for this is to store them all in the root site but I'm stumped as to why there is a _catalogs directory for subsites in the first place. Just wondering. :) ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com
<<inline: image001.jpg>>
