Highlighted

Content fragment variations not accessible in non-AEM platform

bhuwaneshdhakar

18-10-2018

I created few content fragments and some variations of those. I placed these fragment variations in a API page (exposed as JSON via Sling model) which is being called in non-AEM platform (React-based).

If I access API page having at least one content fragment variation (non-master) in react-app then it gives 500 server error.

If I use only master variations of content fragment then the page is accessible in react-app.

If I access API page directly in browser, then JSON is returned as expected.

The CORS related configuration is properly done in AEM so that it allows react-app to access the API page.

Please let me know what else configuration needs to be done so that I  can access API page having content fragment variation within react-app (non-AEM).

Thanks.

Bhuwanesh

Replies

Highlighted

PuzanovsP

MVP

21-10-2018

Dear Bhuwanesh,

Thank you for your question,

It's hard to tell what could go wrong in your API page without action exception that's causing 500

Can you please attach 500 response you are getting from error.log?

Regards,

Peter