Freeway is designed to upload only files that differ from the last upload. This data is collected by Freeway at the very end of the publishing process, and stored in a file called _siteinfo, which lives in the Site Folder of each Freeway project. This is why it is important to allow the uploading process to finish completely (the Upload dialog will go away of its own accord). I am pretty sure this database only tracks the pages. It assumes that if anything at all changed about the page, all of its content (images, plug-in content like Flash or movies, etc.) will also need to be uploaded as well. I believe the tracking is done only at the page level, not the individual asset level – that’s the way it appears to work to me.
As long as your projects each have their own site folder, you should not have any collisions with this process. I can imagine that you might end up with a mess if more than one Freeway document writes into the same folder on your Mac. Try to figure out if that is possible in your case.
Before uploading, Freeway checks the timestamps of the files it created in the Site Folder with those that it finds on the server, and will allow a certain number of seconds’ difference between them before deciding that the file needs to be uploaded.
Another possible reason that this process can fail is if your Mac’s clock drifts off of the global standard by an appreciable amount. A failing motherboard clock battery can cause that to happen, although most Macs are set up to align with the global NTP standard by default (System Preferences / Date and Time / Set date and time automatically … [time.apple.com]). Most servers are time-synched with NTP as well, so if everyone agrees what time it is, everyone can also agree whether a file is “stale” or not.
Before you decide the feature is broken, make a new site from scratch, upload it to a folder on your server, change some content on one page, and upload again. You should see just that one page change.
Finally, Freeway is incredibly cautious about changes which touch multiple pages. Let’s say you have external stylesheets enabled, and you make a chance to a style which affects the font color or size on one page. If you made that change through the Edit Styles dialog (rather than in the Inspector, where your changes would only “touch” that one page) then you will have just “dirtied” all the other pages in the site that use that same global stylesheet. Freeway does this because a style change can also affect page geometry, so instead of just updating the stylesheet itself, it also re-publishes all the pages that link to it, which changes their timestamp and forces them to be uploaded next time. You will know this is going to happen if you see a • bullet appear next to the name of the page in the Site pane. Even though you didn’t touch the content of that page, you did change it through the linked stylesheet. The same holds true (more understandably) for any changes that you make within the Master Page(s) for the site. Any changes there trickle down to all child pages of each Master, and that means another full upload.
Walter
On Jan 11, 2015, at 9:06 AM, DeltaDave email@hidden wrote:
The process always wants to re-upload files that already sit on the server
My first question is - What version of FW as there were some issues with earlier versions that should have been dealt with by now.
2nd - what actions are you using as there are some that do ‘dirty’ each page at Publish time. One of those that I can think of is the Link to Page action
David
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options