People who code: we want your input. Take the Survey
16

It's easier Today if you work with Sitecore 9, you can do it from your Content Management server. Just go to /sitecore/admin/ShowConfigLayers.aspx and select Content Delivery. This is article explaining in details how to View configuration changes


12

You could use the Sitecore Config Builder to do this. It is available from the Marketplace. https://marketplace.sitecore.net/modules/sitecore_configbuilder.aspx This will allow you to view the compiled config without needing to open up the /sitecore directory for access. It also has an option to show the entire compiled web.config and not just the ...


10

You can have multiple versions of Sitecore on a single server. Firstly, just install them into different folders and have them pointed to different Databases. And secondly either have them both sit on their own domains so they can both run simultaenously, or if they need to sit on the same domain, then switch in IIS between the two. I'd recommend having ...


9

There is no out of the box way to make custom link manager configurations scope to a particular site, however you could always include that logic in the custom link manager itself. You can make your link manager resolve the site that a link is for. Then, if the resolved site is Site A then use the custom link manager logic; otherwise, if the resolved site is ...


8

The fast answer is that the publisher site is used for publishing related jobs. But, you probably already knew that. Why is publisher used in Publishing? When one pulls the covers back a little on the Publishing process, it's revealed that Publishing utilizes the JobManager to manage publish processes. This is to allow for asynchronous processing to occur ...


8

It is safe to delete the default Home item. I have done so on many projects. The only place where you need to update the reference is the default site definition: <site name="website" ... rootPath="/sitecore/content" startItem="/home" ... /> Some system sites, such as "shell" and "modules_website", also have references to the Home item. ...


8

It's lowercase hostname in your defintion. There must be capital N: hostName. Site attributes are case sensitive. Should be: <site name="website" enableTracking="true" virtualFolder="/" physicalFolder="/" rootPath="/sitecore/content/brands/clientname" startItem="/home" database="web" domain="extranet" allowDebug="true" cacheHtml="true" htmlCacheSize="...


7

The simplest way would be with security. If you give each site a unique domain and then simply deny read access to the {sitedomain}/Anonymous user it would give you what you want. So the site definitions would become: name="Jack" hostName="jack.com|www.jack.com" enableTracking="true" virtualFolder="/" physicalFolder="/" rootPath="/sitecore/content/Jack" ...


6

Here's how I would approach this: Define a rendering that shows an overlay on any page it's included in. When a user selects a country via this rendering: Send an AJAX request to the server; Take any actions needed based on the user's selection; Add a cookie to the user's browser indicating that a country has been chosen; Hide the overlay. Include this ...


6

Yes, this is a convention that Sitecore uses as triggers for a number of custom handlers: <customHandlers> <handler trigger="-/media/" handler="sitecore_media.ashx"/> <handler trigger="~/media/" handler="sitecore_media.ashx"/> <handler trigger="~/api/" handler="sitecore_api.ashx"/> <handler trigger="~/xaml/" ...


6

Do you have any additional customization in web.config? If yes, try breaking your web.config and put your customization in separate patch files. Meanwhile also have a look at the blog post below, if you are on 64 bit OS then the registry to be edited is different. https://himadritechblog.wordpress.com/2014/09/27/how-to-fix-cannot-read-configuration-file-...


5

I have resolved this a few different ways in the past: Redirects using the IIS Rewrite Module, which is my preferred solution. It does require that the IIS Rewrite Module be installed in IIS, and it is a little more work than the Securities solution, but I prefer it because it changes the URL and caches the change as a permanent redirect, in case any online ...


5

The reason why you are receiving the SiteContext as micrositemain is because url.Host will return microsite.mysite.com. Please see updated SiteDefinition below: name="micrositemainone" hostName="microsite.mysite.com" virtualFolder="/{language_here}/company1" //ex: /en/company1 startItem="/en/Home" physicalFolder="/{language_here}/company1" rootPath="/...


5

I once had to tune a server with Sitecore because we did get a lot of requests and couldn't add more servers (for several reasons). I used this blog as a resource, and although it is a few years old it helped me get a significant amount of extra requests handled on the same infrastructure and code. To answer to the MaxWorkerThreads, I did indeed put that at ...


5

This works because of the way that HtmlCacheClear processes the <sites> list. When you take a peek into the code for HtmlCacheClearer.ClearCache() method, you'll see that it's iterating through the list of sites in a basic for() loop. Therefore, the element name of the list item makes no difference whatsoever. As for how it changed to MyCompanyName ...


5

The issue is the extra <settings> node in your project module config, at the moment you're not patching anything but inserting a new entry within the <settings> node (and it's probably not where you're looking in showconfig.aspx) <configuration xmlns:patch="http://www.sitecore.net/xmlconfig/" xmlns:set="http://www.sitecore.net/xmlconfig/...


5

The only site that needs to be https is the xConnect service, though your Sitecore site is extremely highly recommended to be https as well. Since you are an XP0 configuration where everything is on a single machine, you can create a self-signed certificate to use with the xConnect service. However, you will also need a SSL client certificate for your ...


5

It is not possible to preview an item when you change the publish restrictions and make the item (or one of it's parents) not Publishable. The logic being, from my understanding, is that you are trying to preview how an item will look to the end user once published, if you make an item unpublishable then the end user will never be able to view it. Setting ...


5

In a nutshell, the JSS app's config patch (usually deployed to \App_Config\Include\zzz\my-jss-app.config) is resolved before SXA sites. When the SXA module is installed in Sitecore, you get a bunch of new configs. Of particular interest for this issue is this patch file that says where to place the SXA sites: <!--\App_Config\Include\Z.Foundation....


4

The publisher site is responsible for actually running the publishing of your content. Simple Answer The simplest answer that I can give is that this is one of the ways that Sitecore implements multi-threading/parallel processing in SXP. Since publishing processes in a separate site, you don't have to worry about your publishing operation interfering with ...


4

Sitecore.Globals.ServerUrl is set in the Globals.Load function by calling WebUtil.GetServerUrl(HttpContext.Current.Request.Url, false). The code for that is: public static string GetServerUrl(Uri url, bool forcePort) { if (url == (Uri) null) return string.Empty; string scheme = url.Scheme; string host = url.Host; string @string = ...


4

The path to your license file is set incorrectly. The default value of the license file setting in config is: <setting name="LicenseFile" value="$(dataFolder)/license.xml" /> If you have not change this, then most likely the issue is the dataFolder variable is not set correctly. Use a patch config set to update it to match the folder path your ...


4

This is down to how Sitecore patches child items. The same thing happens if you try to patch the publish:end configuration to add your site in. The problem is that because each of your mapping entries are effectively the same and don't contain any patching hints, each row patches the one above. To solve that you can add a hint attribute to each row like ...


4

I doubt you'll find any recommendation for HDD size because it totally depends on your needs, configuration and needed modules. However, a basic Sitecore 9 installation is around 2gb without any css, js, images, custom DLLs or configs. You'll have to estimate these for your project. You can find xDB requirements here


3

You need to check the default site definition and your custom site definition nodes in the config file. It must not include /home path as start path and master as a database. You don't need to care about modules_website as it is not using the Master database. And regarding the Sitecore.UIUtil.GetHomeItem method, it won't create any issue. If it can't ...


3

Yes there is. Several, in fact. It depends on your Sitecore version. You should read through the official guide: Configure a content delivery server It describes things you need to consider, depending on your particular setup. It also describes any inline edits you should make to existing config files. Additionally, again depending on your setup, there ...


3

Here's how I solved the problem. First, I created a helper method GetSiteContext that returns a SiteContext object based on a URL. This helper method iterates through all configured sites and tries to match them to the host name of the URL. If no site matches, the context of the website is returned. public static SiteContext GetSiteContext(Uri requestUrl) {...


3

The clue here suggests that the login site is resolving correctly. The error message is forwarding to the pagenotfound using the site context of login. This tells me that the SiteResolver is picking up the correct site. Something else is going on preventing access to the login page. Things to Check: Make sure something funky isn't going on in IIS ...


3

The Experience Editor starts on the home page of your current site. Based on the startItem from the node for the current site. rootPath="/sitecore/content/sites/company" startItem="/Home" If you go into Desktop > Content Editor > click on your new home node. Then Publish tab > Experience Editor. Does the editor work? Your item just isn't editable ...


3

As a first port of call, I would try reinstalling the SharePoint module. From the docs I would check that the "Sharepoint Integration Configuration" template exists: To integrate SharePoint lists with the Sitecore content tree or the Media Library use the SharePoint Integration wizard to create a SharePoint integration definition item based on the ...


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