It’s seems that during the dispatchnewsletter pipeline the code is execute inside a securitydisabler block / context, so any effort to change the user context with a userswitcher is useless, as even changing the switcher, the security is not enabled, so you user is “administrator” at this point.
The default drop down for the font size in the RTE, have a list of relative numbers, which will be translated into px, in the html.
The scope of this post is just about how to enable / install the Microsoft Ifilters pack; How to use them in your code is a different matter, but i can tell you using IFilters will be OOTB with Sitecore 7.
As we commented on previous post the default configuration of the Sitecore Azure module 2.0 moves the log files to table storage.
When you use the Module Sitecore Azure 2.0 to move your Sitecore web site to Azure, you lose the log files and the old log viewer become useless.
The first thing you need is to set up the service configuration file to load the “Remote desktop service”.
I´ve been using Log parer lizard thanks to The Client View for a while to review sitecore logs, but today I found it didn´t work for my instance with sitecore 6.6 and the Azure module logs, it was throwing any error, but any result either.
The Windows PowerShell is as task-based command-line shell and scripting language (We’ll, not everybody agree: Windows power shell is not a scripting language). There are two main differences with common “shells”:
We can find a good, free and Open Source reporting framework, ready to install on the SiteCore Shared Source Modules, called Advanced System Reporter.
One of the most common tasks when branding a SharePoint installation is to generate custom master page to be used in your freshly branded site