9

As jammykam has said above I'm not aware of any OOTB way of doing this, despite dictionaries being part of Sitecore for quite some time. I spoke to a friend who has implemented this and I thought they wrote something from scratch, but apparently they based it on the blogpost above mentioned by Sitecore Climber: http://jockstothecore.com/editable-dictionary-...


7

I have this issue on Sitecore 8.1 Initial Release. To fix it you need to add on publish:end and publish:end:remote event a new handler. This is the class: public class DictionaryCacheClearer { /// <summary> /// Clears the whole dictionary domain cache. /// </summary> /// <param name="sender">The sender.</param> /// <...


6

I was pretty sure, the use of dictionary items for translation was pretty quick, due to the fact that Sitecore caches the dictionary into a binary file but... It turns out that when you use the domain, the first thing that Sitecore (always) does is look for the domain item with this query: fast://*[@@templateid='{0A2847E6-9885-450B-B61E-F9E6528480EF}' and @...


5

This is a "bug" in the WFFM module, the Sheer UI form does not set a different text for those headings. In a previous version of WFFM which did not include the "Select Existing Form" option I had added this option back in myself so it is possible to override the behaviour and set the "correct" headings. Make a copy of /sitecore/shell/Applications/Modules/...


4

The JSS app name is in the Sitecore config normally below the \App_Config\Include\ in the Sitecore webroot. You can found also found it with this url /sitecore/admin/showconfig.aspx if you are admin, you can search on <apps> and found it below <javaScriptServices patch:source="Sitecore.JavaScriptServices.Apps.config"> See https://jss.sitecore....


4

Your expectation is correct :) Could you please verify that your API Key has the Impersonation User explicitly set? We've updated the docs recently, you might have configured the API key before the update. "...the Impersonation User will need to access the items under /sitecore/system. By default, the ServiceAPI user doesn't have read access to that ...


4

Using the Sitecore Dictionary Unfortunately, custom pipelines and the like are really the only way to go for this on, AFAIK. Sitecore.Globalization.Translate, the method for rendering out a dictionary item's value, does not run through the Field Render pipeline. As such, custom logic must be written to allow editing of the dictionary item in the ...


3

Background The following assumes you have a Sitecore instance with JSS installed and a JSS application you are working on. Grab your favourite de-compilation tool (I use ILSpy) and locate the following DLL in the bin folder of your running Sitecore instance: Sitecore.JavaScriptServices.Globalization.dll Once you have that open in ILSpy you want to have a ...


3

In Sitecore 9.3 when you create a new site you will find a Dictionary node in it. This works like the ootb Sitecore dictionary and includes fallback to more generic dictionaries (you can set which ones). Reading values from this dictionary can be done with Scriban with the sc_translate function. More info here: https://ggullentops.blogspot.com/2019/11/...


3

This took me a little while to track down but it looks like this text for "Insert an existing form" is set in the Resources bundled inside the Sitecore.WFFM.dll so unfortunately it doesn't look like your going to be able to set this yourself from Sitecore. The only solution I could think of here is to use some JQuery/Javascript to set the value of the text ...


3

What Joost say is 100% correct, I recommend to use specific domain to specific website. Is really easy to copy your dictionary domain from /system node to other place. In version 6.6 as far I remember in site definition was introduce a new attribute dictionaryDomain. I recommend to add the dictionary item not under System node and to be specific to the ...


3

You shouldn't place dictionary content items under system. Instead make a dictionary item that inherits from dictionary under your content node and apply appropriate access to this item. If you still want to I'd recommend making a 'Dictionary editor' role and give it read/write/create/delete permissions on system/dictionary. To do this first click '...


2

If you haven't updated the sample project given by JSS then the dictionary service URL will be generated something like below from the jss app. const dictionaryServicePath = `${config.sitecoreApiHost}/sitecore/api/jss/dictionary/${config.jssAppName}/{{lng}}?sc_apikey=${config.sitecoreApiKey}`; But in your case looks like you tried with the direct URL and ...


2

This is an old issue which I could replicate on some solution of Sitecore 8 but it's strage is still on Sitecore 9. On events <event name="publish:end"> and <event name="publish:end:remote"> you need to add a new handler for reseting dictionary cache : <event name="publish:end"> <handler type="Sitecore.Publishing.HtmlCacheClearer, ...


2

Do not store the list of content items (in your case countries) in Dictionary. Rather have a folder called Countries in your DataRepository (Or GlobalContent) folder. Within this folder, you should create your country items (you can create a basic template for with key, value, country flag etc. fields to create these items). In your dropdown field, give the ...


1

Base on the comments above, you'll require to create an event handler which will reset the cache of the dictionary. The event handler will be executed on the events publish:end and publish:end:remote. If I am not mistaken, the items are available on the target database (web) after publish but it reads the dictionary from a file (.dat). So, it is the file ...


1

My problem was in that I created dictionary domain from template that default dictionary used "Node template", but not default dictionary must be created from Dictionary Domain template.


1

Check the Database which you configured in the jss-app config which you deployed in [.\Website\App_Config\Include\JSS-APP-NAME.config] <site patch:before="site[@name='website']" inherits="website" name="portal-poc-app" hostName="portal-poc1.massmutual.com" rootPath="/sitecore/content/portal-poc-...


1

The Sitecore JSS comes with a set of default configurations located in App_Config\Sitecore\JavaScriptServices\Sitecore.JavaScriptServices.Apps.config Since your configuration setting does not include the dictionary path, it will use the following default settings found in Sitecore.JavaScriptServices.Apps.config. dictionaryPath="$sitecorePath/$name ...


1

I strongly agree with Joost regarding not a best practice giving content editors access to anything under /sitecore/system/ node even though you don't have other option here. This is one of the flaws using OOTB Dictionary functionality in Sitecore. There are a lot other flaws - for instance you need to clear dictionary cache after each publish as Sitecore ...


1

What we know (or assume to know) to be true Sitecore runs fine Fails when trying to install an update package Fails because it's trying to write to a drive/path that does not exist Only happens in production. Other environments are fine. Referenced drive/path (E:) is not to be found in any configuration files What we also know Update packages are really ....


1

Another thing you can do to troubleshoot it is search for E:\ using a grep tool such as astrogrep. It might take awhile, but you might find out what exactly is referencing the E:\ since it searches the inside of files.


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