So I see my fellow bloggers Paul and Khurram posted about Service Pack 2 for SharePoint and Project Server 2010.
Having looked around the blog-o-sphere, I came across some extra information that I believe will be useful to all:
Known issues when you install Office 2010 SP2 and SharePoint 2010 SP2
In particular if you are installing Office 2010 SP2 on Windows Server 2003 (SP2) you will need to install this patch first: http://support.microsoft.com/kb/925336
For SharePoint Server SP2 on Windows Server 2008 R2, you need to be careful of your custom XSL views from SharePoint Designer. Apparently they break but the fix is already available and it is recommended to install the June 2013 CU (or later) on top of the SP2
Links for June 2013 CU for SharePoint 2010:
The Full Server Packages for June 2013 CU are available through the following links:
- Download SharePoint Foundation 2010 June 2013 CU
- Download SharePoint Server 2010 June 2013 CU
- Download SharePoint Server 2010 with Project Server June 2013 CU
After installing the fixes you need to run the SharePoint 2010 Products Configuration Wizard on each machine in the farm.
Locations of all the SP2 download packages around SharePoint, Project Server, FAST, Office Web Apps, Office 2010 products etc…
Next up is that we of course need to consider the different products that we have installed in our farms. Do we have FAST or Office Web Apps?
This link will help: http://support.microsoft.com/kb/2687522
Further links are available here, including Office, Project, Visio, SharePoint Designer and the CSOM binaries:
- I haven’t seen a service pack 2 for the language packs yet, but will update if it comes up soon.
Changes for SharePoint / Office 2010 SP2 that are not in Cumulative / Public Updates
Handily Microsoft have also released a spreadsheet detailing the changes and additions as part of Service Pack 2. Be aware that these are not included in any previous CU / PU.
Ok, hopefully you will all find the above useful. Till the next time…
We created our own results page: Results.aspx
We can modify the “Refinement Panel Web Part” only if we can edit the create a new .aspx results page and change the “Search Setting” to point to the new Results.aspx page instead of the default: 00SSearchResults.aspx
Now that you can edit the “Refinement Panel Web Part”. You might also want to customize which refiner’s appear in the web part. This video will show you how to edit the XML.
Other helpful links:
While customizing an “add new item” form, you might find yourself needing to manipulate form elements via jQuery. However, before you can do that you must and an #id or .class to the elements in question. I will be adding an #id in this demonstration. But why would I want to manipulate form elements in the first place? If you wanted to hide/show a textbox based on the user selection of a checkbox you could use this technique.
How do I: Implement $().SPServices.SPLookupAddNew
Using jQuery to hide/show form elements based on checkbox value
How can I validate a textbox using the PreSaveAction()
How do I: Create a simple form to collect data in SharePoint 2010
How can I hide/show a textbox based on a radio button selection?
How can I hide/show a textbox based on a drop-down value?
In my opinion, the tricky part to this is the third list “CascadeExample”. It was unclear to me after reading the documentation on the SPServices website that the two columns “Country” & “Region” in the “CascadeExample” list need to be lookup columns. It might be obvious to everyone else.
InfoPath 2010 is a great tool. However, while building forms in InfoPath it’s only a matter of time when you have a user requirment that InfoPath alone simply will not do. In that case you might have a few options. You could add custom code using VSTA, which means you will need to publish them as an administrator approved form template.You could ditch InfoPath completely and build your forms in Visual Studio 2010 using asp.net. You could build them using the client object model. Lots to think about. In addtion, you could manipulate some form element using jQuery. The video demonstrates a simple way to hide/show a textbox element using jQuery.
Let’s say you wanted to hide/show a specific textbox only if a specific checkbox has been selected. You can use jQuery to do this via SharePoint Designer 2010
This was done on a SharePoint Online site.
This was done using a SharePoint Online site.
Building forms using SharePoint Designer can be a bit tricky at times. What if you wanted to a text box to show only if a certain radio button value is selected? This video will show you how I acheived this using jQuery.
This post might also help:
Validating a SharePoint form field in SharePoint Designer 2010
Using jQuery to hide form elements based on drop-down value.