5

The App_Config\Sitecore\Services.GraphQL\Sitecore.Services.GraphQL.Content.config is from the JSS package, no need the change there somethings. It is about your GraphQL endpoint, In your end point your configer what you need. Or you can use a predefined config like the. /sitecore/api/GraphQL/defaults/content/schemaProviders/systemContent In your react app ...


4

Well you can't. The one mechanism that could lock that service down with something that could not just be picked up on the network tab and restrict access to the service to only those people you decide does exist. It's called Authentication, and you're ruling that out. If you think this through; if not authentication, what would you lock down the service ...


3

To fix the issue you need to implement React component for this rendering. The problem is that layout service returns it with space in name, so your componentFactory.js should have following generated output to register such component: import HiddenRendering from '../helpers/HiddenRendering'; components.set('Hidden Rendering', HiddenRendering); To achieve ...


3

Once you get a Component from the Placeholder, you can use the ReadFields<T>() method or other Read methods to get strongly-typed values from it. Keep in mind that this is just JSON deserialization, the ASP.NET model binding attributes won't work here.


2

We have discussed the issue in a private chat and figured out, that the /CustomHome item are placed on the same level with a site start item which makes it impossible to resolved by relative path. In general, Layout Service item resolving process looks similar with an original item resolving: 1) Sitecore sites are resolved based on hostname or sc_site query ...


2

Following some testing locally, the reason you may be getting an Error 404 is when there is no layout set on the item. So, my test cases were as follows: 1st Test Case Create an template without any additional fields. Create an item based on my newly created template. Access the layout service api. Outcome: Error 404 2nd Test Case Create an template ...


2

JSS Layout Service take a database based on the current site which is resolved by a domain name in your URL. Your site, that stays behind jssapp domain, is configured to use the web database. Update your site settings to use the master database and JSS also will use it.


1

Without a sample query reference to tailor my answer, I think what you could leverage here are query fragments to help with multiple templates. For example: fragment itemDetails on Item { id name children{ children(includeTemplateIDs:"{GUID}"{ id name someotherfield } } } You can then leverage the fragment on your ...


1

This can be done in following way. protected override void DoProcess(GetLayoutServiceContextArgs args, AppConfiguration application) { args.ContextData.Add("items", new[] { new { field1 = "field1Value", field2 = "field2Value" }, new { ...


1

So I've updated JSS to 15.0.1 and it fixes the componentName issue. It seems there's a bug in Sitecore 10 and Jss that was fixed in 15.0.1. Strange that it wasn't mentioned anywhere in the release notes, but thanks to Vincent Lui for the inspiration to give it a try. Now to get it into our images...


1

Layout Service can not resolve a virtual directory by default. Sitecore recommends to always populate sc_site parameter in the calls to Layout Service to use this technique. But, if you have more than one JSS app, you have to add additional code to extend the Layout Service call with the query string parameter. But I prefer another way. I extended the ...


1

You appear to have an inconsistent JSS installation. Ensure all Sitecore.JavaScriptServices assemblies are of the same version. If you are referencing JSS assemblies via NuGet, ensure you are referencing the correct version and not deploying the wrong version into your solution.


1

As mentioned, Sitecore's session tracking is cookie-based, so for native/mobile apps you will need to use a HTTP client that is capable of storing cookies. For instance, if using React Native, it has some built-in support for using fetch and cookies, but with some limitations: https://facebook.github.io/react-native/docs/network For other native dev ...


1

The Layout Service executes within the Sitecore MVC rendering engine, and thus retains all Sitecore analytics tracking and functionality. So if you use the Layout Service for routing in your JSS app, each route change will reflect as a page view in your analytics data. To avoid confusing URLs in your analytics data, the Layout Service will set the resolved ...


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