Do you have any plan to implement a sane version numbering system? As now there are 3 different version numbering systems, you have episerver v7 and 7.1, patch 1,2 and 3, and the actual assembly version numbers that are seen in the nuget feed, the "patch x" numbers are not visible anywhere in the nuget feed.
Is there a version number translation table somewhere on the site I have missed?

Agree it is a mess and not to mention very hard to remeber the updates when you start a new project from VS where these patch is not included. It is not that easy to remember to apply these updates from nuget when you just installed the vs integration from world. Could you please update those packages so that they include the updates?

@Martin, the bug you mention is fixed but is not possible to release in a patch as it requires changes in artifacts not included in the patch. Regarding the bug list we are working on a new version that will include EPiServer 7.

@Erik, @Eric - We understand that this can be confusing. An explanation to this is that we have both technical and marketing requirements on release versions that don't always play well together. With that said, we could improve by decorating the NuGet packages to include the patch name as suggested by Erik. In the same manner, packages in the add-ons feed should include the marketing name.

Thanks for your feedback!

@Fredrik, Ok, good to know. Do you have any information about when this fix will be available? Or is it possible to get a hotfix becuase this is stopping us from upgrading one of our applications.

I just applied the patch, and it seems to update Web.config. However, the episerver.framework/virtualPathProviders element in EPiServerFramework.config is not updated. For example, is not updated. Should I be worried about this?

@Christoffer, no worries, this is the expected behaviour. After applying the patch the site will still use the RTM versions of scripts and markup which is configured in the VPP section.

I'm a bit confused with these patches...I'm fairly new to EPiServer. I'm going to assume that patch 1 <> EPiServer 7.1. So I guess my confusion is can or should these patches be applied to 7.1 installations?

@fredrik
I am not new to this kind of confusion between marketing naming and actual technical versioning.
Sun was infamous in this regard with their OS numbering.

But the Sun developer website always contained a simple overview matrix to assist developers with mapping the marketing naming with the underlying technical version numbering.
From this overview page you could also find links to the release notes and hotfixes to make the different versions play nicely with each other.

I would suggest that EPiServer follows Suns approach on this, as it is one of the things they got right.

after upgrade, the shortcut functionality stopped working. I can't open my homepage now, it kept saying 404

@code monkey, Can you mail me a more detailed scenario including full stack trace. Mail me at (ft at ep dot se).
@Martin Gray, thanks, a matrix should be possible to put together.
@Ben Rooney, yes, patches should be applied to 7.0 and 7.1 sites.

After updating the CMS on page editing of elements is broken and not all items are showing the "epi-overlay-item" blue box style, the Form editing shows as normal, it looks mainly to be local block content.

Previous version EPIServer 7.1 - Patch 2

Update so far after further testing:

If I attach the edit hints back via the page controller then it seems to be ok, for example:

var editHints = ViewData.GetEditHints, StartPage>();
editHints.AddConnection(m => m.CurrentPage.ThisBlock, p => p. ThisBlock);

The properties names are not changing via the view model so don’t know why it is not automatically mapping as per tech note:

http://sdkbeta.episerver.com/SDK-html-Container/?path=/SdkDocuments/CMS/7/Knowledge%20Base/Developer%20Guide/Content/Pages%20and%20Blocks/How%20To/Edit%20hints%20in%20MVC.htm&vppRoot=/SdkDocuments//CMS/7/Knowledge%20Base/Developer%20Guide/

alternative to this if the Html.EditAttributes is added in the view it becomes editable, so either I need to add edit hints via custom controllers/page view model to work or wrap an extra edit attribute but prior to Patch 3 it automatically mapped these using the Html.PropertyFor and allowed the property to be edited.

I agree with EPiDev, this is a new problem after patch 3! And we also have exactly the same problem. The strange thing is that the first contentarea on the page is working but not any contentareas which renders after.

Thanks Daniel and EPiDev,

We will try to reproduce this and investigate the cause. I'll update this thread as soon as I have further information.

Edit: This has been reported as a bug (#104316) which is planned to be included in the next patch release.

Fredrik, I've applied this patch to a project in dev environment. But now I want to apply the patch on live ennvironment, and have no idea what files have been added/modified. Is there any documentation of that?