6
To do the same follow below steps:
First you need to create custom personalization rule.
Write you custom code which will inherit RuleContext Class, for check the condition where you will match value one which comes from web API and other you set in your rule.
If both the value will be matched then show or hide your rendering bases on the condition.
For ...
2
Yes, you can use self-signed client certificates in the production environment. They are just for authentication purposes only. The server just uses it to validate that the request is from a genuine client(e.g. a server role).
Also, you can use a single client cert for all server roles for easy maintenance.
2
Chapter 5.3 at page 46 of the Installation Guide for Sitecore XP 9.1 Update-1 describes the steps to install a scaled Sitecore XP platform (XP1) on premises.
As highlighted in the document:
You must first install the sitecore-solr.json and the xconnect-solr.json deployment configurations. Then you must install the rest of the Sitecore server roles ...
1
This isn't an error. It is a warning letting you know that you have an item in Sitecore that you don't have YML for and it has deleted the item from Sitecore. This may be expected behavior if the item is supposed to be deleted. If you aren't expecting the item to be deleted you'll need to look into if you have the latest YML and add it back to your folder ...
1
This issue is a known issue described in this Sitecore Knowledge Base article: https://kb.sitecore.net/articles/091652
You can request a patch for your version of the WFFM module to Sitecore Support. It seems that this fix was never included in future versions of the module. I checked the code of the Sitecore.Form.Submit.CreateItem class in all three ...
1
I did a Sitecore migration using the Sidekick module and experienced the same issue. The reason for this is because of the revision number of the item and/or you have the event disabled.
Smart publish mechanism is to compare items and it makes use of the revision field. If you are having none of the item being updated, this is because the revision number is ...
1
If its a separate application that is not connected to Sitecore in anyway, then you can use a virtual folder or application in IIS to set it up, and then you simply need to add that folder name to the IgnoreUrlPrefixes setting in Sitecore.
<setting name="IgnoreUrlPrefixes" value="/customapi|/sitecore/default.aspx|/trace.axd|/webresource.axd|/sitecore/...
1
The path to EditorPage.aspx is hard-coded in Sitecore.Shell.Applications.ContentEditor.RichText. That is the class resposible for the Rich Text field type. You would need to provide an alternate field type implementation if you wanted to point the field at a different aspx page. I wouldn't recommend it.
For most editor customizations, a better approach is ...
Only top voted, non community-wiki answers of a minimum length are eligible
