tag:help-archives.hannonhill.com,2010-02-09:/discussions/general/153-how-do-you-tell-if-smart-publishing-is-workingCascade CMS: Discussion 2011-06-21T13:14:54Ztag:help-archives.hannonhill.com,2010-02-09:Comment/33555922010-10-14T18:55:17Z2010-10-14T18:55:17ZHow do you tell if Smart Publishing is working?<div><p>The easiest thing to do is monitor the time stamps on the actual web server. The time stamps for files that have been published already (and have not changed in the system) should remain as they are on the web server after a publish that references those files.</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/33555922010-10-14T20:07:44Z2010-10-14T20:07:45ZHow do you tell if Smart Publishing is working?<div><p>I checked the date/time stamps and every file in the published folder (and sub-folders) had been updated. If it makes a difference, both the Cascade and web servers are running Windows. Could it be that Cascade is doing a touch on the file to see if it has changed and, therefore, updating the date/time stamp even though it's not actually transferring the file?</p>
<p>I do have a test server with 6.7.1. I will try it there and see if the behavior is the same as our production server.</p></div>byron.marshtag:help-archives.hannonhill.com,2010-02-09:Comment/33555922010-10-14T21:13:48Z2010-10-14T21:13:48ZHow do you tell if Smart Publishing is working?<div><p>Another way to tell would be to set up some additional logging in your instance:</p>
<ul>
<li>Click <strong>System Menu -> Utilities -> Logging</strong></li>
<li>In the text box, enter the class: <code>com.hannonhill.cascade.model.publish.util.LastModified</code></li>
<li>Change the drop down to DEBUG</li>
<li>Click Submit</li>
</ul>
<p>Then, when you publish, you should see messages like this:<br />
</p>
<pre><code>Entity: <id> with destination: <destId> has not been modified since it's last publish and the remote file timestamp matches the one on record.</code></pre>
<p>If not, there may be an issue.</p>
<p>After testing with this, you will want to go back to the logging interface and remove logging for this class (so it doesn't spam your log files).</p>
<p>Let me know what you find.</p>
<p>Thanks!</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/33555922010-10-15T16:47:18Z2010-10-15T16:47:18ZHow do you tell if Smart Publishing is working?<div><p>It appears that the issue is that we have two different targets on the same server. One that handles standard HTML pages and one that handles the CFML pages. If I use one target or the other manually, it publishes correctly and doesn't republish files. Unfortunately, if you simply publish a folder it publishes the pages correctly based on the link in the template target, but files are published by both targets. That apparently resets the publish record so that the files are always published.</p>
<p>Any ideas of a better way of doing this or other work around?</p>
<p>Thanks,</p></div>byron.marshtag:help-archives.hannonhill.com,2010-02-09:Comment/33555922010-10-15T19:05:08Z2010-10-15T19:05:08ZHow do you tell if Smart Publishing is working?<div><p>I see. To clarify, can you verify whether or not you are publishing to multiple destinations that are using the same Transport?</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/33555922010-10-15T19:15:34Z2010-10-15T19:15:34ZHow do you tell if Smart Publishing is working?<div><p>Yes, both transports use the same destinations: one destination per server, three servers total.</p></div>byron.marshtag:help-archives.hannonhill.com,2010-02-09:Comment/33555922010-10-19T21:19:50Z2010-10-19T21:19:50ZHow do you tell if Smart Publishing is working?<div><p>Is it safe to assume that you are still developing in the Global area? At this time, there isn't really any way to avoid this unless you have migrated to Site objects. Once you are in a Site, Targets don't exist so you won't really have multiple destinations going to the same Transport.</p>
<p>Let me know if this makes sense. It can be a little confusing.<br />
</p></div>Tim