-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This does not work in SharePoint 2019 On Premise Environment #835
Comments
did u find the solution? i have the same problem. |
Hello, |
has anyone found the solution for this issue? @scfrederic I have tried your suggestion but unfortunately, it did not work :( |
Did it work for you? |
Hello, the solution described here works for me. |
This is deployed but not available to add on webpage. When I debug I can see this webpart but not there on Modern Toolbox to add the webpart to page. |
I was able to take the zipped 1.4 package and apply it to my 2019 on prem environment without issue. |
@jcschmidt31 could you advise where to find "zipped 1.4 package"? I have the exact issue as @nehasha mentioned. I'm testing this web part on my SP2019 DEV.
Any suggestion or a piece of hint would be much appreciated. Thank you very much. BTW, this DEV environment is a single server. |
@jcshmidt31 Thank you very much. I will try this version and will update the thread. |
@jcschmidt31 Thank you very much. the zip 1.4.1 works for me. |
I follow all the instructions on this for deployment but when I add the webpart, it gives below error. PLease confirm if this is compatible with On Prem version? I am using SharePoint 2019
[SPLoaderError.loadComponentError]:
***Failed to load component "3a328f0a-99c4-4b28-95ab-fe0847f657a3" (ScriptEditorWebPart).
Original error: ***Manifest not found for component id "974a7777-0990-4136-8fa6-95d80114c2e0" and version "1.5.1".
***INNERERROR:
***Manifest not found for component id "974a7777-0990-4136-8fa6-95d80114c2e0" and version "1.5.1".
***CALLSTACK:
Error
at t [as constructor] (http://site/_layouts/15/next/spclient/en-us/sp-pages-assembly.js?uniqueId=2g4QD:356:15766)
at new t (http://site/_layouts/15/next/spclient/en-us/sp-pages-assembly.js?uniqueId=2g4QD:807:22174)
at Function.e.buildErrorWithVerboseLog (http://site/_layouts/15/next/spclient/en-us/sp-pages-assembly.js?uniqueId=2g4QD:807:14408)
at Function.e.buildLoadComponentError (http://site/_layouts/15/next/spclient/en-us/sp-pages-assembly.js?uniqueId=2g4QD:807:10829)
at http://site/_layouts/15/next/spclient/en-us/sp-pages-assembly.js?uniqueId=2g4QD:807:62084
The text was updated successfully, but these errors were encountered: