Hot answers tagged

5

I had the same problem. This was resolved by removing spaces in the field names of my rendering parameters. Sample Input Rendering with configured personalization has a hidden state The rendering has at least one rendering parameter with spaces in field name like "Mobile Width" Output Error Rendering Xslt: /xsl/system/webedit/...


4

This may happen when you have a sibling item (e.g. folder or item without a layout) with the same name or display name. Be aware that Sitecore replaces hyphens to spaces when it tries to find an item in the tree, so if your url is customer-care-support you have a sibling with a name customer care support next to your customer-care-support item, you can ...


4

SitecoreIdentityServer in the URL /identity/login/shell/SitecoreIdentityServer is just an identity provider name which is configured in Sitecore.Owin.Authentication.IdentityServer.config. It should be SitecoreIdentityServer for everyone until we change the config manually for some reasons. So basically you no need to worry about redirection to /identity/...


4

I would recommends you create a new environment and migrate your data/site into that environment. With 9.1 beyond xConnect you have identity server all all the configs that tie it together. This file will set up all the parameters for xconnect install. Just change the name and paths to what you need. Install-Xconnect-tasks-parameters.ps1 #define ...


4

I have migrated sitecore 8 to 9 by using the Option#2 and it worked well for me. Templates, Items, Layout , System, etc you will be able to migrate easily by using the sitecore package. But if you have a huge media library then you can not use sitecore package to transfer this, So, to migrate the media library you need to serialize the whole media library ...


4

You are on Sitecore 9.1 with xDB already in SQL and upgrading to Sitecore 9.2 than you don't require to use MongoDB. Even best practice is to use MS SQL or SQL Azure for xConnect and xDB, we generally try to avoid MongoDB. The xDB Collection database can be hosted on: SQL Server SQL Azure MongoDB (Sitecore 9.0 Update 2 and later) But if you really want to ...


4

Contacted Sitecore Support and its related to corrupted submitQueue folder content. Once cleared the SubmitQueue data, issue went away. Following is the answer from Sitecore Support: From the logs you provided it looks like the content of the Submit Queue folder got corrupted. May I ask you to check if there is any file under \YourDataFolder\...


3

indexAllFields should be inside documentOptions tag <defaultSolrIndexConfiguration> <documentOptions type="Sitecore.ContentSearch.SolrProvider.SolrDocumentBuilderOptions, Sitecore.ContentSearch.SolrProvider"> <indexAllFields>true</indexAllFields> </documentOptions> </defaultSolrIndexConfiguration> You can check solr ...


3

