Hot answers tagged publishing
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
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");
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
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
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: " + ...
4
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
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
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
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 ...
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
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 ...
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
The use of BCS for external content types and lists is more suitable for surfacing external data in a familiar format that business users can consume - a SharePoint List. I don't see much of an advantage using it the way you are suggesting.
Have you considered using BCS to augment user profiles to pull in the bio information as a mapped property? This would ...
2
I would enable the collaboration features. The reason is that it also enables the correct content types and everything became easily available in the content query webpart for aggregation. This eliminated the need for development customizations and it did fit with customer requirements. So in this case no development is needed.
If you go the route of pages ...
2
You need to add the google analytics page tracking to the master page. I got it working read this article which helped me.
http://mikeknowles.com/blog/2009/07/11/EnableGoogleAnalyticsPageTrackingInASingleNameIntranetSite.aspx
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 ...
2
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, ...
2
ContentEditorWebPart wp = ....
wp.Content = "Your text here";
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.webpartpages.contenteditorwebpart.content.aspx
2
The MasterPage Gallery is actually a document library, you want to remove the page layout from the RootFolder of that library (which you can get via List.RootFolder).
Use GetCatalog to get the List, then get the folder via RootFolder.
2
Since you are on a hosted 2007 environment server-side PowerShell and C# are out of consideration. Your best bet is to use jQuery to retrieve the Wiki article content via the lists.asmx Web service.
IIRC, there is a jQuery SharePoint Web service library on www.codeplex.com which could be helpful, but I never tried it myself.
2
Verify that the account has permission to see these draft versions. The libraries may be set up so that only approvers and the original author can see the unapproved content. That means the crawl account needs to be in the Approvers group
Keep in mind that this will result in draft versions appearing in search results for everyone to see. Then, some users ...
2
Needing to review and approve content is precisely one of SharePoint's core use-cases, so that requirement is definitely not an issue :)
I would have the reports sent to separate Document Libraries, with permissions set up so only the relevant people can view them. Set up Content Approval on those libraries, so when they are added, they need to be viewed ...
2
You could call the CheckIn method on the file you just added.
$MasterPageFile = $MasterPagelist.RootFolder.Files.Add($MasterPageName, $MasterPageBytes)
$MasterPageFile.CheckIn("Checkin by Powershell")
$MasterPageFile.Publish("Published by Powershell")
I haven't tested the code, but that should probably be sufficient.
2
You need to CheckIn and Approve your masterpage file after adding. Just after $item = $MasterPagelist.items |? {$_.Name -eq $MasterPageName} add following lines:
$item.File.CheckIn("CheckIn by PowerShell script")
$item.File.Approve("Approve by PowerShell script")
2
Moreover, each timer job has its own default schedule for when the job runs. You can change the frequency with which each job runs on the Job Definitions page on the Central Administration Web site. It entirely depends upon how often content editors engage with the SharePoint portal for creating content, number of users within the organization and so on. ...
2
If you aren't going to use the groups, I can't think of a reason deleting them would be a problem EXCEPT that recreating any one of them can be a real pain. Each group is built up of a combination of settings for the 32 permissions. You might be better off leaving them just in case unless the EXCEPT above doesn't concern you.
2
Html content is usually in the crawled property:
Property Set: 11280615-f653-448f-8ed8-2915008789f2
Variant type: 31
Name: html
(http://msdn.microsoft.com/en-us/library/ff795815.aspx)
You can also add a "Spy" stage to examine what crawled properties are available in the pipeline - and see if you can find the one with the correct content. Or enable ...
2
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 ...
Only top voted, non community-wiki answers of a minimum length are eligible
