Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

org.apache.sling.scripting.sightly.SightlyException: org.apache.sling.api.SlingException: Cannot get DefaultSlingScript:

Avatar

Level 1

I can see bundle as in active stage on system/console but while hitting the page, getting this error -

 

org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: Compilation errors in org/apache/sling/scripting/sightly/apps/...../head_html.java: Line 47, column 2148 : com.....core.page.PageModel cannot be resolved to a type Line 127, column 6223 : com....core.components.configuration.market....Model cannot be resolved to a type
Cannot serve request to /content/.....dashboard.html in /apps/.....abstractPageRenderer.html

Exception:
org.apache.sling.scripting.sightly.SightlyException: org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: Compilation errors in org/apache/sling/scripting/sightly/apps/...../head_html.java:
Line 47, column 2148 : com......core.page.PageModel cannot be resolved to a type
Line 127, column 6223 : com.......core.components.configuration.market....Model cannot be resolved to a type

3 Replies

Avatar

Community Advisor

This usually happens when there is an error in the sightly script, or the included files present in that script. 

Now, if this was component specific, you would get the page, but the component would not be visible. But, as the whole page is not visible, I suspect something wrong in the template's html file on which this page is created.

 

You can check error logs , I'm pretty sure, you would get to the .html file of the template whose structure component is having this error.

 

Avatar

Level 1

But same thing is working for gradle project when we migrated to maven then getting this issue.

Avatar

Community Advisor

It could be due to an OOTB version conflict or an dependency version conflict which will not show up in the bundle but could be present anyway. I would suggest you go through the error logs once, you would find the responsible piece of code.