Cloned and renamed the Welcome (default.aspx) page of a Publishing site - OK to delete the original, but renamed, default.aspx?

• Monday, February 23, 2009 6:34 PM

   

   
  

  0
  Hey all,
  
  We recently ran into an issue with the homepage (default.aspx) of our publishing site. Editing the webpage gave the famed, feared error:

  Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxxxxxxxxxx)."

  
  Since we simply could NOT afford to rebuild the entire site (as it seems there's no good way to fix this error without recreating the page or site), we cloned the page, edited the cloned paged in SharePoint designer, and saved the old version as Default_220209.aspx. For some reason, thankfully, we were able to edit and remove the offending web part in the cloned page, even though the original page remains corrupted somewhere.
  
  However, now we have two pages, each called "Home", that appear in our top-level navigation. One is the original homepage (renamed to Default_220209.aspx) and the second, cloned page is called default.aspx.
  
  We want to get rid of the original homepage, but have questions before doing so:
  

  1. It seems that the system still thinks that this is the homepage of the site, even though we've shifted the default Welcome page to default.aspx
  2. What happens if we delete the page? Will the sharepoint publishing site - our Intranet - be very unhappy with us? Since there's no simple way to backup and/or restore pages through Designer, I'm fearful of deleting the page without knowing that we're safe!

  Thanks for your thoughts & suggestions!
  --Dave
  
  
  • Reply
  • Quote