Forum Discussion
Upload to SitePages library on Classic Team Site with Modern Experience
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 Sit...
Not a problem to ping me with questions. Part of the job, and only slow to reply sometimes as I balance it with other to dos ;). I think you are seeing the move away from classic development patterns and practices. You can allocate server resources to classic team sites from the SPO admin center, but it is something we are moving away from with modern sites in that the SharePoint Framework is the new model we're establishing for modern dev on all modern sites.
And the new pages library is meant to be wired to the New > Page menu that would steer people away from uploading a classic .aspx page. So it's not unexpected what you see, though it does feel inconsistent when you switch between the two.
Hope that helps understand a little more,
Mark
And the new pages library is meant to be wired to the New > Page menu that would steer people away from uploading a classic .aspx page. So it's not unexpected what you see, though it does feel inconsistent when you switch between the two.
Hope that helps understand a little more,
Mark
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?".