Posted By: Stacy Deere-Strole
Date: December 31, 2015 at 11:14 pm
Have you ever had a situation where you were so excited about a new toy or application, that you couldn’t wait to start diving in and playing with it, and when you do, you run smack into a big brick wall? That’s exactly what the missing script and content editor web parts issue is in O365 as most don’t know until your knee deep.
When opening the web parts tab in SharePoint on-prem, you typically expect to see the options below (note script and content editor web parts).
However, below is a screenshot of what you see when you open the web parts tab in O365. Something is missing right? You’ve got it the script and content editor web parts!!
After some research and various discussions, it was discovered Microsoft, through various O365 updates in 2015, more and more features were disabled by default. The ones main ones of concern around the script and content editor web parts are listed below.
The default scripting capabilities are:
Now that we know why this has all happened, a better question is how to we resolve it so that we can continue provide amazing service to our clients?
To enable scripting from the SharePoint admin center:
Pretty simple right? Now you can get back to your project with little to no time wasted due to the derailment. Guess again!! You now have to wait up to 24 hours for the change to take effect. In the numerous times I’ve had to enable the feature it has been very close to the 24 hours each time to activate. However, once it is activated, you go back to your site and open the web parts tab, you will now see your script and content editor web parts as you would expect.
For more information on other web parts and areas affected by the disabled scripting please check out the following links. You will also find a PowerShell command that will assist in enabling or disabling at the site collection level in Tim Ferro’s article which is a great read!