How do you tell if Smart Publishing is working?

byron.marsh's Avatar


14 Oct, 2010 04:23 PM

I have smart publishing enabled (Cascade 6.4.4), but it seems to publish all of the file assets when I publish a folder. At least, that is what the publish log says. Is there any way to tell if smart publishing is not actually republishing the files?

  1. Support Staff 1 Posted by Tim on 14 Oct, 2010 06:55 PM

    Tim's Avatar

    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.

  2. 2 Posted by byron.marsh on 14 Oct, 2010 08:07 PM

    byron.marsh's Avatar

    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?

    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.

  3. Support Staff 3 Posted by Tim on 14 Oct, 2010 09:13 PM

    Tim's Avatar

    Another way to tell would be to set up some additional logging in your instance:

    • Click System Menu -> Utilities -> Logging
    • In the text box, enter the class: com.hannonhill.cascade.model.publish.util.LastModified
    • Change the drop down to DEBUG
    • Click Submit

    Then, when you publish, you should see messages like this:

    Entity: <id> with destination: <destId> has not been modified since it's last publish and the remote file timestamp matches the one on record.

    If not, there may be an issue.

    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).

    Let me know what you find.


  4. 4 Posted by byron.marsh on 15 Oct, 2010 04:47 PM

    byron.marsh's Avatar

    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.

    Any ideas of a better way of doing this or other work around?


  5. Support Staff 5 Posted by Tim on 15 Oct, 2010 07:05 PM

    Tim's Avatar

    I see. To clarify, can you verify whether or not you are publishing to multiple destinations that are using the same Transport?

  6. 6 Posted by byron.marsh on 15 Oct, 2010 07:15 PM

    byron.marsh's Avatar

    Yes, both transports use the same destinations: one destination per server, three servers total.

  7. Support Staff 7 Posted by Tim on 19 Oct, 2010 09:19 PM

    Tim's Avatar

    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.

    Let me know if this makes sense. It can be a little confusing.

  8. Tim closed this discussion on 21 Jun, 2011 01:14 PM.

Discussions are closed to public comments.
If you need help with Cascade CMS please start a new discussion.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac


26 Aug, 2016 01:19 PM
25 Aug, 2016 03:02 PM
25 Aug, 2016 12:50 PM
24 Aug, 2016 08:43 PM
24 Aug, 2016 07:20 PM
21 Aug, 2016 01:20 PM