There is no direct upgrade path from 9.0.2 to 9.1 (for now) I suggest to install Sitecore Commerce 9.1 from scratch. Only what you need to do: update Visual Studio Nuget Packages references to Sitecore 9.1 versions fix and make compatibility for you custom code (if it's needed) deploy your customizations I used this way, instead of migration from version ...


3

It needs to create custom routing for calling a controller action method for multisite. Steps are as below: Step 1) Add App_start folder in the Foundation Layer Project. Add a class file in this folder e.g. RegisterWebApiRoutes.cs, use the below code in this class file. public void Process(PipelineArgs args) { RouteTable.Routes.MapRoute(...


3

I think that something is wrong with your custom fieldtype suggestType, . Did you try to change it with something else (for example with text_general)? I am not sure that charFilter solr.PatternReplaceCharFilterFactory works in solr 7. (And as I see it doesn`t replace in tags < and > ). From my practice (solr 6-7) suggester works only with ...


3

Sitecore.Buckets.Manager is present Sitecore.Buckets.dll assembly in Sitecore 9.1. You don't need to do any changes in your code. Just, reference right assembly. Sitecore 9.1 requires .net 4.7.1. See: https://sitecore.myget.org/feed/sc-packages/package/nuget/Sitecore


3

I guess Sitecore.Xdb.config file was corrupted and not the one expected in your Sitecore 9.1 instance, Because In Sitecore 8.1 Sitecore.Xdb.config file contains the below pipeline entry, <pipelines> <initialize> <processor type="Sitecore.Analytics.Pipelines.Initialize.ShowXdbInfo, Sitecore.Analytics" patch:after="processor[@...


3

Yes. MongoDB is legacy support now. Best Practice is to use MS SQL for xConnect and xDB.


3

I have bad news for you -> ProxyManager, SqlServerProxyDataProvider, SqlProxyDataProvider, ProxyDisabler and many other proxy related classes have been deprecated in Sitecore 9. There is no direct replacement for them in Sitecore 9. You can use Cloning functionality which is similar functionality to Proxy items -> https://doc.sitecore.com/users/92/sitecore-...


2

You should let the item be overwritten by the upgrade as The item is for the Sitecore Path Analyzer to work. Normally, you should not be updating the default items of Sitecore with custom data since those are system based items. You are moving from 8 to 9, so there have been lots of changes in terms of the Sitecore Analytics.


2

In the upgraded version of Glass Mapper (5.3.15), I think by default it will perform mapping of all the models from IGlassBase interface during the application start. Looks like it is not performing the mapping on start up. Glass Mapper provides API to perform this mapping on demand that should convert the base glass model to corresponding template model. ...


2

No, It is not required to rebuild Link databases in CD environments. Publishing will keep your link database updated.


2

Are you just trying to register API routes? Its way easier than that. code public class InitializeRoutes { public virtual void Process(PipelineArgs args) { // Registration RouteTable.Routes.MapRoute("create-member", Constants.BaseRoute + Constants.ApiVersion + "/membership", new { ...


2

During the xConnect upgrade, all files under xConnect bin folder might be replaced with the files from the upgrade package. In XConnect’s .\Website\bin folder, some of the dlls might be blocked by default, when executing the above upgrade step. [It happened in my machine and that blocks starting the service again] Just check all the dlls, you may need to ...


2

The problem with Ignore Dependencies, as you point out, is that it is a global setting. While it can be fine to pick and choose from Sitecore assemblies, which ones you want in your project - it is not so easy and obvious when it comes to other third party libraries. Like for example MVC, as you state in your example. If you don't want to move to ...


2

I had similar issue. Try to remove dictionaryImpl param in solrConfig. This is my working configuration to compare: <searchComponent name="suggest" class="solr.SuggestComponent"> <lst name="suggester"> <str name="name">mySuggester</str> <str name="lookupImpl">AnalyzingInfixLookupFactory</str> <...


2

In Sitecore 9 default location of logs was changed. Instead of having data folder on same level as website folder, logs were moved under website folder. You can check App_Data\logs folder inside your website, logs should be there if you have default logs configuration.


2

In this case, the upgrade for the xDB Shards from 9.0.2 to 9.1.1 is very simple: run the upgrade SQL script - a matter of seconds rebuild xDB index - a few minutes tops (let me know if this isn't the case for you) rebuild reporting DB - a few hours tops if you have this patch applied. Does not impact go-live as you can rebuild and it will capture new ...


2

Solution for Sitecore 8.2 Sitecore has released an upgrade process for version 8.2.7 to support MongoDb 3.6.6. Details can be found on the KB article here: https://kb.sitecore.net/articles/244364 The following upgrade process has been tested with MongoDb 3.6.6. Prerequisite: Customers using Sitecore XP versions earlier than 8.2.7 must upgrade ...


1

There is no direct upgrade option. As you can find in the Sitecore Experience Upgrade Guide to upgrade to Sitecore Experience Commerce 9.1 the prerequisites are: Sitecore Experience Platform (XP) 9.0 Update-2 Sitecore Experience Accelerator (SXA) 1.8. Sitecore Experience Commerce (XC) 9.0 Update-3 So your upgrade path is XC9.0.2 -> XC9.0.3 -> XC9.1


1

First of all, make sure below role has below certificates installed. Role - Content Management Certs- Processing Reporting xConnect Collection xConnect Collection Search xDB Reference Data xDB Automation Operations xDB Automation Reporting Role- Content Delivery Certs- Content Management xConnect Collection xDB Reference Data xDB Automation Operations ...


1

Option #1 will not work because Sitecore needs to install new items in you master/core databases. This is what the update package is for. Option #2 will work as long as you are just transferring items and templates. Any goals, rules, etc may have upgrade issues.


1

If you look at the code for the MediaProvider you will notice that only the parameterless constructor is marked as obsolete: /// <summary> /// Initializes a new instance of the <see cref="T:Sitecore.Resources.Media.MediaProvider" /> class. /// </summary> [Obsolete] public MediaProvider() : this(ServiceLocator.ServiceProvider....


1

You will not have such an instance. A single xConnect instance you will have on XP0. on XP1 you have next application roles: Here are described every role what is doing: https://doc.sitecore.com/developers/91/platform-administration-and-architecture/en/application-roles.html


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