tag:help-archives.hannonhill.com,2010-02-09:/discussions/general/18954-building-an-accurate-xml-sitemapCascade CMS: Discussion 2015-04-17T18:54:44Ztag:help-archives.hannonhill.com,2010-02-09:Comment/348706922014-10-07T18:22:46Z2014-10-07T18:22:46ZBuilding an Accurate XML Sitemap<div><p>I should specify....</p>
<p>We have a Site for our live production pages.</p>
<p>Then we have a Site used for Staging. This is just to accurately
see what the live would look like.</p>
<p>So there are times where we publish to staging for weeks or
months, without publishing to production.</p>
<p>Thanks!</p></div>ces55739tag:help-archives.hannonhill.com,2010-02-09:Comment/348706922014-10-08T11:47:10Z2014-10-08T11:47:10ZBuilding an Accurate XML Sitemap<div><p>Hi,</p>
<p>Will you consider using web services in PHP?</p>
<p>Wing</p></div>Wing Ming Chantag:help-archives.hannonhill.com,2010-02-09:Comment/348706922014-10-08T15:17:25Z2014-10-08T15:17:25ZBuilding an Accurate XML Sitemap<div><p>Sure.</p>
<p>Could you give a brief explanation of how that could look with
Sitemaps?</p></div>ces55739tag:help-archives.hannonhill.com,2010-02-09:Comment/348706922014-10-08T15:55:34Z2014-10-08T15:55:34ZBuilding an Accurate XML Sitemap<div><p>OK, I am not sure if this would fit the bill. But still, here
are some details.</p>
<p>In <a href=
"http://www.upstate.edu/cascade-admin/projects/web-services/managing-orphans/index.php">
Managing Orphans</a>, I talked about how to compare pages and files
between a production server and Cascade. There, if a file exists on
the server but not in Cascade, it can be considered an orphan. In
your case, it is the reverse: a file or a page existing in Cascade
but not on your production server is not a candidate for the
sitemap.</p>
<p>If I understand what you want correctly, then I will suggest
these:</p>
<ol>
<li>Walk through a site on your server, and compare what you can
find there with assets in Cascade.<br></li>
<li>Whenever you see a folder, a page, an image, a PDF file, etc.
on the server, match that to an asset in Cascade to make sure it
exists and is publishable. If both are true, add the info, as an
element, to an XML object.<br></li>
<li>When the traversal is done, you have an XML object containing
something that looks like a sitemap. You can process the XML object
to create the sitemap on your server, or you can push the content
back into an XML block in Cascade.</li>
</ol>
<p>I hope these steps make sense to you.</p>
<p>Wing</p></div>Wing Ming Chantag:help-archives.hannonhill.com,2010-02-09:Comment/348706922014-11-24T13:56:58Z2014-11-24T16:03:12ZBuilding an Accurate XML Sitemap<div><p>Those steps worked for me Wing. I was also getting unwanted
pages in my sitemap before they were ready for publishing.</p></div>rudinesbitt