I am following this tutorials: https://github.com/adobe/aem-sample-we-retail-journalHere, all the child pages JSON is stored into __INITIAL_STATE__ id. I want to know why it is done in this way, can someone please explain?Instead what if I navigate on different links and then on click of each links if I call model json of that page via Async fetch and then accordingly set __INITIAL_STATE__ id. What problem in this approach?

472

Re: AEM SPA Routing Issues with hash and query parameter - Adobe Experience Manager

that code is just in React, but how React component is populating myurl? there must be some React component State properties which is read , check that code, also when you say autometically, there must be some code on componentDidMount() which triggers async call. Sorry without your further code I cannot help you.

(val/1000)?string[".0"]}K

Re: AEM SPA Routing Issues with hash and query parameter - Adobe Experience Manager

this issue comes when first time page load or after page is loaded then when you navigate between links? It seems you have custom code to call model.json on every link click, it could be issue with react component state is not updated correctly, so if you post your code then will be better to upderstand

(val/1000)?string[".0"]}K

Re: AEM SPA Routing Issues with hash and query parameter - Adobe Experience Manager

Understood, are you using Adobe SDK or own to call model? if Adobe SDK then can you check what is the value of cq:pagemodel_root_url when you have this error, ideally it should have yourUrl.model.json and then React code reads it from there

(val/1000)?string[".0"]}K

Re: AEM SPA Routing Issues with hash and query parameter - Adobe Experience Manager

So you are using extension less url ? and without looking at your Apache rewriter rule, it is difficult to say whats wrong in the rule

(val/1000)?string[".0"]}K

Re: AEM SPA Routing Issues with hash and query parameter - Adobe Experience Manager

Is this Client or Server Side react?

(val/1000)?string[".0"]}K

SPA Server Side approach - Adobe Experience Manager Forms

I am evaluating how is it possible to implement Server Side Rendering in SPA app with React and AEM as content service. This is the approach I see Next.js suggest to have per-rendered and all most all CMS system suggests: 1. User request a page from react app running on Node server2. Node server requests JSON data from CMS through fetch call3. Then React App reads this JSON and transform HTML into String like renderToString() and sends the response back to the user. The disadvantage of this appr...

(val/1000)?string[".0"]}K

Advantage of Adobe I/O runtime - Adobe I/O Runtime

Hello,I am exploring the option of developing Server Side React App with Adobe I/O runtime as described here : https://docs.adobe.com/content/help/en/experience-manager-64/developing/headless/spas/spa-ssr.htmlI know the advantage of using Serverless technology but I do not understand the real benefit of using SSR app deployed in Adobe I/O. Ad sated in that page the advantage is "More familiar to SPA developers". Is this the only advantage? Can you please help me to understand, any link?

(val/1000)?string[".0"]}K

Likes given to

User

Count

Likes from

User

Count

Guidelines

Cookie preferences