React Script Editor Communications Site

%3CLINGO-SUB%20id%3D%22lingo-sub-812133%22%20slang%3D%22en-US%22%3EReact%20Script%20Editor%20Communications%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-812133%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20deployed%20the%20SpFX%20React%20Script%20Editor%20to%20my%20App%20Catalog.%20In%20a%20Team%20site%2C%20I%20can%20see%20it%20in%20the%20web%20part%20drop%20down%20but%20not%20in%20a%20Communications%20Site.%20Is%20this%20normal%20behavior%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-812133%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExtensibility%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1254671%22%20slang%3D%22es-ES%22%3ERe%3A%20React%20Script%20Editor%20Communications%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1254671%22%20slang%3D%22es-ES%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F362619%22%20target%3D%22_blank%22%3E%40Chris_Mancini%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20the%20same%20problem.%3C%2FP%3E%3CP%3EDid%20you%20found%20any%20solution%3F%3F%3F%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1255205%22%20slang%3D%22en-US%22%3ERe%3A%20React%20Script%20Editor%20Communications%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1255205%22%20slang%3D%22en-US%22%3EI%20don%E2%80%99t%20believe%20I%20actually%20deployed%20it%20but%20I%20got%20it%20working.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1255236%22%20slang%3D%22es-ES%22%3ERe%3A%20React%20Script%20Editor%20Communications%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1255236%22%20slang%3D%22es-ES%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F362619%22%20target%3D%22_blank%22%3E%40Chris_Mancini%3C%2FA%3E%20how%3F%3F%3F%20only%20re-deploying%20the%20component%3F%3F%3F%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1255545%22%20slang%3D%22en-US%22%3ERe%3A%20React%20Script%20Editor%20Communications%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1255545%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F595836%22%20target%3D%22_blank%22%3E%40DaniFC%3C%2FA%3E%26nbsp%3BIf%20you%20have%20uploaded%20it%20to%20your%20App%20Catalag%20make%20sure%20it%20is%20Enabled%20by%20going%20to%20right%20clicking%20the%20item%20and%20choosing%20Properties%20from%20the%20menu.%20Check%20the%20Enabled%20box%20and%20click%20Save.%20It%20should%20then%20be%20available%20to%20add%20to%20your%20sites.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1255602%22%20slang%3D%22es-ES%22%3ERe%3A%20React%20Script%20Editor%20Communications%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1255602%22%20slang%3D%22es-ES%22%3E%3CP%3EYes%2C%20I%20deployed%20the%20solution%2C%20its%20appear%20in%20the%20appcatalog%20and%20it%20is%20enabled.%3C%2FP%3E%3CP%3EThen%20when%20i%20try%20to%20add%20into%20a%20moderpage%20the%20webpart%2C%20in%20some%20sites%20appear%20but%20in%20other(in%20this%20case%20in%20comunication%20sites)%20don't%20appear.%20But%20still%20work%20in%20modern%20pages%20from%20team%20site%20for%20example.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1255613%22%20slang%3D%22en-US%22%3ERe%3A%20React%20Script%20Editor%20Communications%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1255613%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F595836%22%20target%3D%22_blank%22%3E%40DaniFC%3C%2FA%3E%26nbsp%3BDid%20you%20follow%20all%20of%20the%20instructions%20per%20the%20%22Minimal%20Path%20to%20Awesome%22%20section%20on%20this%20page%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FSharePoint%2Fsp-dev-fx-webparts%2Fblob%2Fmaster%2Fsamples%2Freact-script-editor%2FREADME.md%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2FSharePoint%2Fsp-dev-fx-webparts%2Fblob%2Fmaster%2Fsamples%2Freact-script-editor%2FREADME.md%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1340900%22%20slang%3D%22en-US%22%3ERe%3A%20React%20Script%20Editor%20Communications%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1340900%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F595836%22%20target%3D%22_blank%22%3E%40DaniFC%3C%2FA%3E%26nbsp%3BI%20have%20the%20same%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20was%20able%20to%20use%20the%20Modern%20Script%20Editor%20in%20Team%20Sites%20but%20not%20in%20Communication%20Sites.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20CS%20I%20am%20able%20to%20add%20the%20web%20part%20in%20the%20site%20contents%20but%20for%20some%20reason%20it%20does%20not%20show%20when%20I%20try%20to%20add%20it%20on%20a%20page.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDid%20you%20find%20a%20solution%20for%20this%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1340945%22%20slang%3D%22en-US%22%3ERe%3A%20React%20Script%20Editor%20Communications%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1340945%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F638593%22%20target%3D%22_blank%22%3E%40Jose_Clua%3C%2FA%3E%26nbsp%3B%20You%20might%20want%20to%20check%20this%20out.%20I%20seem%20to%20remember%20that%20I%20had%20to%20run%20the%20Powershell%20mentioned%20for%20Modern%20sites%20as%20they%20are%20noscript%20sites%20by%20default.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FSharePoint%2Fsp-dev-fx-webparts%2Fissues%2F1128%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2FSharePoint%2Fsp-dev-fx-webparts%2Fissues%2F1128%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1340956%22%20slang%3D%22es-ES%22%3ERe%3A%20React%20Script%20Editor%20Communications%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1340956%22%20slang%3D%22es-ES%22%3E%3CP%3EHi%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F638593%22%20target%3D%22_blank%22%3E%40Jose_Clua%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYes%20from%20central%20admin%20you%20can%20allow%20scripts%20for%20that%20kind%20of%20sites.%20Works%20for%20me%20%3B)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1346700%22%20slang%3D%22en-US%22%3ERe%3A%20React%20Script%20Editor%20Communications%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1346700%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F362619%22%20target%3D%22_blank%22%3E%40Chris_Mancini%3C%2FA%3E%26nbsp%3B%2C%20it%20did%20the%20trick!%3C%2FP%3E%3CP%3EPreviously%20I%20ran%20the%20powershell%20specifically%20for%20the%20Team%20Sites%2C%20where%20I%20was%20able%20to%20add%20the%20Modern%20Script%20Editor%20Web%20Part.%3C%2FP%3E%3CP%3EBut%20then%20I%20had%20enabled%20client%20scripts%20in%20admin%20center%20and%20I%20thought%20that%20was%20a%20tenant%20wide%20configuration.%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20after%20reading%20your%20post%20I%20decided%20to%20run%20the%20Powershell%20for%20the%20Communication%20Site%20and...%20it%20worked.%3C%2FP%3E%3CP%3ENow%20I%20am%20able%20to%20add%20the%20web%20part%20in%20that%20site%20as%20well.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20so%20much%20for%20your%20help!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1346780%22%20slang%3D%22en-US%22%3ERe%3A%20React%20Script%20Editor%20Communications%20Site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1346780%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F595836%22%20target%3D%22_blank%22%3E%40DaniFC%3C%2FA%3E%26nbsp%3Bfor%20me%20allowing%20client%20scripts%20in%20the%20admin%20center%20was%20not%20enough.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20also%20had%20to%20run%20this%20powershell%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22hljs-pscommand%22%3ESet-SPOsite%3C%2FSPAN%3E%3CSPAN%3E%20%3CSITEURL%3E%3C%2FSITEURL%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22hljs-parameter%22%3E%20-DenyAddAndCustomizePages%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22hljs-number%22%3E0%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22hljs-number%22%3EThanks!%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

