I set up an office 365 developer account and I;m trying to add a CEWP to the page. I can't find the CEWP anywhere. I've enabled publishing to see if that was the issue but it didn't help. Not sure what to try next.
This is what I see:
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It only takes a minute to sign up.Sign up to join this community
You need to activate Publishing features for both Site Collection and Site level
I found the answer from this site http://mstechtalk.com/missing-web-part-features-office-365/
Login to Office365 account
Open the SharePoint Admin center
Click Settings in left column
Scroll down to Custom Script section
Click selection Allow users to run custom script on personal sites
Click selection Allow users to run custom script on self-service created sites
Scroll to bottom and click Save button
According to the description of this setting, it may take up to 24 hours to take effect
To make the change effective quickly, it will require using PowerShell to connect to SharePoint online and run one cmdlet. You will need to change each line for your relevant credentials and sharepoint URLs
$adminUPN="firstname.lastname@example.org" $orgName="mstalk" $userCredential = Get-Credential -UserName $adminUPN -Message "Enter password" Connect-SPOService -Url https://$orgName-admin.sharepoint.com -Credential $userCredential Set-SPOsite https://mstalk.sharepoint.com -DenyAddAndCustomizePages 0
Instead of using existing team site, please go ahead and create new team site under new site collection.
That will work for you.
I did this and it works in seconds. https://www.youtube.com/watch?v=eMwBIpnEh1o
Enable the Custom Script feature via SharePoint admin center > https://DOMAIN-admin.sharepoint.com/ > Settings > https://DOMAIN-admin.sharepoint.com/_layouts/15/online/TenantSettings.aspx
Custom Script > Allow users to run custom script on self-service created sites >It takes about 24 hours for the change to take effect.
If the issue persists, follow the steps below to enable publishing feature : A. Go to Site Settings > Site Collection Administration > Site Collection Features >
https://DOMAIN.sharepoint.com/_layouts/15/ManageFeatures.aspx?Scope=Site > SharePoint Publishing Infrastructure > Activate. B. Go to Site Settings > https://DOMAIN.sharepoint.com/_layouts/15/ManageFeatures.aspx Site Actions > Manage site features > SharePoint Server Publishing > Activate.
If you do not want to wait for 24 hours, then use this powershell command :
$adminUPN="USERID@DOMAIN.onmicrosoft.com" $orgName="DOMAIN" $userCredential = Get-Credential -UserName $adminUPN -Message "Enter password" Connect-SPOService -Url https://$orgName-admin.sharepoint.com -Credential $userCredential Set-SPOsite https://DOMAIN.sharepoint.com -DenyAddAndCustomizePages 0
please replace DOMAIN in URL with your domain, before clicking on link.
Here is a more recent solution:
It should now be available in the Add Web Part - Media & Content.
Do you mean this web part? This is a screenshot from my Developer Site Collection.
If the web part is missing in all your site collections/subsites, they may not be provisioned correctly. Try to recreate them if you have such a possibility. If it doesn't help, you may need to contact Microsoft to fix it for you. If it's a trial account, can you set up a new one?
It's weird but for SPO fristly I had to add at least "View only" permissions to web part library or selected web part (depend on your needs ...../_catalogs/wp/Forms/AllItems.aspx) for choosen user/group. Next I had to add "Design" permission for user/group on Site level and finally I had to add at least "Contribute" permissions to Site page. For some reason most important permissions are on Site level - the rest of permissions are only for Site/Page access.
For anyone looking for the solution to this in the future, this was what I found:
You need to enable the "Custom Script" feature from your Site Admin Center. This will take about 24 hours to kick in. The link above has a dropdown titled "Features affected when scripting is disabled" which includes the 'Content Editor' Web Part.