This article describes the issues that are fixed in the Microsoft SharePoint Server 2013 hotfix package that is dated October 8, 2013.
Issues that this hotfix package fixes
When you use a publishing template on a SharePoint Server 2013 site, you cannot add a search box to the XsltListViewWebParts web part.
Assume that a blog contains more than 11 entries. When you go to the next page of the blog in the Archives view, the title of the page is displayed incorrectly. Additionally, you may receive the following error message:
There are no posts in this month.
When you try to join a custom group on a SharePoint Server 2013 site, you receive the following error message:
Sorry something went wrong.
As a search service administrator on a SharePoint Server 2013 farm, you cannot click the Query Rules button under the Queries and Results heading in the Navigation pane to view query rules.
Assume that you do not install or enable the DragUpload ActiveX control in Windows Internet Explorer 8 or Internet Explorer 9. When you click the New document button on a SharePoint Server 2013 document library in this situation, Microsoft InfoPath does not start.
When you follow a document on a SharePoint Server 2013 site that has alternate access mappings enabled, the link to the document points to the default zone instead of the alternate access mappings zone.
After you use SharePoint Designer 2013 to add a Dataform web part to a SharePoint Server 2013 page and to enable grouping on one or more fields, you cannot expand or collapse the group.
When you trigger an automatic approval workflow on a SharePoint Server 2013 site from a nondefault zone, the approval email message includes a URL that uses the default zone.
Assume that you add the Tag Cloud web part to a page on a SharePoint Server 2013 site that has the Save metadata on this list as social tags feature enabled. When you try to add a term in the Enterprise Keywords column for an item, the term is not added, and no tag is displayed on the Tag Cloud web part.
Consider the following scenario:
You create a SharePoint Server 2013 document library that has the versioning and "required check out" features enabled.
You upload a document to the document library.
You check in the document and submit a version comment.
You open the version history of the document.
In this situation, the version comment that you submitted is blank.
The number of downloads is not removed from the details page of an app.
Assume that you enable the WOPI Binding feature for a .pdf file on a SharePoint Server 2013 server. When you click the Open button on the .pdf file callout, you receive an error message.
When you add a client-side-connected web part that provides data to a consumer web part on a SharePoint Server 2013 site, the web part does not work in Internet Explorer 10.
Assume that you create a SharePoint Server 2013 site that contains a Managed Metadata Service (MMS) column. When you use the "multiple file upload" control to upload a document to the site, the values for calculated columns are not populated.
When you change the Ipersonalizable property of a web part on a SharePoint Server 2013 site, the property is not saved correctly.
Additionally, this update adds a new IT control to the SharePoint Designer client. This control helps you migrate WF3 workflows to a WF4 workflow environment.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
You must install the following public update before you apply this hotfix package:
2767999 Description of the SharePoint Server 2013 update: March 12, 2013
You do not have to restart the computer after you install this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
To use one of the hotfixes in this package, you do not have to make any changes to the registry.
This hotfix package may not contain all the files that you must have to fully update a product to the latest build. This hotfix package contains only the files that you must have to resolve the issue that listed in this article.
The global version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.