WCMScriptHelper Failed to locate script script.webcomponent.html

[SN-AquilaVasconcelos]

Hey guys,

I'm getting the following message in one of my pages, this page is not loading and I think this could be one of the causes, it was working fine, and them know it is not, there's no extra logs outside of the one down bellow and other related to template policy not found:

*ERROR* [179.60.168.49 [1723662768094] GET /content/project/language-master/en-us/sample-page.html HTTP/1.1] com.adobe.cq.sightly.WCMScriptHelper Failed to locate script script.webcomponent.html.

Did anybody ever faced a similar issue, and could anybody help me understand where this file could come from and how could I trace this better?

Best Regards,

[sherinregi]

Hi @SN-AquilaVasconcelos 

Can you please check for your template resourcetype and see if this is included anywhere . I believe you are not using any OOTB template for creating your page .

Look for any data-sly-include or data-sly-call . Also try to enable debug level on error.log for any additional logs 

[SN-AquilaVasconcelos]

Thanks for the reply @sherinregi.

In did we're not using the out of the box page, there's was an inclusion in the page resource from a file got deleated. 

The debug level was already at debug but I didn't got any additional logs.

I know what the problem is know, thank you very much for your help.

[narendiran_ravi]

You can locate the page component of your template and see if this script HTML is added to your page.html or referred to in other files included in the page.html. 

For example, go to Crxde and locate your page.

/content/project/language-master/en-us/sample-page

check for sling:resourceType property to get the page component path. Ex: /your-project/components/page. You can see the page.html file and all the scripts.

[SN-AquilaVasconcelos]

Thanks, @narendiran_ravi

That was very helpful, thanks for the reply.

[HeenaMadan · Accepted solution]

Hi,

Error  indicates that the system is unable to locate a script  script.webcomponent.html. This likely means that the page you're trying to load is referencing a component or script file that either no longer exists or moved?

Can you verify page template is correctly configured and includes all necessary policies and components, including the one that references script.webcomponent.html or script.webcomponent.html file is located in the correct directory

You can also check file below included in your component like

<sly data-sly-include="script.webcomponent.html"></sly>


[SN-AquilaVasconcelos]

Thank you that was the exact case, there was a custom page.html in another project page component, and in this page.html there was an inclusion like the one you mentioned.

What happened was that our project's template uses that other project from the same client as a resourceType and I wasn't finding it, after you said I searched in the other project and found it.

Thank you, very helpful.