Try our conversational search powered by Generative AI!
AI OnAI Off
| Views: | 8960 |
| Number of votes: | 5 |
| Average rating: |
EPiServer 7 – Patch 2
Mar 18, 2013
Today we are delivering a new platform patch that addresses a number of issues found in EPiServer 7. This patch is cumulative meaning that it includes the changes present in Patch 1. In this second update we have also simplified how the patch is applied by removing the need to update assembly binding configuration. Please visit the updated installations instructions for more details.
The list of fixes that has been added
|
92672 |
Empty property value also removes published value (on master language) |
\CMS |
|
94440 |
MVC: Visitor Group not work as expected |
\CMS |
|
96161 |
Improved logging for cleared cache and ASP.NET restarts |
\CMS |
|
93078 |
CurrentPage member in a EditPanel plugin does not work in upgraded solution |
\CMS\Core |
|
93628 |
RenderTemplateScanner public method is not virtual |
\CMS\Core |
|
95697 |
EPiServer.Data throw argument null exception when it gets missed events. (Bad code) |
\CMS\Core |
|
92738 |
FriendlyUrlRewriteProvider throws exception on upgraded site |
\CMS\Core\Friendly Url |
|
91768 |
ResolutionId for MVC IDisplayMode |
\CMS\Core\MVC |
|
92967 |
Template registration: A class that implements both IView and IRenderTemplate<T> will not be registered |
\CMS\Core\MVC |
|
92979 |
MVC: PropertyFor should store PropertyName |
\CMS\Core\MVC |
|
93017 |
Tagname in partial view without controller not working |
\CMS\Core\MVC |
|
93933 |
MVC: ViewRegistrator should be pluggable |
\CMS\Core\MVC |
|
95628 |
Not possible to add full refresh using the FullRefreshPropertiesMetaData extension method |
\CMS\Core\MVC |
|
94618 |
PageLink html helper renders incorrect URL:s on a partial routed page |
\CMS\Core\Routing |
|
91611 |
Make routing to pages more strict regarding language segments. Details about this change. |
\CMS\Multi Language |
|
90658 |
Performance: Many calls to netPageDataLoadVersion during editing |
\CMS\SparrowHawk |
|
95413 |
The page name must contain at least one visible character |
\CMS\UI\Edit Mode |
|
94334 |
Obsolete information on obsolete attribute for PageDefinitionType’s List method. |
\Internal Work\Doc |
|
92867 |
DDS(Indexing): Validation of dds throw exception if the model is not marked as indexing clolumn but in the DB the user has changed it to be be indexed |
EPiServerCMS\Core\Data Access\DDS |
|
91802 |
Problems with links in a mixed-language enterprise environment |
EPiServerCMS\Multi Language\Core |
|
95598 |
EntitySecurityHandler.Instance.AccessRightsSet event: data event does not contain new data |
EPiServerCommunity\API |
Installing the patch
The patch is available as a set of packages on Nuget feed on nuget.episerver.com. Refer to the installation instructions for information on how to install the patches to your sites.
Related documents
Comments
Please login to comment.
Great! I would prefer to have this information/link also on the CMS 7 download page (http://world.episerver.com/en/Download/EPiServer-CMS/?id=66773&epslanguage=en&version=7) since it would make it feel a bit more official.... Also, will the core CMS 7 installation be updated with this patch or do we always have to apply this patch on top of CMS 7?
Hi Johan, thanks for the input.
We are looking into how we can have the Installation/patch/add-on update process better described and linking to the latest updates from the download page is one way of simplifying the "workflow".
We are not planning to update the download package to include the latest patch since our deployment process does not support that (at least not in an acceptable way).
How is the official way of patching a load balanced production site?
@Fredrik: One simple fix would be to link this page under "Download Also" or even "Related Information" on http://world.episerver.com/en/Start/Download/Items/EPiServer-CMS/EPiServer-7---CMS/ =)
Hi Christian,
Applying a patch is a coding related task. That means that you integrate the patch in the development environment of your project and then publish the rebuilt project just as you would deploy new features to your site.
[Double submit by reload obviously not prevented =)]
Hi Patrik,
You are not downloading the patch yourself. Instead you let NuGet download it for you. See the installation instructions.
Hello Fredrik,
Thanks for information about this patch, great that updates come more frequently now! Also great that we don't have to change our assembly bindings manually anymore, however some of our bindings were't updated correctly when applying the patch, what kind of pattern is the postscript doing to find the correct assembly bindings to update I wonder?
Best regards
Martin
Hi Martin,
The script is essentially matching each binary in the currently installing package with the list of configured redirects. If there is an assembly name that matches, the redirect is rewritten with a new oldVersion range and of course a newVersion. Assemblies that are not present in the list of redirects before the installation starts will not get redirected. Perhaps this is what you are seeing?
I had to manually remove the DLL references in the project file after the installation so the new references could be applied. All rows to the episerver libraries/episerver folder:
Seems these conflicted with the new ones.
Shahin, To me it sound like you still have the dll-copy-build-step left in your project. This should be removed as described in the installation instructions.
So the DLL copy build step should be removed to support Nuget updates. What is the suggested way to handle project libraries to make sure all required libraries get included when for example publishing site? Reference all DLL:s and set copy local true?