Share via

sharepoint web parts

Anonymous
2024-07-22T15:07:28+00:00

I have a SharePoint online site collection that I've had since 2018. It originated in 2010 as on-prem site. When I built the site, I used content editor web parts to add custom HTML to the site. When i migrated to online version in 2018, I swapped content editor web parts with HTML l forms web parts. This better allowed me to add custom HTML to my site. I have been able to modify the HTML up until recently. Now when I go to edit the contents, I get the following error message: the custom properties of the form web part are not available in personal view. I tried adding a new web part but could not find the 2 web parts as being available. I contacted Microsoft support who told me to create a public view of the page in order to edit the web part. I was later told that page views were only available on the server version of SharePoint and that M365 Support can assist you if you having an error adding/ removing a web part. For any customization/ editing properties of the web part itself, this is outside our support boundaries.

It now appears as though Microsoft removed the 2 web parts from SharePoint online and broke existing parts on my site. Much googling has shown me that I should experiment with modern pages and that web part containers can now hold custom HTML in what are referred to as snippets. I can add web parts and snippets to the page. How can I hide the snippets title bar? Custom CSS?

Does anyone know how to regain the functionality lost in the HTML form web part? I hate to create new pages and rebuild from scratch to remove 2 links from some custom HTML. the interesting thing to note with snippets is that I can't edit them, only replace.

Microsoft 365 and Office | SharePoint | Other | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-07-22T17:55:18+00:00

    I've never looked at the SP framework (SPFx). I also do not know git. I originally was hired to be a full time developer, but have not had the luxury of sticking to development. I'm now wearing multiple hats since folks left. I will place this on the back burner and if I have some time later this year, I will investigate.

    I kind of knew there would be problems down the road when I learned that audiences compile once a week. I would rather have stuck with the server version, but MSFT gave my non-profit a free subscription to 365 years ago.

    Was this answer helpful?

    0 comments
  2. matt howell 3,511 Reputation points
    2024-07-22T17:17:22+00:00

    Msft has done an abysmal job of helping people move from the more "open" classic environment you were using to the more restrictive modern sites. Any custom code would have to be redone on modern pages but Msft offers no out of the box options, so you have to look into 3rd party solutions. Thankfully there's a helpful group of devs working as the PnP community who have come up with a bunch of solutions you can take advantage of, including a replacement for the content editor web part called the modern script editor. https://github.com/pnp/sp-dev-fx-webparts/blob/main/samples/react-script-editor/README.md

    It's also a good idea to look into the SP framework (SPFx) which is the dev foundation for the "modern" sites. If you're familiar with git based development practices it's pretty easy to grasp-if not, there'll be a significant learning curve.

    Was this answer helpful?

    0 comments