Tag Info

Hot answers tagged

12

I would say yes, it's certainly the query string parameter you are using. Check out this post for more details http://blogs.technet.com/b/stefan_gossner/archive/2009/01/30/querystring-parameters-you-should-not-use-in-your-sharepoint-application.aspx


8

Try editing the SharePoint list settings in the browser. Open the list, go to List Settings, click the field name and select "No" for "Allow multiple selections". Edit after clarification that this is not a list form: The described behavior of the control leads me to believe that the form has initially been created with InfoPath 2007 and the people picker ...


5

ExecuteOrDelayUntilScriptLoaded(function () { var pageStateGroupPublishValue = SP.Ribbon.PageState.PageStateCommands.pageStateGroupSubmitForApproval; SP.Ribbon.PageManager.get_instance().executeRootCommand(pageStateGroupPublishValue, window.g_CUIcommandProperties, { CommandId: pageStateGroupPublishValue }, null); }, "sp.ribbon.js");


5

When you enable publishing you gain a lot, but you lose the ability to "save site as template". (To be clear, you lose this ability when you activate the site (web) level feature. If you only activate the site collection level "publishing infrastructure" feature, then you will still be able to "save as template".) http://support.microsoft.com/kb/2492356


4

There are no events specific to publishing pages. They are just ordinary documents (.aspx files) in a document library (the Pages library) that have been enhanced by the publishing API. So, you're on the right track with SPItemEventReceiver.ItemUpdated. Compare BeforeProperties with AfterProperties, specifically the Level field. A value of 1 means the file ...


4

The search delegate control is loaded into the standard v4 master in a placeholder called PlaceHolderSearchArea: <asp:ContentPlaceHolder id="PlaceHolderSearchArea" runat="server"> <SharePoint:DelegateControl runat="server" ControlId="SmallSearchInputBox" /> </asp:ContentPlaceHolder> In the minimal.master, this placeholder is hidden ...


4

Please, try to add List="116" attribute to your Module element, as it is shown in this MSDN how-to: http://msdn.microsoft.com/en-us/library/ms441170.aspx <Module Name="MasterPages" List="116" Url="_catalogs/masterpage"> <File Path="MasterPages\custom_main.master" Url="custom_main.master" /> </Module>


4

One approach, as an alternative to your RichHtmlField, and short of them having access to editing the entire page, is to use a ContentEditor Web Part. You can put your Javascript in here and not have it stripped out.


4

Another possible solution is to just setup two text field instead of using the url field. I'm not sure if that would work for what you described, though.


4

When provisioning Publishing Pages, you need to load an instance of the Template Redirection Page (found under SiteTemplates\SPS\default.aspx), but set the Url for the page to the name that you want to create, and set the properties such as content type and page layout in the normal way. Have a look at this for an example: ...


4

