As a developer you have several ways to customize the alerts.
In order to insert your company's logo, you will have to implement your own iAlertNotifyHandler.
You can get an overview about your possibilities here: "msdn Library > Alerts in SharePoint Foundation"
The article says nothing about SharePoint 2013, but when you look in the documentation for "...
This was not as easy as i first expected but here is my solution:
This block opens the new document with the designated libray as default savelocation:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
You can't. If you save the stp-file, rename it to cab, opens the cab file and opens the manifest file inside you can see what you can see from the splist. An if it's a generic list, that has added fields. The only way I guess you can do it is to add some kind of information in the schema that will identify the template.
Question: Will the .stp file include the content type used by the list?
So answer of this question is, no the content type will not be included with the list template.
Question: where will it be uploaded to on the new site?
We upload the .stp file in List Template Gallery. So, it will be stored there in certain. and then you can create a new list from ...
The control templates and display templates are terminologies used for Search in SP 2013.
Display Templates are used with CSWP to format/style search result
generated by CSWP search query. Display Templates control which
managed property is shown in the search results and how they appear in
the Web Part. Each Display Template ...
In SharePoint 2010 this functionality is not available. It's present in 2013 though. There's a very popular hack to do this but it requires some manual effort. Below are the steps to achieve this:
In the first(source) site, create the required workflow and publish it.
Now select Export to Visio option which allows you to save the workflow with a .vwi ...
I would go for a WebTemplate based on Blank Site (or, I usually base my templates on STS#0 or STS#1). That way you get full control over which features that will be enabled.
You could activate your composed look with the help of a feature too (with modules containing the elements needed, and a feature receiver with code that makes sure to configure what ...
One of the core functions of sharepoint's document libraries is just that!
Store the Templates in the Forms folder within the library, allow multiple content types, and associate the templates to various content types.
Here's some links to get you started. Welcome to sharepoint!
I have been reviewing my site definition and I have a Calendar that is deployed in a Publishing site.
The Elements.xml of that list is as follows
<ListInstance Title="Calendar" OnQuickLaunch="FALSE" TemplateType="106" FeatureId="00bfea71-ec85-4903-972d-ebe475780106" Url="Lists/Calendar"...
You can reset the subsites to inherit the master page of the parent site in the masterpage option located under Settings -> Site Settings -> Look and Feel -> Master Page.
This option is disabled by default in the Team Sites to activate it you have first to activate the SharePoint Publishing features.
Note: The Team Sites in the SharePoint 2013 inherit the ...
The problem was my profile. It was kind of corrupt.
Somehow whenever I logged-in on my SharePoint 2013 server, windows could not find my profile and used a temperary profile.
Removing this profile and restarting the server solved the problem.
Removing temperary profiles describes the following various steps to solve the problems
How to fix it if you see ...
I have tried to reproduce issue that you are facing. but Its working for me.
I have some suggestion for you
Do the workflow named with a long name or the specified path is very long?
SharePoint has limitation that fully qualified file name cannot more than 260 characters, and the directory name cannot more than 248 chars. If this is your problem, please ...
When saving the list as a template you get the option "Include content". So depending on your selection content will be included, but I think there is a limitation regarding the max. size of list templates (which was pretty low in SP2010, I think 10 MB) I will doublecheck on that...
You shouldn't have any issues by updating the template. Just make the change in your content type hub and re-publish the content types.
Documents that were created with the old template will not be updated to target the new template though. If that has to happen, they need to be updated manually.
There are couple of ways to find it.
simple one is Go to the view source of the SharePoint page >> Search for "SiteTemplateID" to find site template name SharePoint 2010.
USe command Line tool stsadm.exe -o enumallwebs -databasename <content-db-name> > Template.txt Now, Open the template.txt file and check for template
Use SharePoint Manager to ...
here is a solution for publishSites:
Open the publishing site in SharePoint Designer 2013.
Click the Site Settings icon on the ribbon. SiteOptions_in_SPD
Modify the parameter SaveSiteAsTemplateEnabled from the default value of false to true.
Saving Publishing Site as a Template in SharePoint 2013
As I understand, you are trying to copy list template to another site. You have to download such list template as file from List Template Gallery (available from Site Settings) and upload it to List Template Gallery of target site. Then you can simply create new list based on this template (when you choose to add new app in Site Contents, you will be allowed ...
Just add another attribute for your button i.e. style attribute. You can put any style you like within it. In your case you can go with following code:
<input type="button" style="font-size: 24px; font-family: Arial, Helvetica, sans-serif;" onClick="CoreInvoke('createNewDocumentWithRedirect2',event,'LINK.pptx', '...
To create a template you should first create a subsite with the required design, then save it as a template using the OOTB tools in the UI by navigating to Site Settings>Site Actions>Save as Template
Note, however, that if publishing features have been enabled on your site collection you will not be able to save the site as a template. A SharePoint ...
If you plan to use Cross-Site Collection Publishing for Publishing Site, So
Yes, Working with (Not just Activating) the Cross-Site Collection Publishing for Publishing Site Will impact the ability to Save a Site as a Template functionality.
Publishing site collections for the publishing site must have the SharePoint Server
publishing features ...
Inspect the disabled greyed out Control in browser. Remove the disabled flag using just the browsers HTML. And close the browser. The control should be enabled. and the warning will go and you'll be able to Save the workflow.
Silly SharePoint Client Side Validation.
There is few change in the C# code used for SharePoint 2013. Here is step by step guide for implementing it in SharePoint 2013.
First download the STP file from Site A. For that
Open Site Settings -> List Templates -> Select the list template file and download it.
Now open Site B.
Open Site Settings -> List Templates -> From Ribbon Upload Document.
Choose the STP file.
You will see the benefit when you upload the template file back to a site collection.
To upload the template, you goto Site Settings -> List templates. You will see the list template gallery which works just like any other Document library. You can upload your template file here.
If the gallery already contains the template with filename same as the one ...
There is no limitation for Calculated columns. When you save the list as template which contains a calculated column it behaves normally. You will be able to save the list template and recreate a new list using that template. The newly created field also has the Calculated column with same formula.
Similarly when you save the site as template and reuse it, ...
You can export the list to excel and then import it into SharePoint online list.
Also check this KB articles for more detailed information about how to manually migrate the content to the office 365.
Ok, figured it out.
The issue was that for the custom list where I used a custom ListForm successfully, I was using a simple custom content type and in my content type definition had Inherits="FALSE", which caused the content type to defer to the form template specified in the list schema.
In the document library, I was using a custom content type that ...
To share Content Types between Site Collections, you usually implement a Content Type Hub. The CT Hub publishes Content Types, which other Site Collections can subscribe to. That way the get the same GUID and template to use across Site Collections.
See: Create Content Type Hub in SharePoint 2013