Karthick's Blog!

InfoPath 2010 ·          Part of Office Professional Plus 2010 ·          Tool to design electronic forms ·          These eForms can be published to SP Server ·          Two tools o    InfoPath Designer 2010 o    InfoPath Filler 2010 (Only when used outside SharePoint) ·          In SharePoint o    InfoPath Forms Services part of Enterprise Edition ·          Usage of InfoPath in SharePoint o    InfoPath Customization for a Custom List o    InfoPath Form Libraries o    DIP – Document Information Panel ·          Two Development Approaches o    InfoPath forms without code o    InfoPath...

Also, if you look at the Event Viewer, you might find the below issue: An operation failed because the following certificate has validation errors..... It could look something like this: The solution to fix this issue is to add the root certificates of the SSL certificate to the SharePoint 2010: Open the SharePoint 2010 Central Administration Open the ‘Manage Trust’ section under the ‘Security’ Tab Add the SSL Certificate and all the Root Certificates of the certificate chain. The best way to import the certificates is to store them in base-64 files with the file extension *.cer Now check if the SharePoint 2010 Portal is working via the Https url

Resolving "The super user account utilized by the cache is not configured." If you have a SharePoint Publishing site and you check the event viewer every once in a while you might see the following warning in there: Object Cache: The super user account utilized by the cache is not configured. This can increase the number of cache misses, which causes the page requests to consume unneccesary system resources. To configure the account use the following command 'stsadm -o setproperty -propertyname portalsuperuseraccount -propertyvalue account -url webappurl'. The account should be any account that has Full Control access to the SharePoint databases but is not an application pool account. Additional Data: Current default super user account: SHAREPOINT\system This means that the cache accounts for your web application aren’t properly set and that there will be a lot of cache misses. If a cache miss occurs the page the user requested wil...

There are times when you want to show the Workflow History only to Admin Users and not for normal users. But whenever a user clicks on the status of the Workflow, it redirects to the _layouts/WrkStat.asp and shows all information for all users. In order to avoid that, we can take advantage of the SPSecurityTrimmedControl. Open the WrkStat.aspx from 14->template->layouts in Visual Studio and then add <Sharepoint:SPSecurityTrimmedControl runat="server" Permissions="ManageLists"> in Line 128 and close the tag in Line 239. You will have the Workflow History Page appear like this for non-admin users :)

With SharePoint 2007 all you needed to do was edit the page in SharePoint Designer and remove the following 2 lines: < asp:Content ContentPlaceHolderId=”PlaceHolderNavSpacer” runat=”server”></asp:Content> < asp:Content ContentPlaceHolderId=”PlaceHolderLeftNavBar” runat=”server”></asp:Content> With SharePoint 2010 you also need to delete the following: < style type=”text/css”> body #s4-leftpanel { display:none; } .s4-ca { margin-left:0px; } </style> The quick launch will now display on the web part page. Make sure you do this in the Advanced Editor Mode of this WebPart page.

http://sharepoint.stackexchange.com/questions/13455/can-all-the-layouts-xxx-debug-js-files-not-be-served-to-end-users When I view my SharePoint site I see a lot of .debug.js files being added by SharePoint. Is there a way to stop this happening. cui.debug.js core.debug.js sp.debug.js sp.ribbon.debug.js init.debug.js they account for around 400k of the page download. Gotcha, in your masterpage, set the ScriptMode to Release, so that it looks like this:  <asp:ScriptManager id="ScriptManager" runat="server" ScriptMode="Release" EnablePageMethods="false" EnablePartialRendering="true" EnableScriptGlobalization="false" EnableScriptLocalization="true" />  –  James Love   May 26 '11 at 18:25

http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=253