A message from our CEO about the future of Stack Overflow and Stack Exchange. Read now.
16

There are potentially 3 places in the web.config to modify to extend session timeout: <!-- AUTHENTICATION CLIENT SESSION TIMEOUT Specifies the number of minutes before Sitecore considers user authentication session tickets as expired. This setting is only relevant for users logging in to Sitecore Client and when the Sitecore license has a ...


15

Things to keep in mind Whenever you have a site with user-generated content, you need to make sure that you keep the following in mind: Security is both more important and more difficult If storing user-generated media, performance can be a major factor, depending on the media that you are storing, how you store it, and how media-intensive the site is If ...


15

You may be able to package up both paths of the content tree and use something like WinMerge or Kdiff to do a item by item comparison, which might be quick and dirty but may be hard to wade thru especially in instances of inherited fields. I usually like to see if I can use Sitecore Powershell Extensions to complete potentially repeatable tasks like this. ...


14

Move the root item. Step 1 Step 2 Result EDIT: Included to add this And yes, as you point out in comments. Instead of publishing this change, execute this operation in both "master" and "web" (and as needed, if you have more databases in play)


14

You can use targetHostName setting in your site definition. It tells Link Manager to use that host name while generating url. It doesn't change the way how sites are resolved on your CM and CD servers. This only tells Sitecore to generate links using that particular host name for your site no matter if you're on CM or CD server. You can read more about ...


13

Scroll to the bottom for the updated answer This format (with T in the middle and ending with Z) is called by Sitecore ShortIsoDateTime. I don't know if that is official name of it or not. You can get it using Sitecore.DateUtil.GetShortIsoDateTime(dateTime) method. There are more formats which are used by Sitecore. Sitecore.DateUtil class is a really ...


8

The main thing you need to set up is the Instance Names in your ScalabilitySettings.config file. The names can be anything they just need to be consistent between the CM and CD. You can leave these blank and Sitecore will create it's own unique names which can cause issues if you switch IIS sites, so it's safer if you create the names yourself. On the ...


7

Although Sitecore has great support for multi-site and multilingual implementation, there is no 'silver bullet' design that works for every situation. Below I described four options we use for our sites. Hopefully you can use one of them or build your own. 1. Separate Site MyWebsite.com |-Page1 |-Page2 MyWebsite.eu |-Page1 |-Page2 Every ...


7

Answer to this question will slightly vary on your Sitecore Version but I am listing out most common differentiating factors. If earlier both the environments were configured correctly than you can easily find out the following difference: Sitecore Admin Panel and Admin pages Mostly Sitecore Admin Panel and Admin Pages is restricted on the CDs. Hence if on ...


6

Audit information is available in the logs, and I thought there was a way to isolate them in a separate log file by changing log4net settings. But you could also use the Audit Trail module from the marketplace: https://marketplace.sitecore.net/Modules/S/Sitecore_Audit_Trail.aspx Helps you to answer following questions: Who did change? When it ...


6

You can refer to the Sitecore Scaling Guide from SDN: https://sdn.sitecore.net/upload/sitecore7/70/scaling_guide_sc70_a4.pdf P.s. Keep in mind that http://doc.sitecore.net contains documentation only for Sitecore 8+ versions. Thus if you are looking for documentation for Sitecore versions prior to 8, you should refer to the https://sdn.sitecore.net/


6

While Vandsh's PowerShell script is very nice, I think I would use Unicorn and Beyond Compare. You can configure Unicorn to ignore fields as needed. Once your items are serialized, use Beyond Compare to merge your changes. If you have Unicorn's transparent sync enabled it will automatically pull your changes into Sitecore. Otherwise, you can manually ...


5

There are a number of ways to go about this - it depends a little bit on how ambitious you want to be with this. One way is to configure a new site on your CM server (a Sitecore site definition), make it respond to a different host name (so preview.cm.internal or whatever). Sitecore includes Livemode.Config.example to show how this can be set up. Another ...


5

You'll need to run your CM instance in Live Mode. Running a site in Live Mode means that it reads items directly from the Master database. At the same time, your web connection string is preserved and you are still able to publish from Master to Web. To enable the Live Mode, go to App_Config/Include and rename the file LiveMode.config.example to LiveMode....


5

Your CM and CD servers are available by different addresses.(e.g.: cms.test.com and www.test.com) It is possible to filter redirect rule before execution using {HTTP_HOST} variable: <rule name="Force SSL" stopProcessing="true"> <match url="(.*)" /> <conditions logicalGrouping="MatchAny"> <add input="{HTTP_HOST}" pattern="...


