Today was the end of my humble vacations, and back to work.
As I told some weeks ago, I was looking for some time to try
ReGhost.NET because in our development portal, many many pages were unghosted.
The installation is quite simple, just install in your Sharepoint portal and you´re done. Next, is time to run the application. First is required a SQL Server instance running to select then what "_SITE" database you are going to look for unghosted pages.
After that, you will see a listing with all the unghosted pages, and who you should "blame" for that.
In our case, the portal has the company "branding", so we use an
area template to have the same look & fell across the different areas. Because that, the same page (the default.aspx from the template) was listed many times and, at least for me, at the beginning looks confusing. Sadly, there is no way to know to "which area" correspond the unghosted page. So, if for any reason you want to keep an unghosted page, you're out of luck unless you know who to "blame". An area in the portal was created and unghosted by my boss doing some tests, because that, I knew to which area correspond the unghosted page.
Well, ReGhost.NET works great, there is no doubt about that. Just try it, tell me if you want your experiencies.
Maybe needs improvement:
- UI.
- Know to which area corresponds the unghosted page (I don´t know if that is possible).
- Some better docs.
Kudos to
Matthew Cosier.