Tag Info

New answers tagged

0

Here's what I did to solve my problem: IgnoreIfAlreadyExists Needs to be set to TRUE everywhere in the Elements.xml files Upgrade solution Deactivate the Feature Delete the CSS folder Reactivate the Feature VoilĂ ! Thanks to all for your great advices!


1

IgnoreIfAlreadyExists needs to be set to TRUE. IgnoreIfAlreadyExists="FALSE" => Don't update if file already exists. IgnoreIfAlreadyExists="TRUE" => Do update even though file already exists.


0

It sounds like you need to active or re-activate the feature. Try running install-spsolution after you have added it to the solution store. If it's site or web scoped feature you need to activate it on the appropriate site collection or sub site.


2

Try the following in powershell to see whether your CSS file is customized: $web = get-spweb http://yourweb $f = $web.GetFolder("Style Library/folder/css") $f.Files |? {$_.CustomizedPageStatus.ToString() -eq "Customized"} |% {$_.Name} If it's customized, use the following to revert back to unghosted mode: $f.RevertContentStream() Reference here.


1

WSP Packages are indeed the recommended approach to deploy a solution. The WSP will contain all the components you mentioned, such as Web Parts, Page Layouts, Master Pages, Workflows, etc. The preferred approach to perform updates in an integration environment would be to automate the deployment of the WSP with a PowerShell script that performs the required ...


0

Use a makeCab utility to create one & try to use it. Before that I suggest you to extract a SP 2013 compatible .WSP & see all the artifacts present & whether they match your old .WSP inner files.


1

Create a mapped folder in your project and place .preview file inside it. Add a module to the project and provide the url which references /_catalogs/theme/15 in the XML file in order to place .spcolor file in it.



Top 50 recent answers are included