5

Quick and clean solution: Create a new template (called "Folder with default item" or whatever you prefer), inheriting from the standard Folder template Add a field to your custom folder (e.g. Droptree, and set the Source of the field to query:./*) Add new httpRequestBegin processor after ItemResolver. Use code (not tested - try and fix if needed): public ...


4

The best way to fix this would be to move to SOLR - really its the safest way to ensure that the index is the same for all delivery servers. On top of that you get additional things like the query cache, better language indexing and better scalability with Solr Cloud. If you absolutely must stay with Lucene, you could setup the CM server to build the ...


4

One reason for this behavior may be having an httpCookies domain setting in web.config that doesn't match the domain you are using to login to the Sitecore client, or having httpCookies requireSSL set to true while login in on http instead of https.


4

This is a very subjective question as a lot will depend on your requirements. My general rule is: If the sitemap for all language versions of the site is the same with maybe a few minor differences, and its only the content that will be translated, maybe a few module differences, then I will use option 2. A single site tree with versions for each language. ...


4

The contextual ribbon is controlled by the Ribbon field on the template of the item you are on. So for images, it would be on either the /sitecore/templates/System/Media/Unversioned/Image or /sitecore/templates/System/Media/Versioned/Image (also could be on the Jpeg templates - depending on the type of image you uploaded). Those ribbon bars are defined in ...


4

I just attempted this in Sitecore 8.2 Update 5 with no issues. Here are the steps. Step 1 Open an Item with a Rich Text field and enter some text. Step 2 Select the text you want to use for your anchor tag and then click the Hyperlink Manager button. You should be presented with the pictured dialog. Note that to set an anchor, you need to switch to the ...


4

You can adjust the security rights In the core database item: /sitecore/content/Documents and settings/All users/Start menu/Right/Development Tools/Install Package default: read right for sitecore\Sitecore Client Developing You can remove that right, see the Security Field of that item. Than only the admin has access to the Package installation ...


3

Try to make your "Author" role a member of "Sitecore Client Publishing" role to view and modify a subset of items, and can publish only a single item.


3

Adding some additional context, mentioned in other answers, the Sitecore Scaling Guide which is available on the old Sitecore Developer Network site is intended for versions of Sitecore 7.0 to 7.2. In this guide, Chapter 2.4 specifically, talks about how to convert a CM instance (which is the standard Sitecore install) and make it a content delivery server. ...


3

For the non-CMS users i.e. who do not have access to sitecore, we can extract content through Powershell extenstion Reports as shown: Sitecore Powershell Reports: Extract Options: please note that we have many audit reports like Configuration Audit Content Audit Media Audit Solution Audit we are frequently using Broken links audit which is very ...


3

From the experience I have with Sitecore, we have rolled out 70+ sites on sitecore. Below are the following points/practice we usually follow when implementing our sites. Content Sharing You may have a main content repository which stores all the common content for the different sites. Contents that are specific to a site are created under the site node. ...


3

Another super fast way to do this is using Sitecore Powershell Extensions found here in the Sitecore Marketplace (https://marketplace.sitecore.net/en/Modules/Sitecore_PowerShell_console.aspx). SPE is now one of the most popular modules for Sitecore. In one line of code you can move one or thousands of items very quickly as in this example below: Move-Item -...


3

To start off, I would always recommend training for someone who needs to make use of a WCMS platform before they go in. There is always going to be so much involved. One option is using the sitecore apis you could always create a Wizard Tool that works through content creation or managing content for certain pages. The cost and time effort of that would be ...


3

As Marek mentioned, you should set @targetHostName on /configuration/sitecore/sites/site in your Sitecore.config. Furthermore, you should create your UrlOptions object like this: UrlOptions urlOptions = LinkManager.GetDefaultUrlOptions(); urlOptions.AlwaysIncludeServerUrl = true; This ensures that your code keeps using the settings of LinkManager, except ...


3

If you would like to avoid changing core Sitecore templates, you could consider another approach and adding a contextual right-click action to the item. That way it wouldn't matter what ribbon loaded because you would always have the right-click option available. Outlined here: https://cardinalcore.co.uk/2014/08/20/simple-sitecore-tip-right-click-publish-...


Only top voted, non community-wiki answers of a minimum length are eligible