Yes we do have corressponding react component and have mapto for that
too. I also checked same for wknd-spa-react project(demo that AEM folks
has provided). Same issue is also happening on their custom component
and hello world component.
For our site , we think experience fragment can be good choice for some
work.When I created Experience fragment in react SPA app, I can use some
generic components but can not use my custom component.I can see those
components available to add but when I add it , we do not see anything
in UI(in experience fragment and in page where we use it). We can see
that component in crxde but not in UI.Also checked same for
wknd-spa-react project(demo that AEM folks has provided). Same issue is
also happen...
Able to resolve this issue via following method.Added 3 js scripts and
css links in external site (
clientlib-react.js,container.js,clientlib-base.js,clientlib-react.css)in
index,js where we initialize modelmanager, had to give our rootpath as
an argument.(since our site was within external site, defualt rootpath
was getting taken by browser url)(ModelManager.initialize(//your root
page relative URL//))in order to make sure that model.json doesn't load
again, we manually check in json object to ...
We are also facing similar issue, when we updated page policy in
templated , we can see that component available on page but when we add
it on page , nothing happens
Hi team, Our web lives within another team's website. we are recreating
our site with AEM 6.5 React SPA and wanted to check about approch for
itegration. If it is react only app, we can include script tags along
with matching div name and that should work but since it is AEM app
seems like there is some problem on ModelManager side where it is taking
a root path of current url instead of our app(just a guess). Any ideas
or approch to embed our app in other team's site? Thank you for your
time an...
