Tag Info

Hot answers tagged

9

Admin Pages: Admin pages are typically used to extend central administration functionality and links to such pages are given in central administration site. Central Admin Web site uses a virtual directory named /_admin that is similar to the /_layouts virtual directory of content sites. The administrative virtual directory is mapped physically to the ...


5

Create a JS file (HideScript.js) and paste the following code in it, which hides the ribbon for a certain page. Upload the JS file to some document library for e.g. "SiteAssets" function HideRibbon() { $("#s4-ribbonrow").hide(); var newHeight = $(document).height(); if ($.browser.msie) {newHeight = newHeight - 3; } ...


2

Go to Site Settings, Site Collection features and verify that that the "Office SharePoint Server Publishing Infrastructure" feature is activated


2

You should be able to provision html at the root of the site by a FEATURE that uses Module element. From VS.NET add project item of type Module, replace sample.txt with your html file and make sure the elements.xml looks like below assuming you have sample.htm file abd your module name is RootModule. The name of module and html file can be different in ...


2

If the file isn't expecting to be in a document library, you can use SharePoint Designer to upload the file to the root of the web site, and also set this page to be the HomePage for the site within SharePoint Designer. SharePoint Designer is a free product available from Microsoft, here: http://www.microsoft.com/download/en/details.aspx?id=16573


2

This could be a case where the handle to the list is recreated with each call which would explain why the changes are not persisting. Try this instead : SPList pagesList = publishingWeb.PagesList; pagesList.EnableModeration = false; pagesList.EnableVersioning = true; pagesList.MajorVersionLimit = 10; pagesList.EnableMinorVersions = false; ...


2

This generally boils down to differences between Word's way of representing a document and HTML/CSS's approximations of such. One of the big areas they differ is indentation - SharePoint does its best to migrate the formatting but it doesn't always work. There are a couple things you can do about this: Use another tool to convert the document into ...


2

Yes, if the assets are stored in a document library and you save the site as a template, the assets will be there when provisioning a new site off the template. It may be a better approach though to bundle those assets into a feature and deploy them so they reside in the _layouts directory. If you need to make a change in the CSS or find a bug in the ...


2

If I understand you correct, what you want is a site map of your SharePoint 2007. This can be done following the guide Creating A SharePoint 2007 Site Map.


2

What is the real objective? As far as I know there is no easy way of, from a webpart knowing if the page (list item) has just been published or checked in. You can use the following code to check if the page is in display or edit mode and take some action: if (Microsoft.SharePoint.SPContext.Current.FormContext.FormMode == SPControlMode.Display) { // ...


2

Make sure you perform a Full Crawl after creating the Managed Properties to populate them with data. Incremental crawl will not be enough.


2

Add this to your SPServices call: CAMLQueryOptions: '<QueryOptions><ViewAttributes Scope="Recursive"/></QueryOptions>', So: SP.SOD.executeOrDelayUntilScriptLoaded( 'SP.UserProfiles.js', "~sitecollection/Style%20Library/Scripts/jquery.SPServices-2013.01.min.js"); SP.SOD.executeFunc('SP.js', 'SP.ClientContext'); $(function() { var ...


1

To answer the question, the expected behaviour of SharePoint under memory stress is that page response times would increase dramatically as Windows tries to thrash memory pages to disk. Sending garbage back to the client is not what you would expect. These problems suggest something wrong with the server, but you talk about having this problem with several ...


1

According to my understanding, you are referring to page layouts from which all pages in page library are created from. Page layouts are stored in the Master Page Gallery and you could easily update their XML markup using SharePoint designer or Visual Studio. See post for further information


1

Since the problem seems to be related to the Publish of the file, try this approach: SPFile fileDest = libDest.RootFolder.Files.Add( urlDestFile, streamFile, hashSourceProp, userCreatedBy, userModifiedBy, dateCreatedOn, ...


1

To create a SPUserField in PowerShell you can use $user=New-Object Microsoft.SharePoint.SPFieldUserValue(web, $userId, $userName) $item[[Microsoft.SharePoint.SPBuiltInFieldId]::Editor] = $user $item[[Microsoft.SharePoint.SPBuiltInFieldId]::Modified_x0020_By] = $user $item.SystemUpdate($false);


1

Looks like when the Workflow was created, two groups were added to assigned to and parallel was chosen. When an approval workflow is started, both groups get a task. I was a member of both groups, but it only counts my approval for one of the tasks. After I approved the first time, one task was completed, and I was only ever brought back to the approved ...


1

You will need to use the 'Approval Status' field in conjunction with Version field in order to find what you are looking for. For example, an Approval Status of 'Draft' but with a version of 4.5 tells you that there is a published version available (4.0) but that the page is still being revised (Draft). If this is a new site then you especially want to be ...


1

The issue with publishing pages is that they're not just list items, the Pages library is a document library. Each page consists of a template redirection file. You've nearly got all that you need but you need to create a copy of the template direction file. Now if you were using server side code, this is handled behind the scenes with the PublishingPage ...


1

Go to Site Actions--> Site Settings--> Navigation and deselect Show subsites and Show pages. The opposite of what is shown in the image here: Following this procedure means that they are hidden in Navigation. They will not be hidden from All Site Content. Show or hide individual subsites and pages Do one of the following: On the Site Actions ...


1

This is an awesome guide for learning how to work with WebTemplates and Modules to provision pages, pagelayouts etc. What you would need to do to provision pages with your WebTemplate is to add a new Module to a feature. In the module you would add your pages and specify where the pages are to be provisioned. Then add the Feature GUID to either Web and Site ...


1

Use SPSiteDataQuery to get all the pages or filter them w.r.t their associated Content Types. See example below SPWeb web = SPContext.Current.Site.RootWeb; SPSiteDataQuery query = new SPSiteDataQuery(); //Server template for pages library is 850 query.Lists = "<Lists ServerTemplate='850' Hidden='TRUE' />"; query.ViewFields = @"<FieldRef ...


1

I believe you need to use PublishingPage.GetPublishingPage to get the page, then use that to get Layout. For example: var pagesList = web.Lists["Pages"]; pagesList.GetItems(new SPQuery()).Cast<SPListItem>().ToList().ForEach(item => { if (!PublishingPage.IsPublishingPage(item)) return; var publishingPage = ...


1

For some odd reason, the items came back after selecting Modify this View > Scroll down to the bottom of the edit view page and select OK (without making any changes). It exceeds my knowledge why our SharePoint instance behaves this way - but it worked for me.


1

It's nested in one of the many javascript files in layouts folder. You can download a software called FileSeek and search through all files in this folder using keywords, in this case "function HideListViewRows". I have no affiliation with this piece of software.


1

Don't know where HideListViewRows is defined, but its added from the C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\GLOBAL\XML\VWSTYLES.xml file. E.g: <xsl:choose> <xsl:when test="$IsDocLib or dvt_RowCount = 0"><script ...


1

If you're querying multiple Site Collections use FullTextSQLQuery since it searches across the farm and if you plan to query Pages Library of a single Site Collection, use SPSiteDataQuery instead. I think you might need SPSiteDataQuery? SPSiteDataQuery queryObj = new SPSiteDataQuery(); //query Pages libraries queryObj.Lists = "<Lists ...


1

Application Pages: Application Pages are available available through the site collection. You can't modify the application pages using SharePoint designer. Application also called a layout pages because its deployed and _layouts/settings.aspx Admin Pages: Admin pages that are available in Central admin Site. Admin pages are used to perform that ...


1

We've done something similar by: 1) Creating a new Application page which uses a DataFormWebPart control to render a custom form. The Application page can be deployed via a WSP. 2) Customising the DataFormWebPart to show / hide certain fields, and expanding regions etc 3) Changing certain SharePoint links to point to the custom form. For example, adding ...



Only top voted, non community-wiki answers of a minimum length are eligible