Search Results
Search type | Search syntax |
---|---|
Tags | [tag] |
Exact | "words here" |
Author |
user:1234 user:me (yours) |
Score |
score:3 (3+) score:0 (none) |
Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
Views | views:250 |
Code | code:"if (foo != bar)" |
Sections |
title:apples body:"apples oranges" |
URL | url:"*.example.com" |
Saves | in:saves |
Status |
closed:yes duplicate:no migrated:no wiki:no |
Types |
is:question is:answer |
Exclude |
-[tag] -apples |
For more details on advanced search visit our help page |
For questions about the Sitecore JavaScriptServices module and JSS CLI.
2
votes
Accepted
Using the Layoutservice with a virtualFolder setup
Solved by adding sc_site: config.jssAppName to the RouteHandler.js query string parameters.
Edit RouteHandler.js:
...
function getRouteData(route, language) {
const fetchOptions = {
layoutServic …
2
votes
1
answer
167
views
Using the Layoutservice with a virtualFolder setup
I am using Sitecore 9.3 JSS with a virtualFolder site setup. My JSS site is located at /jss while there is another (MVC) site running at /. … &sc_site=jss also solves it.
Is it possible to configure the item or site name passed to the Layoutservice using JSS? …
0
votes
1
answer
757
views
JSS Layout Service fails an item resolving by path with virtual directory
I am using Sitecore 9.3 JSS with a Create React App front-end with a virtual folder setup. … This is due to Layoutservice HTTP call that does not return any route data for: http://localhost/sitecore/api/layout/render/jss? …
1
vote
1
answer
548
views
JSS Tracking API example fetch errors
I am trying to use the JSS Tracking API, according to https://jss.sitecore.com/docs/fundamentals/services/tracking, with Sitecore XP 9.1. … Following the example code:
import { trackingApi } from '@sitecore-jss/sitecore-jss-tracking';
const trackingApiOptions = {
host: config.sitecoreApiHost,
querystringParams: {
sc_apikey: config.sitecoreApiKey …
1
vote
Accepted
JSS Tracking API example fetch errors
Turns out that the client-side CORS error is a false-positive. The actual problem is that the fetcher is performing a GET iso a POST. My fix for it:
import fetch from 'node-fetch';
async function my …