New answers tagged upgrade
Check if its still pointing old URL. ULS logs would be much handy to solve this. MOSS 2007 has a /default.aspx page which now converted in SharePoint 2010 to /pages/default.aspx or /sitepages/default.aspx. You may need to create a new page as default page and put the content back on it or use SharePoint Designer > All Files to locate the old page. Hope it ...
Just to close this up -- Turns out the problem was indeed related to InfoPath, specifically the lack of InfoPath Services on the 2013 farm. The old 2010 farm was running SP 2010 Enterprise, and the farm the site was migrated to is running SP 2013 Foundation. So... no InfoPath Services available. Oops.
I created a new site with a new content db and migrated the contents and subsites with 3rd party tool (in my case ShareGate). Then I could upgrade the site collection. But my client doesn't want to buy a migration tool to migrate only one single site collection. So I ended up using the export-spweb and import-spweb cmdlets to move the old contents to the ...
Finally, I found an another solution for this critical problem. Cause we modified directly js or CSS or some files of Front End in the server SharePoint, "IIS" will keep the original files as web content cache, even we did Ctrl+F5 or empty the cache in browser, that doesn't work at all. I tested many times in that way. So we need Expire the web content in ...
I did the same thing too, and the result is the disaster... However one solution is adding "?Rev=2" after the link of your js. I hope this could help you.
Top 50 recent answers are included