0

I created a content type and deployed it as a feature. It shows up in the root site. I cannot attach it to the Task list in a sub site. I created a console app (code from MS) and tried to add it programatically. The message "The content type is not available in this site" appears. How can I make a content type available to a subsite? I thought it would be available by default to all subsites, especially being in the root. When I ran the console app, I was logged in as the system account on the SP server, so it shouldn't be a permissions thing. The content type has a parent of Workflow Task.

I have been struggling with this for over two weeks.

Improve this question

2 Answers 2

Reset to default
0

go to features and click the features/feature name/.feature and change the scope up from site to web and it should work fine.

To improve my answer here is the MSDN on scope and content type

Improve this answer
7
  • Bummer. I get the error: "Elements of the type 'Content Type' are not supported at the 'Web' scope. This feature could not be installed.
    – Steve W
    Sep 10, 2012 at 17:42
  • To quote msdn I linked "Although you can create a content type with a Feature that is scoped either Site or Web, the scope must be Site if you are also provisioning files (such as document templates) with the same Feature."
    – Hugh Wood
    Sep 10, 2012 at 17:50
  • ok. This is a pretty basic content type but it inherits from the Workflow Task type. I don't know if that is the problem. My content type is made up of an elements and feature xml file. I'll keep digging around. Thanks.
    – Steve W
    Sep 10, 2012 at 18:27
  • Got your link and it would have been helpful to state I am on MOSS 2007. Checked the same MSDN page but for 2007 and the web scope is "No".
    – Steve W
    Sep 10, 2012 at 19:24
  • One last thing. I am able to see and add the content type to the task list at the root level, just not any sites below.
    – Steve W
    Sep 10, 2012 at 20:29
0

I was able to make the content type available to the task list in the sub site by adding the following to the feature.xml file: 

<Properties>
    <Property Key="GloballyAvailable" Value="True" />
</Properties>
Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.