This is our new mantra in the digital marketing world we are living now and Sitecore has taken it seriously.
How many times have you right-click on an item to publish it to remember that this option is not available? How annoying it is for you, having to go to “Publish” tab, click on publish item, etc…
By default, when we index our content in solr (same for Lucene) Sitecore creates a document per item, and store the value of each (Sitecore) field in its related field in Solr.
Some months ago we had to move our servers from Germany to North Europe and recently windows is asking us to provide a valid product key.
Recently, one of my biggest instances went mad and decided to consume all the available memory on the server, to finally die and restart. No deployment, nor code changes, no editions, nothing…
Recently I have been having issues while trying to send really long queries to Solr from Sitecore. Sometimes my problem was Solr rejecting the request, other .Net itself complaining about the length of the uri.
Since Document DB started supporting Mongo’s protocol I was wondering if we could have Sitecore running on Document DB.
And today I managed to get it running.
Installing uCommerce on a content delivery server is pretty simple, nothing new, just install the package on Sitecore and done.
Perfect! everything is up and running, but… what if now you follow the standard procedure of “security hardening” for a CD server?
Every Sitecore developer knows (or should know) about the configuration transformation files under the folder app_config/include.
If you ever notice that links are not working when somebody receives an email sent by Sitecore Email campaign Manager, but after a while, without doing anything everything starts working, you may have a problem with the publishing queue.
The good old “news mover” (Or item mover) has been there helping in most of my project, so I thought it´s time to give something back.
First of all, keep in mind this is just a “prove of concept” and all the security concerns this kind of solutions could have.
As you know, sitecore search is based on Lucene. Lucene uses Analysers and filters in order to “read” and “query” the content. By default sitecore 7.0 (131127) is configured to use by default, the Lucene standard analyser.
Has shown on my previous post “Using real pixels in the rich text editor of sitecore” is it possible to change the relative font size in the RTE drop down
If you try to add a link to an anchor somewhere else in your email, you’ll realise ecm could be replacing your link with the base url.
How to fix the error 532462766
Sitecore Azure module 2.0 has an error on the default transformation code of Content delivery farms.
Do you have these symptoms in your site?
The link table (Usually in the core database) is too big, even bigger than your master or web databases
Recently, I tried to upgrade my sitecore CD server with the Upgrade Files option of Sitecore Azure Module 2.0, but after creating the package it shown an time out error: