Page Content field value. Lorem ipsum dolor sit amet ...

The problem: When browsing a web part page with query string parameters, the page displays an error text "Page Content field value. Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ...".

This is very strang and annoying behaviour. I faced it now in SharePoint 2013 but there are blog posts explaining this error in the previous version as well.

The solution I found in the posts was not to used the reserved query string parameter.

I agree this is good option but what about the cases when something is working in SharePoint 2010 and after the upgrade to 2013 it is not. And rewriting the logic is definitely time&money consuming task.

The solution I found is more simple.

The solution: Download a web part page from SharePoint 2010 environment. Upload it in SharePoint 2013 library using the Explorer View. Add you web part(s) in it. Browse the page with your query string parameters and it will work correctly.

I have done this with the publishing library Pages and was able to make my existing web parts working at the same urls, as in SharePoint 2010.

If I'm using the user interface to create a page in SharePoiont 2013, I can't use the url parameter ID which in my case was critical.

Comments

ClientPeoplePicker in SharePoint 2013

Start using SharePoint 2013 I noticed that the way for selecting people or groups is changed. The new way is simple – just ‘Enter name or email address’ without any icons for ‘Check Names’ or ‘Browse’. I guess that the PeoplePicker is changed but NO. PeoplePicker sitll has the same functionality as before. There is a new control called ClientPeoplePicker . How to use it: 1. Add this references <% @ Register TagPrefix ="wssawc" Namespace ="Microsoft.SharePoint.WebControls" Assembly ="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> 2. Add the following control declaration < wssawc : ClientPeoplePicker Required ="true" ValidationEnabled ="true" ID ="peoplePicker" runat ="server" InitialHelpText =" <% $Resources:wss,aclinv_PickerIntialHelperText %> " VisibleSu

Error: A duplicate field name "xxxx" was found

Soon I have some experience with migrating solution from SharePoint 2010 to SharePoint 2013. The migration was on 3 steps. First one was just to copy the custom fields, content types and list definitions from the old VS 2010 project into a new VS 2012 project for SharePoint 2013. Looks like pretty simple task but ….. The problem: Error “ A duplicate field name "xxxx" was found ” when the feature for provisioning the fields and content types is activated. The solution: Review the field definitions and make sure no field has Name property equal to some of the ‘reserved’ values. Explanations: In SharePoint 2010 there was no problem to have these fields as a definition of custom fields: < Field Type = " Note " ID = " {893FB9BC-2DA4-4451-A1D1-88010CDC6A08} " Name = " Description " StaticName = " Description " DisplayName = " Description 1 " Required = " FALSE " MaxL

Using SharePoint Attachments' controls with elevated security

The scenario: Create custom forms for Add/Edit/Delete items to a list which is not accessible by the regular users. The forms should support working with attachments. The problem: The default SharePoint controls don’t work if the current user doesn’t have access to the list items. The solution: Use custom code for generating the SharePoint default HTML so the out-of-the-box javascript works correct. Explanations: The scenario occurs when some list need to be hidden form the users. The list has broken security inheritance and users can't navigate directly to it. Working with its fields requires crating web warts or application pages with appropriate controls on them and server-side code running under elevated privileges. The issue here is that the OOTB (out-of-the-box) controls for Attachments don't work if the user doesn’t have access to the related list item. The OOTB controls are: AttachmentsField , AttachmentUpload , AttachmentButton . There is a lot of code

SPObject.Resolve()

Search This Blog