Tag Info

New answers tagged

-2

_catalog is a is available to current SPWeb Style library is available only to current SPWeb _layouts folder is available to all websites in WebApplication If you want any site to have access to a file, add it to _Layouts.


1

In you custom ONET.XML you need to provision default.aspx as well. <Module Name="Home" Url="$Resources:osrvcore,List_Pages_UrlName;" Path=""> <File Url="default.aspx" Type="GhostableInLibrary" > <Property Name="Title" Value="$Resources:cmscore,IPPT_HomeWelcomePage_Title;" /> <Property ...


-1

The easiest way would be to create a new application page and display all the pages that you need using iframe elements. The other way would be to create custom web part that would collect all data from SharePoint DB to display all repotrs. You can use this post to get details for second choise. If you would need more help let me know.


0

You can try setting the current HTTPContext as null, this way sharepoint does not recognise that it is a GET Request. Please see the below code, which worked for me: using (SPSite site = new SPSite(SPContext.Current.Site.Url)) { using (SPWeb web = site.OpenWeb()) { HttpContext ...


0

I've stolen from the mysitehost. There the mysite is create with this mechanic: if (Page.IsPostBack) { SPLongOperation operation = new SPLongOperation(this.Page); operation.LeadingHTML = "Meeting wird erstellt"; operation.Begin(); SPUtility.ValidateFormDigest(); Do site creation ... operation.End(currentMeeting.Url); } // This code ...


2

Create a custom 404 page for your site collection, then either add code behind to it with your own logic as when you want to create a subsite and when not.. OR in SharePoint 2013 create a custom error page, add a content editor webpart to it, and some javscript code which will create a subsite for you, but there is a lot of things that you will require to ...


0

remove the machine name and only use the user name! if in dout look in active directory users and computers to see the local user account that your using to make sure its correct..... Make sure that the machine name is correct –


1

Is the stuff with promises important? If not why not just use 'Include(AllProperties)' to include the properties and do something like this: var context = SP.ClientContext.get_current(); var webs = context.get_site().get_rootWeb().get_webs(); context.load(webs, 'Include(AllProperties)'); context.executeQueryAsync(function(){ var enumerator = ...


1

You can try the below powershell code. You need to # get a sitecollection object(SPSite) $SPSite = Get-SPSite -Identity "http://sp2010/" # loop through all the subwebs(SPWebs) in the site collection foreach ($SPWeb in $SPSite.AllWebs) { # check so that this is not the root web if (!$SPWeb.IsRootWeb) { # allow unsafe updates ...


2

You can activate SharePoint Server Publishing Infrastructure features on the site collection level. Then Go to the site settings of your subsite and find Navigation link in Look and Feel section. In Current Navigation settings select Display the same navigation items as the parent site


0

It is doable scenario for IIS URL Rewrite Module . Please refer Using the URL Rewrite Module for a details. Since REDIRECT is supported operation in SharePoint 2007/2010/2013 according to Microsoft, the following scenario could be configured: Client makes a request to http://webapplication:8000/sites/team1 IIS with Rewrite Module receives the request to ...


3

After searching over internet four hours I found one thing. That it is not possible to make alias of the url because the site collections lie within same web application. So, that way was not possible for me. The final solution is to create an HttpModule for web application that checks specific url, if it meets the condition then redirect that request to ...


1

The best way from my point of view is to add the users to an Active Directory Group. Then assign this AD group the requested permissions on the calendar and on the other site collection.


0

The setup account doesn't necessarily have access to a site collection. Adding it to Farm Administrator group has no effect either. Does the "Owners" SPGroup have effective permissions on the site (normally it would, but you or someone could have removed permissions for that group altogether) ? What happens if you do a permission check of that account for ...


0

I was able to get my desired result by making my web-parts, user-controls. This works for us since we don't really need end/power users adding/removing, re-sizing moving or interacting in any way with these controls other than reading from them.


1

Your sub sites will have the content types. Make sure that you have created the content types, and the hub, on the root site. You know that you are on the root site because if you go to site settings, you will see the "Site Collection Administration". Really the only possibility is that the hub is not coming from the root site of the site collection (I ...


0

SharePoint also offers you the possibility to create Site Columns. What are these? They are columns that we create in a SharePoint site to be available to its’ sub sites. SharePoint Columns, Site Columns and Content Types explained As you can see when you create a SharePoint Site Column it is available to the site and its’ sub-sites. This makes it very ...


1

I found an answer, just for site collection created on web application root. Use this command to backup a site collection Backup-SPSite -Identity "http(s)://your-site-collection-url" -Path "C:\backups\your-site-collection-backup.bak" It's important to use an absolute path as -Path parameter. Then create a new web application and then run the following ...


1

couple of things you can do. 1) Backup curent site collection and then restore it with different name & url. 2) you can use export Site Collection and Import site collection. You will lose the metadata etc. 3) you can use the 3rd party tool for this, which give you more power & flexbility and less effort. try ShareGate migration tool. they have 15 ...


0

Is this SP 2013 or SP 2010 ? Generally, it is cleaner to give each department there own site collection. But, there is one thing to keep in mind when splitting your departments across different site collections vs keeping them in one. Cross-SPSite query'ing is usually a problem. Everything inside an SPSite is more or less accessible from accross other ...


0

It is wise to segregate departments as separate functions. Each department function has their own unique processes. Granted there are times when they may cross. Each department can have their own set of sub sites contained, with unique permissions and content. You can create shared workspaces. This can be access restricted with the creation of ...



Top 50 recent answers are included