Errors

Sometimes we use the Sitecore class called UpdateHelper to install packages on different Sitecore instances for example via a webservice. Today I copied some code from a Sitecore 7.2 installation which did exactly this. It is a simple service class that installs a package from a path and then it logs the installation results as done by the Sitecore InstallUpdatePackage wizard. public static string InstallUpdatePackage(String packageFile) { var log = LogManager.GetLogger("LogFileAppender"); string result; using (new ShutdownGuard()) { var packageInstallationInfo = new PackageInstallationInfo { Action = UpgradeAction.Upgrade, Mode = InstallMode.Install, Path = packageFile }; string text = null; List<ContingencyEntry> entries = null; try { entries = UpdateHelper.Install(packageInstallationInfo, log, out text); } catch (PostStepInstallerException ex) { entries = ex.Entries; text = ex.HistoryPath; throw; } finally { try { UpdateHelper.SaveInstallationMessages(entries, text); } catch (Exception ex) { log.Warn("Unable to write the installation messages", ex); } } result = text; } return result; } But the code would not compile when using the Sitecore.Update.dll from 7.5 ...

In the current version of ECM the same mail message will be sent several times to the same user if the user has registered several times to the same target audience with a different user but the same email. The issue is really that the email recipients are not filtered by distinct emails before the newsletter is dispatched. Personally I would have thought that ECM ensured that emails was distinct before it dispatches the mail but this is not the case ...

The silence is broken, this is my first blog post for the last 3 weeks time since I’ve been renovating my apartment. But now I’m back first with this small information post. I was installing a clean Sitecore 7 with ECM 2.1 and design importer 2.0 for Sitecore 7 yesterday. The design importer was working fine in the content editor but when trying to create a new message in ECM I received the following exception. ...

I’ve been working a bit on an extremely weird support case the last couple of days. When the editors on a site clicked on preview from either the content editor or the page editor then the page ended up in a redirect loop. Who stole my cookie? Using Fiddler I quickly noticed that the .ASPXAUTH cookie was removed from the session as soon as preview was clicked and what actually happened was the user being redirected infinitely to the login page until the browser crashed (chrome crashes nice, IE just fails miserably). ...

When update 6.6 rev 130111 was released I upgraded a customer solution from the previous 6.6 release thinking that this was only a minor update which would solve some of the other issues the previous revision have had. I was terrible wrong and the upgrade led me into a ton of trouble. The first issue in the new revision was an added processor in the renderField pipeline. <renderField> ... <processor type="Sitecore.Pipelines.RenderField.GetTextFieldValue, Sitecore.Kernel" /> ... </renderField> This processor ensures that all text fields and multi line text fields is output escaped when rendered through the renderField pipeline. ...