JSON Exporter not working on contentfragment | Community
Skip to main content
S
sandeepk7656774
New Participant
October 26, 2017
Solved

JSON Exporter not working on contentfragment

  • October 26, 2017
  • 1 reply
  • 3118 views

Hi All,

Trying to follow the JSON exporter documentation, but model selector is not working on content fragment.

http://localhost:4502/content/we-retail/us/en/experience/arctic-surfing-in-lofoten.model.json (This is working fine), but if we try to access the URL till content fragment node, that is giving error. This URL

http://localhost:4502/content/we-retail/us/en/experience/arctic-surfing-in-lofoten/jcr:content/root/responsivegrid/content_fragment.model.json  gives following error

Invalid recursion selector value 'model'

Cannot serve request to /content/we-retail/us/en/experience/arctic-surfing-in-lofoten/jcr:content/root/responsivegrid/content_fragment.model.json in org.apache.sling.servlets.get.DefaultGetServlet

Is there any other configuration required?

Thanks,

Sandeep

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by sandeepk7656774

It seems the screenshots in documentation have been given from we.retail sandbox component. The documentation doesn't mentions about the sandbox content fragment component. After installing we.retail sandbox component the model selector is working fine.

Not sure why "General" Content Fragment components don't work with "model" selector. May be the model exporter functionality is not implemented for those yet.

1 reply

S
sandeepk7656774AuthorAccepted solution
New Participant
October 26, 2017

It seems the screenshots in documentation have been given from we.retail sandbox component. The documentation doesn't mentions about the sandbox content fragment component. After installing we.retail sandbox component the model selector is working fine.

Not sure why "General" Content Fragment components don't work with "model" selector. May be the model exporter functionality is not implemented for those yet.

Terms & ConditionsAccessibility statement

Loading footer...