New answers tagged feature
As specified by Nadeem Yousuf in a previous answer, you need to activate the feature on the new site collection. If you require this to be activated on every site collection you create from here on out, you need to create an event receiver to activate this feature. If the sites already exists, you can run a powershell command across your web application ...
You need to activate the feature in other site collections first. After that the webpart will be available.
Since you are propergating different DisplayName, you do have them defined somewhere... eg. mapped in the regional resource files. The declarative approach would be to set the DisplayName = $Resources:<projectName>,<propertyName>
First thing I do is close my PowerShell window & open a new instance, this works almost every time. If not I move onto restarting SPTimerv4 & IISreset, retract & deploy. if its still a no go I rebuild my package and manually remove the existing files.
I made a similar feature not long ago and I was able to achieve this by looking at all existing templates and matching the names against the know out of the box templates. If the current template is one of those then hide it. It's very cumbersome but it works. You need to list each template by name so a bit tedious... Just to add, I do ...
If I remember correctly the flow is: Site Collection Scoped Features Web Scoped Features Lists Modules Your stapled features would be shot in after Site collection scoped features or Web scoped features (depending on scope) and hence the lists is not guaranteed to be created before the lists. Found a source here: ...
Javscript Object Modal can be used to fetch profile information of current logged in user more information is here
Top 50 recent answers are included