Issues with converting HTML file to master page in SharePoint 2013 - sharepoint

Right now I have an HTML file and I'm trying to convert it to a master page. I'm using a VM on CloudShare.
So I create a new site collection and go into the site settings. Under “Look and Feel”, Design Manager isn’t there so I’ve found that if I go to “Site Collection Features” under “Site Collection Administration”, and activate “SharePoint Server Publishing Infrastructure” Design Manager will show up. So I go into design manager, but under Edit Master Pages none of the file or folder names will show up, and when I convert the html file the status column doesn’t show up either, so I can’t go to preview it or to the snippets gallery.
The only thing I can find online is to create a new site collection, which I’ve tried a few times. This happened on my old CloudShare VM, and creating a new site collection fixed it, but it’s not working for this. Can anyone help?

Personally when working with new master pages I have found that the best application to use is SharePoint Designer. You should be able to download it for free. Here are the instructions to configure SharePoint designer using it with CloudShare.
http://blog.cloudshare.com/tag/sharepoint-designer/

Figured it out - I made a new site collection and set it to a Publishing site template and it fixed the issue.

Related

How to create a sharepoint 2010 template that will dynamically update its child sites

I recently created a site in Sharepoint 2010, and I have saved it as a template. I'm able to apply this template to new sites, which is great. I can then add new data to each site individually. However, my problem is that if I want to change something on every child site, I would have to go through manually and do so. Is there any way that I can create a template that will work dynamically so that I can make changes to the original and all the child sites will inherit these changes?
Unfortunately not how you are requesting. When a site is created it uses a site template, including your own custom site template. Once a site has been created there is no way to reapply a site template to that existing site. You could use PowerShell to update a series of existing sites but the commands would get quite complex.
If you have deployed new site collections using a globally deployed template and you change that template using SharePoint designer, you should not have any issues and changes will be automatically applied to child sites unless you change master page.

Sharepoint 2010 web parts not displaying on one website, but are on the other

I'm working on remolding my companies current exsisting Sharepoint site. I installed the SP ZAP Slideshow webpart and went to the sharepoint site to insert it, and absolutely no webparts were listed. I went into the provided Sharepoint 2010 central administration and realized that everything seems to be listed as
//usmvwc0wtf1srv.ww005.work.net/sitepages/
When the website were hosting, and it should be listing is
//usmvwc0wtf1srv.ww005.work.net/sites/
I went to the /sitepages website and all the webparts exsisted and worked, however i need to get them working on the /sites page. Is there some way to switch it so it will not default all the webparts and content i'm uploading to the wrong page? I feel as though the wrong default page is listed? sorry new to all this!
Web Parts, which you see listed and are able to insert on a page when you edit it, come from the Web Part Gallery in the site collection. They are usually installed to the gallery when you activate their site collection-scope feature. Check what features you didn't activate in the new site collection - I suspect that one of them is responsible for the installation of Web Parts you are looking for. (The scope of the feature can be site collection or site - check both.)

Custom master page not refreshing upon deployment in Sharepoint 2010 Foundation

I use VS2010 on Server 2008 R2 with Sharepoint 2010 Foundation.
I have created a custom master page following instructions from here: http://msdn.microsoft.com/en-us/library/gg447066.aspx (activating my custom page as feature), and was delighted with the results. But as soon as I changed the images and attempted to deploy them through VS2010, I noticed that my changes were not showing in the page (which was still showing the old images).
Useful observations:
It's a Sandboxed solution.
I checked that wsp is built with the new images, and so it was.
When I retract my solution, I also go to Master Page Gallery, and
delete my custom master page from there to make sure I start from
scratch. No difference.
My SP Designer does not give me an option to "revert to site
definition".
My "Look and Feel" section in central admin does not offer a
"reset to site definition" option.
Checking "CustomizedPageStatus" property of the SPFile for my master page shows that it's set to "none", and indeed, calling RevertContentStream throws an exception. This indicates it may not necessarily be the unghosting issue.
Does anybody know where my images get deployed to, and what the cause of this problem may be? The "Deployment Location" property does not lead to the correct location (in fact, I can't even see my Feature's folder). Could it be something to do with the way variables in the path - {SharePointRoot}\Template\Features{FeatureName}\StyleLibrary\Branding101\Images\ - are parsed?
I am new to Sharepoint, so all and any help would be much appreciated.
Since this is a Sandboxed solution, everything gets stored in the content database, accessible through SharePoint Designer 2010. In SP Designer, open the site you are working on, then look under "All Files" in Site Objects: that's where I found my masterpages, images, etc.
Deployment paths (displayed in module properties in VS2010) are just red herring, as no deployment to the file system itself takes place. Hope this helps somebody else!

File not found error in SharePoint 2010 while using a site template

I'm using SharePoint 2010. I saved a Site Template(.stp) and used this template to create a sub site. Browser shows file not found error, however, if I add /_layouts/ChageSiteMasterPage.aspx to that URL, I'm able to see settings Page.
Error:
cannot create folder "Path".
Correlation ID: 4baa2636-0dd9-4965-afc1-e438d74a20d5
What could be the problem??
Search for that correlation ID in your SharePoint log. Probably the problem is because you need to activate a feature in the new site, or you have a custom solution that you need to deploy there.
Go to Site Setting and open the Master Pages section. Look for anything checked out and chack it back in. This happens each time you create a new site from a template.

Duplicate SharePoint MOSS site without content

What is the best way to copy an existing SharePoint MOSS site and then recreate a copy of it on the same server?
I want to ideally include web parts but not actual content like documents etc.
I've looked at using the SPDeploymentWizard and saving the site as a template but the SPDeploymentWizard takes all the content and saving it as a template I get an error that the site is too big to save.
Any suggestions appreciated
You can create a site template by clicking the "Save Site as Template" option in the Site Settings page. SharePoint does not have the ability to create templates based on Publishing definitions but there is a work around listed here:
link text
Webpages with weparts or not are considered content in SharePoint.
So to move the site you will have to create a new moss site with an associate content database.
You will then be able to backup your original site and restore it over the new one.
Then you will have to delete the content you did not want to have in the new site.
To avoid this problem in the future, create a SharePoint Solution containing site template using STSDev2008.
This will take time, but it will allow you to create a site with all the required content pages etc ready to go and will reduce the time to create these sites.
You can backup and restore to a different server using stsadm.exe.
EDIT
Apparently there's an actual export feature for content
http://msdn.microsoft.com/en-us/library/bb507233.aspx
The default size of templates is around 10 MB. you can increase that using
stsadm -o setproperty -pn max-template-document-size
Also if you are doing templates, that does not do sub-sites.

Resources