Sharepoint OOTB pages - content types and fields

Base Page CT - "System Page", ID 0x010100C568DB52D9D0A14D9B2FDCC96666E9F2, columns:
Content Typec042a256-787d-4a6f-8a8a-cf6ab767f12d
Select5f47e085-2150-41dc-b661-442f3027f552
Name8553196d-ec8d-4564-9861-3dbe931050c8
Created8c06beca-0777-48f7-91c7-6da68bc07b69
Titlefa564e0f-0c70-4ab9-b863-0177e6ddd247
Modified28cf69c5-fa48-462a-b5cd-27b6f9d2bd5f
Document Modified By822c78e3-1ea9-4943-b449-57863ad33ca9
Document Created By4dd7e525-8d6b-4cb4-9d3e-44ee25f973eb
Comments9da97a8a-1da5-4a77-98d3-4bc10456e700
Scheduling Start Date51d39414-03dc-4bd0-b777-d3e20cb350f7
Scheduling End Datea990e64f-faa3-49c1-aafa-885fda79de62
Contactaea1a4dd-0f19-417d-8721-95a1d28762ab
Contact E-Mail Addressc79dba91-e60b-400e-973d-c6d06f192720
Contact Name7546ad0d-6c33-4501-b470-fb3003ca14ba
Contact Picturedc47d55f-9bf9-494a-8d5b-e619214dd19a
Page Layout0f800910-b30d-4c8f-b011-8189b2297094
Variation Group ID914fdb80-7d4f-4500-bf4c-ce46ad7484a4
Variation Relationship Link766da693-38e5-4b1b-997f-e830b6dfcc7b
Rollup Image543bc2cf-1f30-488e-8f25-6fe3b689d9ac
Target Audiences61cbb965-1e04-4273-b658-eedaa662f48d
Hide physical URLs from search50631c24-1371-4ecf-a5ae-ed41b03f4499

Page CT, "Page", ID 0x010100C568DB52D9D0A14D9B2FDCC96666E9F2007948130EC3DB064584E219954237AF39, extra columns:

Browser Titleff92f929-d18b-46d4-9879-521378c689ef
Meta Descriptiond83897e5-2430-4df7-8e5a-9bc06c664992
Meta Keywords45ae2169-585c-440b-aa4c-1d5e981fbbe5
Hide from Internet Search Engines325c00dd-fd91-468b-81cf-5bb9951abba1

Article page CT - "Article Page", ID 0x010100C568DB52D9D0A14D9B2FDCC96666E9F2007948130EC3DB064584E219954237AF3900242457EFB8B24247815D688C526CD44D, extra columns:

Page Image3de94b06-4120-41a5-b907-88773e493458
Page Contentf55c4d88-1f2e-4ad9-aaa8-819af4ee7ee8
Summary Linksb3525efe-59b5-4f0f-b1e4-6e26cb6ef6aa
Bylined3429cc9-adc4-439b-84a8-5679070f84cb
Article Date71316cea-40a0-49f3-8659-f0cefdbdbd4f
Image Caption66f500e9-7955-49ab-abb1-663621727d10
Style Definitionsa932ec3f-94c1-48b1-b6dc-41aaa6eb7e54

Comments

Post a Comment

Popular posts from this blog

OverTheWire[.com] Natas Walkthrough - JUST HINT, NO SPOILERS

game portal: http://overthewire.org/wargames/natas/ PASSWORDS for each level are stored in /etc/natas_webpass/natasX I made this walkthrough for people like me, i needed some help, but didnt want the spoiler, so here i will give you all the information needed to pass each level, yet not the solution. For levels needed custom web request i made a different post for powershell and javascript  with how-to's, since is a piece of learning for itself, and also for those of us that play at work and have only powershell at their hands. Although its not a complete spoiler there, its quite most of the solution so try yourself 1st. Natas The Natas game is from basic to advances web hacking. Every few levels is about whole new exploitation (with some harder ones doing comeback later), so a lot of learning. If you're new, you're the reason i am writing so much even for the 1st level, just please google EVERY topic you see, since in the following levels i assume you know the ...
Read more

Asp.Net Ending Response options, Response.End() vs CompleteRequest()

this blog is for any1 who get the ThreadAbortException when caling Response.End(), and then tried the other options such as HttpContext.Current.ApplicationInstance.CompleteRequest() and found out that there was no replacement. i'll start with the bottom line: if you want to stop right now your response and send it as is you dont have any other option other than Response.End(), period and it's the right thing to throw that EX in that case. the answer is its because there is the "HTTP pipeline" and the "Asp.Net pipeline", and CompleteRequest() cuts the HTTP pipeline but not the Asp.Net one so everything that is from handlers forwars (including all page events) continues but your part, the asp one, stays in your hands so that no information will be lost, so ur suppose to manage your code currectly, since information lost is really a bad thing, although in most cases we use Response.End() we know what we are losing and we want it. see this short article ab...
Read more

SOLVED The item could not be indexed successfully because the item failed in the indexing subsystem

if you got an error like this The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Failed to recover content group; Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 04081656-B51B-4DCD-96D4-6DB2D2CEEEE7 ) as well as these: The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Caught exception when preparing generation GID[7]: (Previous generation (last=GID[6], curr=GID[7]) is still active. Cannot open GID[7]); Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 92EB0180-C086-4853-BED8-F4878D9748AD ) the solution for me was to clear configuration cache (PS)  and then restart SP Search Services. THX ...
Read more