I have deployed the SpFX React Script Editor to my App Catalog. In a Team site, I can see it in the web part drop down but not in a Communications Site. Is this normal behavior?

11 Replies

Hi @Chris_Mancini 

I have the same problem.

Did you found any solution???

Thanks

I don’t believe I actually deployed it but I got it working.

@Chris_Mancini how??? only re-deploying the component????

@DaniFC If you have uploaded it to your App Catalag make sure it is Enabled by going to right clicking the item and choosing Properties from the menu. Check the Enabled box and click Save. It should then be available to add to your sites.

Yes, I deployed the solution, its appear in the appcatalog and it is enabled.

Then when i try to add into a moderpage the webpart, in some sites appear but in other(in this case in comunication sites) dont appear. But still work in modern pages from team site for example.

@DaniFC Did you follow all of the instructions per the "Minimal Path to Awesome" section on this page:

 

https://github.com/SharePoint/sp-dev-fx-webparts/blob/master/samples/react-script-editor/README.md

 

@DaniFC I have the same issue.

 

I was able to use the Modern Script Editor in Team Sites but not in Communication Sites.

 

In CS I am able to add the web part in the site contents but for some reason it does not show when I try to add it on a page.

 

Did you find a solution for this?

 

Thanks

@Jose_Clua  You might want to check this out. I seem to remember that I had to run the Powershell mentioned for Modern sites as they are noscript sites by default.

 

https://github.com/SharePoint/sp-dev-fx-webparts/issues/1128

 

Hi@Jose_Clua 

Yes from central admin you can allow scripts for that kind of sites. Works for me ;)

@Chris_Mancini , it did the trick!

Previously I ran the powershell specifically for the Team Sites, where I was able to add the Modern Script Editor Web Part.

But then I had enabled client scripts in admin center and I thought that was a tenant wide configuration. 

So after reading your post I decided to run the Powershell for the Communication Site and... it worked.

Now I am able to add the web part in that site as well.

 

Thank you so much for your help!

@DaniFC for me allowing client scripts in the admin center was not enough.

 

I also had to run this powershell:

 

Set-SPOsite <SiteURL> -DenyAddAndCustomizePages 0

 

Thanks!