New answers tagged

0

Root cause: the content wasn't available in the locale specified by URL: en-US. The docs, https://jss.sitecore.com/docs/getting-started/app-deployment, will create content in en. There will be an en.yml file in the [app]\data\routes folder. To create content in en-US, refer to https://jss.sitecore.com/docs/techniques/content-translation. Copy en.yml as en-...


0

We have been able to have a way around. The way around is: Change the placeholder for any of the renderings. Publish the item. Revert the change in point 1. Publish the item


0

Very likely this is an issue with Robot Detection. In React Native I assume you are unabvle to trigger Visitor Identification. You would either need to find a way to simulate that script in a mobile app, or potentially look at Universal Tracker as an alternative.


0

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

The component factory generation is a convenience within the JSS samples, which enables registration of components by convention, instead of manually maintaining a component factory. The out of the box convention in JSS React is /src/components/ComponentName/index.js, with a default export. As noted in comments, you can change that convention if you like. ...


4

The React JavaScript SDK can work with Sitecore tracking and analytics via the Headless Proxy. In "headless mode," all requests are proxied through the node instance, which is also doing server-side rendering of your application. This means that the Sitecore Analytics cookie is associated with the domain of the node server. If you create a custom ...


0

This issue occurs due to Node not trusting certificates added to Windows root Certificate Authority list. If you're using https with Sitecore locally, it's likely you'll need to whitelist that specific certificate to Node when running jss cli commands. This is done (as you mentioned) using the --acceptCertificate flag. I believe this is supported by the ...


Top 50 recent answers are included