forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r535757 - /forrest/branches/forrest_08_branch/site-author/content/xdocs/docs_0_80/upgrading_08.xml
Date Mon, 07 May 2007 06:28:15 GMT
Author: crossley
Date: Sun May  6 23:28:13 2007
New Revision: 535757

Explain that un-necessary project sitemaps should be removed.
Explain the error message that results from not following #modules upgrade step.


Modified: forrest/branches/forrest_08_branch/site-author/content/xdocs/docs_0_80/upgrading_08.xml
--- forrest/branches/forrest_08_branch/site-author/content/xdocs/docs_0_80/upgrading_08.xml
+++ forrest/branches/forrest_08_branch/site-author/content/xdocs/docs_0_80/upgrading_08.xml
Sun May  6 23:28:13 2007
@@ -112,6 +112,11 @@
           <code>{project:</code> and replace with
+      <p>
+        The consequence of not making such corrections is an error message similar to the
+      </p>
+      <source>Could not find component for role:
     <section id="clean">
       <title>Run a clean target after upgrade</title>
@@ -188,6 +193,19 @@
         When it is ready, replace your project's skinconf.xml and files. Any remaining issues would concern other
         aspects of your configuration, such as site.xml and your actual content.
+      </p>
+    </section>
+    <section id="project-sitemap">
+      <title>Remove project sitemap if not necessary</title>
+      <p>
+        It has come to our attention that some people have a 
+        <a href="site:project-sitemap">project sitemap</a>
+        even though they are not using it. Such un-necessary sitemaps should be
+        removed to avoid maintenance issues.
+      </p>
+      <p>
+        If you do use a project sitemap, then pay attention to the upgrade
+        instructions "<a href="#modules">Forrest configuration simplification</a>"

View raw message