Deploying a publishing page
Today I deployed a publishing page through a Sandbox solution
I created an Elements File in the Module that looked like this:
<Module Name=”Pages” >
<File Path=”Pages\Tasks.aspx” Url=”Pages/Tasks.aspx” >
….
Then I changed the solution into a farm solution and the page (tasks.aspx) would not appear in my pages library.
When I checked with SharePoint designer the page was there but it wasn’t there when I looked through the browser.
Your Solution
Then I changed the above to:
<Module Name=”Pages” List=”101″ Url=”Pages”>
<File Path=”Pages\Tasks.aspx” Url=”Tasks.aspx” Level=”Published” Type=”GhostableInLibrary” >
And now my page appear properly in the pages library.
I’m not sure why this is different for Sandbox and Farm solutions, but it is one to remember for next time.
Discover more from SharePains
Subscribe to get the latest posts sent to your email.
Is your business still running on paper trails, sprawling Excel files, or ageing Access databases? There's a better way — and I can show you exactly what it looks like.
I'm the Technical Director of Vantage 365, a Microsoft solutions consultancy working with clients across the UK, the Netherlands, and worldwide.
For over 30 years I've been turning messy, manual business processes into clean, automated systems that save time, reduce errors, and give teams the visibility they need to make better decisions.
SharePains is not just any blog run by a Microsoft MVP. Have you ever used Try-Catch in Power Automate? The original post about Try-Catch in Power Automate can still be found on this site, https://sharepains.com/2018/02/07/try-catch-finally-in-power-automate-flow/
Or have you ever used the Pieter’s method to avoid variables and speed up your flows? https://sharepains.com/2020/03/11/pieters-method-for-advanced-in-flows/
You can contact me using contact@sharepains.com