May 30 2018 02:04 AM
We have been using simple ".aspx" files to show custom pages (things which can't be created with SPO) on select sites in our classic environment. For example, web exports from Visio are hosted in SitePages on one of our classic team site.
I know that ".aspx" files can be uploaded to SharePoint Online, but they won't work unless the site allows to run custom script. By default, custom script is blocked on user-created sites that have Office 365 groups. I understand that O365-Group-connected team sites won't allow ".aspx" files. Now that is an other gripe for another day.
But, I have a classic team site, and when I choose to use the modern experience, then the SitePages library won't show the "Upload" option in the UI at all.
However, using the classic experience, there is that regular old upload available and functional.
Why so?
Why should this be? Perhaps there is a common UI pattern irrespective of whether it is on a classic site or a group-connected modern site. But, this should check and honour the type of site, permissions, and whether custom scripting is enabled; based on which "upload" button should be enabled/disabled.
Jun 02 2018 07:18 AM
Pinging @Mark Kashman for visibility, because I don't know who would be right people to ping on this.
Sorry Mark, that is the price you pay for being a known name --> so that unknown names can flood your inbox with pings ;)
Jun 04 2018 10:06 PM
Jul 06 2020 06:08 AM
@Mark Kashman so this isn't a solution in as much as it is a "sorry ol chap, we turned it off, have you considered not wanting the thing you want?".