According to Microsoft:
You cannot use the period character at the end of a site name, a subsite name, or a site group name.
You cannot use the period character at the end of a folder name.
You cannot use the period character at the end of a file name
Are you looking for a way to by-pass this directive?
Alternative access map is the feature desgined specifically for the purpose you describe.
The instructions I have linked to are for SharePoint v3 (WSS 3.0 and MOSS 2007), but remain the same for v4 (Foundation 2010, Server 2010). To my knowledge Microsoft has not provided updated instructions for the 2010 products and does reference this article in some of ...
What you are referring to are usually called "vanity URLs" because they are used by marketing more than the end users. One free product from Microsoft that can do this is the URL Rewriter. It is actually for IIS but works with SharePoint.
This works well and is performant but does have a few drawbacks:
It requires a server Admin to add new URl redirects
You're not supposed to change the IIS settings SharePoint thinks it control in IIS manager (at least not without telling sharepoint).
SharePoint notices that you access it through an unknown zone so it redirects you to the default zone which has the url http://oldurl
So please go into AAM and tell sharepoint what you did :-)
I don't fully understand your entire setup (especially when it comes to the "URL rewrite" part that looks more like a DNS redirection).
Anyway, one important thing here is probably to configure "Alternate Access Mapping" (AAM) on the SharePoint side.
This is needed in case the request SharePoint receives on its network card uses a different host-header ...
If you added that managed property to default display templates you need to create new manage result type from that display template.
Go to YOURSITE/_layouts/15/manageresulttypes.aspx?level=sitecol and click copy on that display template, add only different name (like WebPageNEW) and save.
Go again to YOURSITE/_layouts/15/manageresulttypes.aspx?level=...
The answer, though you may not like it, is that this is not officially supported in Microsoft SharePoint.
See: Supportability of Rewrite and Redirects with SharePoint 2007/2010/2013
Rewriting is actually changing both incoming and/or outgoing URLs. Any implementation of such rewrites is unsupported with SharePoint unless the path is symmetrical.
This looks like the master page has not been published after the link to the image was changed. Especially the fact that people with design access can see the correct image, points to that as the reason.
The regular user will see the last major version of the master page.
Make sure to publish the master page with the correct link as a major version.
Based on the Managed Properties that you show it would be hard. I would review all of the managed properties you can and see if you can find another that contains the rewritten parent url or the item url so that you could write a display template that does path trimming.
In cases like this I use the SharePoint Search Query tool from GitHub.
i presume from the reply that you want a custom 404 page? there are two methods. One is generic:
To configure SharePoint Foundation server or SharePoint Server 2010 to
point to a custom 404 error Web page, follow these steps.
1.Log on to the computer that is running SharePoint Server 2010 by using an account that has administrative permissions.
yes you can, but putting files from let's say googledocs defies the Whole point of SharePoint. Also you need to deal with the permissions in the other native source.
I believe you have more luck creating the hyperlink from scratch via the navigation in SITE SETTINGS - navigation, if as i seem to understand that screen is from the quick launch
currently there is no friendly name. I understand that within a business having an unrelated url to your standard name is not friendly.
usually if that is the case you should than have DNS setup. If so you can create a CNAME entry in DNS.
so the friendly name could be:
the main website is in mvc hosted on azure or internally that is called:
Their are couple of ways to cofnigure the Vanity URLs either OOTB(IIS) or 3rd party.
Configuring at IIS level: How to create vanity URL for sub site she is talking about the subsite but true for site as well.
Go to IIS.
Go to SITES right click and ADD a Web Site.
Name = SharePointVanityURLs (This is so the App Pool can be named
this, and they will all ...
If you are using 2010, then you can import that template into Visual Studio. At that point there is a lot of cleanup work to produce a valid WebTemplate package, but you can include code that can put web parts on a page or change web part properties as needed through feature receivers that fire on activation.
URL Rewrite Settings for SharePoint
Ok, the network admin and myself dove into the IIS rewrite add-on and figured this all out in an hour or so.. seems to be working very well for us. Internal users can continue to type 'intranet' into the address bar, and they get redirected to our preferred 'UAG-friendly' alternate access mapping of sharepoint. Sweet!
It could be accomplished by specifying more narrow match pattern for url
For example, let's discuss the scenario, where requests from:
should be redirected to:
and requests from:
You don't really have a whole lot of options here, but here are a few:
1) IIS URL Rewrite Module (I know you don't want this, but it is actually the best route) - http://blog.mastykarz.nl/sharepoint-redirects-revisited-301-302/
2) Your own custom Http Handler - http://blog.mastykarz.nl/sharepoint-2007-redirect-solved-using-301-instead-of-302-redirects/ (...
SharePoint itself is unaware of the rewriting that is being applied. When it goes to see if the active page should be highlighted, the URL of the page doesn't match what SharePoint "thinks" is the URL of the page.
You could probably do this with a simple event receiver on the list, taking in the field with the spaces in and generated the text with the spaces swapped for dashes in the other field.
You'd probably need some code, via powershell or a command line app, to retrofit the current items in the list, though.
Here's some documentation on MSDN on creating List ...