Almost exactly two years ago, I wrote a post about using TLS with SMTP. See Using TLS with SmtpClient
If you’d like to send transport layer encrypted email with you SharePoint farm, you can do so by installing a .NET update and modifying the registry.
https://blogs.msdn.microsoft.com/rodneyviana/2016/06/28/the-unofficial-guide-for-sharepoint-2013-and-2010-working-with-tls-1-2-only/
The concept of Add-Ins (formally knows as Apps) in SharePoint puts logic as HTML and CSS to another page. This page is then rendered as iFrame to another SharePoint page. This approach has advantages and disadvantages. You have to decide yourself.
A very promising way to put stuff (or WebParts) onto a SharePoint page is the Widget Wrangler.
More information can be found on https://dev.office.com/blogs/introducing-widget-wrangler.
Conceptually Widget Wrangler implementation is based on similar thinking as PnP App Script Part implementation, which was released few years back as part of the PnP patterns (or at the time it was call App Model Samples).
After a SharePoint 2010 to SharePoint 2013 migration our users complained, that in the multiple Active Directory domain environment they havethe People Picker does not resolve the users the same way it did earlier. Only a subset of the users was resolved, users from a few domains were not included in the results at all.
Read more about it here.
According to this post, Microsoft will release a public preview in August 🙂
I can’t wait to get my fingers on it…
Today I installed the May CU on a SharePoint 2013 farm hosted in Azure. After the Installation was done (with a PowerShell script that disables some services to speed up the process), there were Exceptions opening the User Profile Service (UPS) settings page.
So I investigated the logs and found many entries about “Access Denied”. Some directly pointed to the registry hive “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\15.0” with the message Requested registry access is not allowed.
If your site is missing the three default groups “Visitors”, “Members” and “Owners”, you can create them easily with PowerShell or the Object Model.
Add-PSSnapin Microsoft.SharePoint.PowerShell
$web = Get-SPWeb https://your.site.url
if ($web.AssociatedVisitorGroup -eq $null) {
Write-Host 'The Visitor Group does not exist. It will be created...' -ForegroundColor DarkYellow
$currentLogin = $web.CurrentUser.LoginName
if ($web.CurrentUser.IsSiteAdmin -eq $false){
Write-Host ('The user '+$currentLogin+' needs to be a SiteCollection administrator, to create the default groups.') -ForegroundColor Red
return
}
$web.
A new version is out. If brings some great new extensions (two of them are from me 🙂 )
v5.0.4.6440 (2015-04-04)
New: All extensions added: Blocked file extensions, content type hub, custom crawl connector, features, logging configuration, managed metadata, re-ghost, search schema, secure store, site structure, CSOM extensions for files and 2013 workflows Updated: SharePointVersions.xml Updated: Typos in comments fixed and some code clean-up First release based on GitHub repository Grab your version from http://spsd.
Deploying Solutions can be a …. (fill in as you wish).
The SharePoint Solution Deployer offers a great opportunity to writing your own scripts. The existing functionality should match your needs to deploy SharePoint Solutions. If not, the “framework” can be extended with custom Extensions or simple PowerShell code.
I’ve written two Extensions, which let you enable and disable features upon deployments and reset files to their site definitions (aka ReGhost).
Getting the PageTitle of a page should be just a property away would you think. I would call Page.Title to get the title of the current page.
Unfortunately Page.Title contains “\r\n ” and the title of the page is in a new line, like this:
<title>
RH Test
</title> The property will only return the first row, which is not very helpful 🙁
So what can we do? Since the title is set through a control within a ContentPlacehoder, my way was to get the control and take the value from it.
Recently I had a problem setting the title field of a Page within the pages library. My requirement was to set the title with the value from the PageTitle field of the current item.
An ItemEventReceiver, which is executed synchronously to prevent save conflict exception or problems with published items, was supposed to do exactly that. But when I set the title property of the item via AfterProperties, the value did not get stored.
This article is written with scope on SharePoint 2013. With SP 2013 the default TrustLevel in the web.config is set to “FullTrust”. On previous version the value is “WSS_Minimal”.
When you develop Farm-Solutions for SharePoint, you can deploy assemblies to the Global Assembly Cache (GAC) or configure the solution for a “bin-Deployment”.
The bin-way puts assemblies into the bin folder of the WebApplication, where the solution is deployed to.
You can switch the target of the assemblies by modifying the properties of a SharePoint project.
Recently I was developing a custom field. To store modified values, the UpdateFieldValueInItem method has to be overwritten.
In a normal way of clicking the submit/save button, the method is called and I can adjust the value for the field within the current item. The changes are submitted to the database later.
But what if you want to modify items outside of the current item? Sure, you can do so would you think.
This is another post to help me remember. And as a reference for all of you, who cannot remember how to create a SPFieldLookup via XML.
<Field ID="{8b26ec41-b6c3-4327-0066-0c18c0768626}" Name="InternalName" StaticName="InternalName" DisplayName="Display Name" Type="Lookup" ShowField="Title" Mult="TRUE" List="Lists/LookupList" Overwrite="TRUE" /> When you provision a SPField via features, do not forget to add Overwrite=”TRUE”! Otherwise you’ll get an exception like this:
0x8107058aFehler beim Binden des Inhaltstyps ‘0x010200C7A18EB120BB4A00892E9E1EE9481C9B0067E475B6FDD54048B347370871443CAD’ an die Liste ‘/sites/rhtest/Lists/LookupList’ für ‘http://rhdevsp2013/sites/rhtest’. Ausnahme ‘0x80070057’.
As promised here, this is a follow-up post with the tool I developed for the SharePoint to WordPress migration.
First, a screenshot:
What is it, that we have to cover with a migration? Copying the posts is not enough. So I came up with this features:
Features Copy posts Copy comments Copy resources like images and downloads Create needed tags and categories Modify links to local resource deal with https, if links are absolute on the source blog and mixed with http Using web services to connect to source and destination URL rewriting (covered by a WordPress Plugin) Delete all content from the destination blog (for migration testing) Replace strings (with Regex) a nice (WPF) GUI Description Originally I’ve build a plain console application.
This post has some really great examples for JavaScript helper methods and available properties for working with Display Templates in SharePoint 2013. http://dotnetmafia.com/blogs/dotnettipoftheday/archive/2014/02/26/useful-javascript-for-working-with-sharepoint-display-templates-spc3000-spc14.aspx If you ever had to decide if your script is running on a SharePoint Foundation, use this one: // Determine if the host is SharePoint Foundation
if (!Srch.U.isSPFSKU()) { }