You can get usage data of the respective SPWeb, and filter out the statistics of a specific list item. DataTable usageDt = SPContext.Current.Web.GetUsageData(SPUsageReportType.url, SPUsagePeriodType.lastMonth); foreach (DataRow dr in usageDt.Rows) { if(dr["Page"].ToString().ToLower().Equals("myitem.docx")) { Response.Write("Page: " + ...


3

The module element won't replace files that have already been provisioned. You'll need to delete them from Feature deactivating if you want to re-provision files in a feature.


3

Did you try using SPSiteDataQuery or CrossListQueryInfo instead? This already handles caching and filtering is done using CAML. Check Waldek's blog post where he monitors performance of different approaches. Another post by Ton Stegeman here


3

So it really boils down to a few things. First, when you create a Publishing site you will have complete control over the master page and page layout experience. Another words, if your requirement is to build a public facing web site you would want to create a Site Collection based off the Publishing Portal template that is available. You can control page ...


3

It depends. If you want to add JavaScript to specific publishing pages, then the ContentEditor web part is a good choice. Alternatively, SharePoint Designer is a good way of doing this too. It would allow you to edit the page layouts - adding JavaScript to all pages using that layout. Alternatively you can 'disconnect' a publishing page from it's layout, ...


3

Pages based on the page layout should get updated when you change the page layout. A couple of reasons why this might not work are: 1) You are trying to change the page layout in the SharePoint root directory (e.g. by deploying a solution package) but the layout has been customized in SharePoint Designer. In this case changing the page layout on the file ...


3

You could certainly parse it out with script. It sort of depends on what "use the 'Description' and actual URL stored in this field in separate and different ways" means. With jQuery, you could get the href and replace the link with that text. Something like this (untested): var theLink = $("a[Title='LinkTest']"); $(theLink).replaceWith("<span>" + ...


3

If you have SharePoint 2010 standard license you will get document sets. Document sets allow you to treat documents as one set. Similar to a folder. Whats nice about sets is you can than use a approval workflow to approve the complete set. If you want to continue to use existing folders a workflow to approve all docs will be difficult. Perhaps others ...


3

You can use the Manage Content and Structure function in SharePoint (from site settings on all publishing sites) to select everything in a folder (mark all items in heading row) and publish it.


3

Simplest option would be to use the "Send To -> Other location" functionality to create a link between the two documents. When the source document is changed, the user can be prompted to update the various copies in other locations that may exist.


3

I have encountered the exact same issue you're having - a HTTP Module that handles 404, and getting 404's (and thus an infinite loop or a 500) when going to Manage Content and Structure. We also did what you did, and just remove the module for the authoring environment, but another 'short term' workaround until Microsoft sort this, is to put a 1x PNG file ...


3

There's one answer to all of your questions. No, Publishing feature is there to provide you with extra features to site collection, this feature is activated by default for Publishing side. Portal I am working on has team site collections with publishing feature enabled so that we sub-webs can inherit master page from Site Collection Home Page. ...


3

I recently blogged about how to restore the Navigate Up button in SharePoint 2013 using an AdditionalPageHead delegate control. This lets you add a control to the header of every SharePoint page and you can then do the necessary functions to restore the navigate up button. See ...


3

Thanks Robert! I am banging my head on the wall for this! Basically you don't have to add a code just to show the ribbon by default. Just go navigation and tick NO to show or hide command ribbons. According to the error that i got below, it is referencing to a script outside our domain. Webpage error details Message: Script error Line: 0 Char: 0 Code: ...


3

You hit the nail on the head with the loss of MDS. The only real drawbacks to using the Publishing features are: You can't turn the features off; there's no going back Loss of the Minimal Download Strategy functionality Loss of Save Site to Template functionality End users will have to be trained on the new functionality The question to ask in return is ...


3

One way for your to achieve this would be: Create a new SharePoint Group (or you can use one existent already) Make sure the original People/Person field in itself (when defined in the underlying list) is only allowing selection from that specific Group. Put target User into the group at step 1. Refresh your form to get the latest updates from the ...


3

you can add security trimmed on custom masterpage which only an authorised user will be able see the ribbon 1) Open your SharePoint master page 2) Locate this line: <div id="s4-ribbonrow" class="s4-pr s4-ribbonrowhidetitle"> 3) Change it to: <div id="s4-ribbonrow" class="s4-pr s4-ribbonrowhidetitle" style="display:none"> 4) Now find the ...


2

I have a bad habit of activating web application features on the wrong web app. I would double check that the correct web application is selected from the toolbar on the "Manage Web Application Features" page. If the problem still persists, you could try using stsadm to deactivate/reactivate the standard web application feature with the -force parameter.


2

Has anyone experienced this Yes :) and might have a workaround You might end up in implementing a Workflow/Timer job if you want to automate the publishing process. However, you could use major/minor versioning to write "draft" versions of a post that not gets published until you click on Publish as Major Version.


2

FYI to anyone, answered on MSDN: When setting up this site - I had added the columns directly to the site, and not to the content type at the root of the site. When I add tyhe colums to a custom content type - and then add that content type to the site (rather than the individual columns) - it works. I have no idea why this would result ...



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