Updated General Hotfix CMS-6 R2
A new version of EPiServer Relate2 R2 has been uploaded under download section on episerver world after some bug fixes. This version is also compatible with General Hotfix for CMS-6 R2 (6.1.379.501). Follow these installation instructions if you want to patch an existing Relate2R2 installation.
A new version of EPiServer CMS-6 R2 has been uploaded under download section, which addresses the bug (#76625:Update schema in General hotfix doesn't included when upgrading) along with some other bug fixes. See the updated list of fixed bugs here.
Newly uploaded installation package has following assembly info:
File Version: 6.1.379.501
Assembly Version: 6.1.379.0
We at EPiServer developer support have been getting requests from our partner developers for hotfix(s) of different bugs which appeared in cms-6R2. So far, we have provided different hotfixes to different partners for their issues.
Now to ease the developer’s life, we have created a general hotfix for CMS-6R2 which addresses the most common bugs in CMS-6R2 and for those we have already provided hotfix(s) to different partners.
Download the latest version of EPiServer CMS 6 R2 from here.
Note1: Security vulnerability issue which Jens Nygård blogged about is also included in this general hotfix.
Note2: Partners who want a patch into existing CMS 6R2 installation should follow these installation instructions. Apply the database changes by running this script on an existing 6R2 database.
Is these hotfixes applied to the Software Installation package?
Yes, a new version of Software Installation package has been uploaded under "download" section and it includes all the fixed bug mentioned above.
Excellent! Great work EPiServer Support!
Finally, thanks! :)
Thanks support! Is there any reason this wasn't released as a service pack? Manually patching existing installations is a bit of a pain (and a bit risky) so would prefer a service pack that can be run through the deployment centre.
@Celia, the goal was to make minimum impact on sites that you want to patch. The fact that you have to copy the dll's to the bin folder is the only changes to files required in the site. When we are releasing service packs the impact on the site is generally much greater. For service packs we typically update assembly version, change configuration, update the database schema etc.
Do you have to update all R2 sites when you have installed this patch (run DB scripts etc) or will old R2 sites still work without any changes after the installation?
I have been waiting for this for along time. Thanks for finally releasing it!
@Viktor, Actually, it's a required to upgrade all R2 sites on a machine and for all sites that share the same database. Given that the CLR will prefer the GAC:ed assemblies (over assemblies in bin) you will effectively patch binaries for all sites on a machine by doing the reinstall of the msi's. The copying of files to the bin folder is for hygienic reasons to keep everything in sync.
Regarding the schema update, you need to apply that on all R2 databases affected by the patch.
Is the "Fetch pages from" DB script 0006_0000_0535_0000to0006_0001_0233_0000.sql
included in the installer?
@Daniel, Indeed! It is refered to as:
64439 Some fields of tblWorkPage are null after upgrading from CMS 6 to R2
in the bug list.
Seems like the database-script was not added in the installation-package. We had to run the script manually after installing the CMS6 R2 installation (updated January 25).
I installed this on one of our servers. However when I uninstalled the current version of 6r2 and then installed this version the GAC was not updated. I had to manually install the new EPiServer.dll into the GAC myself. Should the install have put the dll into the GAC? As the bug fix I needed was not fixed until I put this in the GAC.
We're on a tight schedule close to production and we really need to know the details on some of these bugs in order to decide whether to invest some time into trying to apply this patch.
I tried to look up some of the fixed bugs in that wonderful (sarcasm intended) bug list tool over at http://world.episerver.com/Support/Bug-List but no matter what filters I try I fail to find some of the mentioned bugs...
How can I find the details of a bug if I know the bug ID? Seems like a simple request..
@Johan: You can search the bug against its title in the bug list. Below is how I did:
Qurey Fixed/known Bugs | EPiServer CMS | 6R2 | "title of the bug" | All Keywords
However if you still find some trouble, send a query to developer support to get all the required details.
OK this is fun. Let's pick the last bug in the list, 75277. Copy the title. Paste it into the freetext field. First search "Fixed bugs". Wait like 10 seconds. 0 hits. Hmm ok, thought it was fixed. But let's try search "Known bugs" then. Switch in the first combo and search anew. Again wait 10 seconds... 0 hits. I still think it is very strange that you cannot find a bug either by ID or title... Where do I file my complaints? =)
Totally agree with Johan. The bug list is very hard to use and makes it hard for us to help report bugs :/
+1 on the buglist sucking.
When are you going to update the NuGet packages with this release? If you are to make a point out of the repository, it should be updated simultaneously as executables are shipped.
I have ran the script on CMS 6 R2 following the steps and Fetch pages issue is still there. It is still missing all the link pages on the site. Is there a easy way to rollback the site from R2 to R1?
@Mohammed: Sorry, i don't have a solution for rollback to R1. Should be easy if you restore the database from old backup before upgrading to R2. (if you have one).
Regarding "fetch pages issue", it should have been fixed in the hotfix anyhow could you please run it through developer support and leave all information in support ticket.
Thanks Shahid. I have raised this with Developer support. I rolled back my databse as I initially upgraded from CMS 5 R2. When I upgraded to CMS 6 R1 I am getting the same issue so it is not only when upgrading from CMS 6 R1 to R2 it is also happening when you upgrade from CMS 5 R2 to CMS 6. Any idea if there is a fix for that some where?
Any chance you could do a real service pack where you update the assembly version?
It is hard for us to keep track of what version our customers sites are on when the same assembly version is used.
@Alex: There is no such plan of releasing a service pack now since dev teams are finalizing the code for Falcon release. Releasing a SP means alot of efforts, to make all the products, modules, connectors compatible with latest release.
For every hotfix, we only update the assembly file version, which is somehow easy to back track.
Could you please update the nuget?
You need to be careful when upgrading a server with Community / Relate Plus. If you install (i.e. run setup.exe) the new 6.1.379.501 version of CMS and then install Relate Plus R2, the newer files in CMS will be overwritten. This is because the Relate Plus installer also installs a version of CMS (the original). Both the new and old CMS msi files presumably have the same version number which means they will overwrite each other regardless of whether files are newer or older.
If you install Relate Plus after the 501 version of CMS, you will loose many important fixes from 501.
Thanks for sharing Paul.
I think this is a real mess. R2 is seriously buggy (the one that gets the most complaints from our customers is the one when you get an error when you publish a page at random times, and the XHTML property serialization bug cripples dynamic content to near useless). I know the team is busy with Falcon, but you need to support CMS 6 R2 as well.
You have already made the hotfixes part of the CMS 6 R2 download, so you will need to ensure compatibility with other products and modules anyway.
Please clean up this mess and release a service pack.
Seriously this is a f#¤"#¤ mess. Release a service pack for all products. It is not that funny to make other sites bad because you like to make one site better. we have also had some trouble with the problem regarding installing relate on a server with the hotfix for r2.
You need to ensure that all your download packages that have the cms installer are updated with this hotfix..
As Alexander said:
Please clean up this mess and release a service pack!!
I totally agree with Erik and Alexander: Release this as a service pack!
Indeed, please release as a service pack instead.
I agree, this is causing a big mess in our daily work.
+1 for service pack
+1 for SP
I came here because of the "Column 'SecondsAfterLastPing' does not belong to table Table" error caused by the original hotfix (http://world.episerver.com/Modules/Forum/Pages/thread.aspx?id=56972&pageIndex=1).
Guess I'll have to join the choir and say +1, make a proper service pack.
I have upgraded from 6R2 v 6.1.379.1 to 6.1.379.1000. After I managed to sort out the mix of different versions of log4net being used by different EPiServer products (cms/framework/etc) it now seems to work fine, except I haven't run the SchemaUpdate.sql script because I cannot find it. It says it should be "under attachment on the target site (6R2) database." Could someone please tell me: where is that?
You don't need to run the dbscript anymore. These are the updated patch-installation instructions.
Thank you for your rapid answer, Shahid. :)