JSS Layout Service and Personalization
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
When using the JSS Layout Service with my Angular application, I notice that if I add personalized content to my component, the response (and display) I get back from the Layout service depends on a certain flag. [pageEditing: true, site: name: "portal.local", pageState: "normal", language: "en"]
If this value is false, my personalization seems to work. If true, it shows some generic HTML content (code). I notice I can control this flag by logging out of the Sitecore instance.
Is there a programmatic way to always request the pageEditing=false version from my app? I understand that the experience editor needs to show the content so it needs to handle both. Thank you.
personalization jss
New contributor
add a comment |Â
up vote
1
down vote
favorite
When using the JSS Layout Service with my Angular application, I notice that if I add personalized content to my component, the response (and display) I get back from the Layout service depends on a certain flag. [pageEditing: true, site: name: "portal.local", pageState: "normal", language: "en"]
If this value is false, my personalization seems to work. If true, it shows some generic HTML content (code). I notice I can control this flag by logging out of the Sitecore instance.
Is there a programmatic way to always request the pageEditing=false version from my app? I understand that the experience editor needs to show the content so it needs to handle both. Thank you.
personalization jss
New contributor
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
When using the JSS Layout Service with my Angular application, I notice that if I add personalized content to my component, the response (and display) I get back from the Layout service depends on a certain flag. [pageEditing: true, site: name: "portal.local", pageState: "normal", language: "en"]
If this value is false, my personalization seems to work. If true, it shows some generic HTML content (code). I notice I can control this flag by logging out of the Sitecore instance.
Is there a programmatic way to always request the pageEditing=false version from my app? I understand that the experience editor needs to show the content so it needs to handle both. Thank you.
personalization jss
New contributor
When using the JSS Layout Service with my Angular application, I notice that if I add personalized content to my component, the response (and display) I get back from the Layout service depends on a certain flag. [pageEditing: true, site: name: "portal.local", pageState: "normal", language: "en"]
If this value is false, my personalization seems to work. If true, it shows some generic HTML content (code). I notice I can control this flag by logging out of the Sitecore instance.
Is there a programmatic way to always request the pageEditing=false version from my app? I understand that the experience editor needs to show the content so it needs to handle both. Thank you.
personalization jss
personalization jss
New contributor
New contributor
New contributor
asked 4 hours ago
Toby Nunn
61
61
New contributor
New contributor
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
3
down vote
This behavior is due to being logged into Sitecore and browsing your JSS app in the same browser instance (even if they're separate tabs they share cookies).
I would suggest browsing to your app in an incognito window or separate browser.
Related question: Layout API returning strange code into placeholder
Perfect...company policies do not allow incognito windows but a separate Edge browser did the trick. Thanks for the extremely quick response Adam!
â Toby Nunn
4 hours ago
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
This behavior is due to being logged into Sitecore and browsing your JSS app in the same browser instance (even if they're separate tabs they share cookies).
I would suggest browsing to your app in an incognito window or separate browser.
Related question: Layout API returning strange code into placeholder
Perfect...company policies do not allow incognito windows but a separate Edge browser did the trick. Thanks for the extremely quick response Adam!
â Toby Nunn
4 hours ago
add a comment |Â
up vote
3
down vote
This behavior is due to being logged into Sitecore and browsing your JSS app in the same browser instance (even if they're separate tabs they share cookies).
I would suggest browsing to your app in an incognito window or separate browser.
Related question: Layout API returning strange code into placeholder
Perfect...company policies do not allow incognito windows but a separate Edge browser did the trick. Thanks for the extremely quick response Adam!
â Toby Nunn
4 hours ago
add a comment |Â
up vote
3
down vote
up vote
3
down vote
This behavior is due to being logged into Sitecore and browsing your JSS app in the same browser instance (even if they're separate tabs they share cookies).
I would suggest browsing to your app in an incognito window or separate browser.
Related question: Layout API returning strange code into placeholder
This behavior is due to being logged into Sitecore and browsing your JSS app in the same browser instance (even if they're separate tabs they share cookies).
I would suggest browsing to your app in an incognito window or separate browser.
Related question: Layout API returning strange code into placeholder
edited 3 hours ago
answered 4 hours ago
Adam Weber
76628
76628
Perfect...company policies do not allow incognito windows but a separate Edge browser did the trick. Thanks for the extremely quick response Adam!
â Toby Nunn
4 hours ago
add a comment |Â
Perfect...company policies do not allow incognito windows but a separate Edge browser did the trick. Thanks for the extremely quick response Adam!
â Toby Nunn
4 hours ago
Perfect...company policies do not allow incognito windows but a separate Edge browser did the trick. Thanks for the extremely quick response Adam!
â Toby Nunn
4 hours ago
Perfect...company policies do not allow incognito windows but a separate Edge browser did the trick. Thanks for the extremely quick response Adam!
â Toby Nunn
4 hours ago
add a comment |Â
Toby Nunn is a new contributor. Be nice, and check out our Code of Conduct.
Toby Nunn is a new contributor. Be nice, and check out our Code of Conduct.
Toby Nunn is a new contributor. Be nice, and check out our Code of Conduct.
Toby Nunn is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f14575%2fjss-layout-service-and-personalization%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password