Tag Info

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 ...

The standard, simplest way of doing this is to use built-in wiki functionality:
Type [[ then wait for the drop-down menu which should show other pages in the same library at the end of the menu 2 options -Lists and Views.
Use keyboard Arrows ↑ and ↓ to select LISTS(very important: DO NOT USE MOUSE as the menu is quite Sensitive)
Press the TAB key. This ...

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 ...

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

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;
...

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 ...

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 ...

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 ...

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)
{
// ...

A Pages library is a document library that contains all the content pages for a publishing site. A site that has thousands or tens of thousands of pages stored in the Pages library must consider a unique set of issues that relate to managing these pages, and providing navigation between them in a site.
...

As Varun Verma answered already, I will try and support the answer with my own to get you as much resources/information as possible. :)
Content pages in Site Pages library are wiki pages. Page Layouts in Pages library, on the other hand, are the layout upon which a new Publishing page is created.
This article explains what page layouts are and how they ...

The navigation options which you have set tries to pulls the items from managed metadata term sets.
Change the Global and Current Navigation settings as below to display the pages as navigation items.
The folders will not be displayed as navigation items. But you can still add the folders manually and move the pages accordingly under the same navigation ...

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 ...

James your answer got me to look at it differently. If you want to create pages with the rest service I recommend you do the following. Create a page in the SharePoint site. Then download the page from the SharePoint server. This is the XML in the aspx page that needs to be uploaded to the server using the rest. ...

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 ...

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 ...

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 ...

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 = ...

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.

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.