Master Page file cannot be loaded when trying to edit aspx on a subsite

Question

A while ago, we (myself and our web developer) customized our master page. We made a copy of v4.master called v4custom.master and edited it. This was at the site collection level. Just recently, a user created a form in her site (subsite) and when she tries to edit it in SPD, it gives her the error "The Master Page file 'http://sharepoint.abc.xyz/_catalogs/masterpage/v4custom.master' cannot be loaded. Attach a different Master Page or correct the problem in Code view." I tried to navigate to that location in a browser & reports 'webpage cannot be found'. Navigating in my Site Collection, I see the master pages are located in http://sharepoint.abc.xyz/_catalogs/masterpage/Forms/AllItems.aspx.

Everything else appears to be fine. Does anyone have any suggestions as to what is causing this error?

Thank you!

Answer 1

This may be a conflict between the site template in the subsite and your custom master page. If your subsite is of different type compared to the parent site, the master page may assume to have different Content areas to what the subsite page layout really has.

Another thought is that if you're using Publishing features, you can inherit the master page from the parent. If you're using Team sites, you cannot just use the parent site's master page, but you will have dedicated copy of the v4.master in your Team (sub)site.

If you want to get the Team (sub)site to use same master page as the parent, you need to programmatically change the master page of the SPWeb of the subsite. You use the SPWeb.MasterUrl property.

See that every user has permissions to Style Library. There is a special group for that already, called "Style Resource Readers", so check that All authenticated users is a member of that group. Source

Answer 2

make sure you check-in and publish your custom master-page cause another user cannot see your work if your master-page not published yet..

Answer 3

I looked into this myself and discovered that our user didn't have access to the master page gallery on the -site collection-. Once I provisioned read access to the master page gallery on the site collection, the user was able to get in.

David K