Just lately, we encountered a major challenge the place our ASPX pages, as an alternative of rendering and functioning as anticipated within the browser, began downloading as information.
Upon researching the problem on-line, we found that Microsoft has carried out a change in how SharePoint On-line processes and handles customized ASPX pages. This transformation seems to be the foundation explanation for the issue, because it alters the best way customized pages are handled, resulting in them being downloaded as information fairly than displayed accurately within the browser. This shift has had a direct influence on the performance of our customized options inside SharePoint On-line.
To resolve this challenge we’ve got to do two issues:
Transfer the pages to Website Pages Library -> As soon as the pages had been relocated, the problem was resolved, they usually started functioning as anticipated.
- Throughout our makes an attempt to add pages programmatically utilizing the PnP PowerShell module, we encountered an “Entry Denied” error.
Upon investigation, we found that the problem is attributable to the DenyAddAndCustomizePages setting being enabled on the positioning.
To resolve this, you’ll be able to disable it with the next command:
Set-Sposite -identity $siteURL -DenyAddAndCustomizePages:$false
- Sadly, even after disabling this setting, it routinely re-enables itself inside 24 hours, and there may be at the moment no strategy to completely disable it.
As a workaround, we’ve got included this line of code immediately into our scripting resolution to make sure it will get disabled when obligatory.
I hope this weblog proves useful if you end up dealing with an analogous state of affairs.
Thanks for studying …
Tech Wizard
