Forum Discussion
Content Editor Migration From Classic To Modern
I have created a content editor webpart in sharepoint 2016 and i migrated to Office 365 E3 license account.After Migration it is showing thw same classic experience in the E3 account,then i converted that page into Modern using Pnp Script after converted it is showing Content Editor Contains Scrip that cannot be Loaded.Is there any other alternate solution for the content editor webpart to get it in the Modern Experience.
2 Replies
Jaswanthi You have below options for modern experience:
- Try using Modern script editor web part
- Re-develop functionality in classic content editor using SharePoint Framework (SPFx)
You can find SPFx web part samples submitted by community members which will help you to get started with the development: sp-dev-fx-webparts
Please click Mark as Best Response & Like if my post helped you to solve your issue. This will help others to find the correct solution easily. It also closes the item. If the post was useful in other ways, please consider giving it Like.
- RobElliottSilver Contributor
Jaswanthi out of the box the Content Editor web part cannot be used in modern SharePoint. This is by design as Microsoft have said they don't want to break sites when they add or change features. You might be able to do something with SPFx but someone clever like ganeshsanap would have to answer that.
Rob
Los Gallardos
Intranet, SharePoint and Power Platform Manager (and classic 1967 Morris Traveller driver)