13

I've created a publishing page, placed a custom web part on in and published it. When I try to navigate to it I see this text instead of the content:

Page Content field value. Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

Searching the web I've found similar pages, for example: https://www.mundaring.wa.gov.au/ResidentServices/PublicHealth/Pages/default.aspx?ID=4&ID=4

One thing about the page is that it's getting a query parameter called id - could that be causing the error?

Improve this question

3 Answers 3

Reset to default
13

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

Improve this answer
4
  • +1 for more information available on this link.
    – ashish.chotalia
    Commented May 3, 2011 at 7:20
  • lol that sure is weird behaviour. Nice find
    – Anders Rask
    Commented May 3, 2011 at 7:58
  • I'm fairly certain this is the issue - I've sent the system admin the updated solution even before writing the question, but though I'd ask anyway. I'll update soon. In my defense, I should state that it worked on my machine, but not on the test environment.
    – Kobi
    Commented May 3, 2011 at 8:15
  • Important update - Our system guy is sick, so you won't get those 15 points for now, but you've got your health!
    – Kobi
    Commented May 3, 2011 at 8:53
2

Can you please recheck with giving id=1?

While passing ID as query string it's going to cast ID in some numeric format, so it will cause issues.

It's loading contents from the SiteLibrary pages document library.

Improve this answer
1

For the cases when you want to use your custom web part inside of a SharePoint 2013 page, I can suggest you the following workaround:

  • download web part page from SharePoint 2010
  • upload it in SharePoint 2013 using the explorer view
  • add your web part that uses the reserved url parameters

In my case this worked. Here is a blog post I have written: http://spobject.blogspot.com/2014/03/page-content-field-value-lorem-ipsum.html

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.