[Pro] Upload individual pages only?

How is this done. The freeway site file that is uploaded shows up at the server as separate .html pages. I would like to be able to take individual page html and upload.

The need for this is due to the reoccurring time out problems of the Freeway uploader as well as a similar problem when using an ftp client.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

I see you are using 5.4.3 - there were some upload issues with some earlier versions. Not sure if it was specifically that version though. Might be time for an upgrade?

The built in FW FTP facility doesn’t have an option to upload individual pages unfortunately. All or nothing I’m afraid.

You can certainly upload individual pages via an FTP app but you would need to use the Synchronise feature of Transmit (or similar) to ensure that you got all the changed Resources that went with it.

But if you are having upload issues with both FW and FTP then maybe there is a problem with your hosting?

David


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Thanks Dave

Tell me where my thinking goes wrong here. When sites are uploaded, no matter the app or ftp client, I have been under the delusion that the files already on the server are checked against those that are being uploaded and that only the changes that have taken place are put into place.

If this procedure was the case there would most likely be no further problems. I have contacted Fetch and my host. I have also tried to upload with 7 to no avail.

I think there has been enough talk on this problem to warrant some tweaking from the Freeway engineers. In an earlier discussion here, someone suggested uploading large pdfs or zips separately, but without some sort of exclusion box to the site upload- ala “do not upload these extensions” - that process is useless.

I can see this is timeout issue, not sure who is cutting it off, Freeway or the host.

Also, I was told by Fetch support that the .freeway file that is uploaded by freeway won’t work by dropping it on the correct url at the server. I was told that only the files inside the “wrapper” need be uploaded. But how does one get to them?


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Here’s how (I believe) Freeway works:

After each successful upload using the built-in upload facility, a database file called _siteinfo is created/updated within the Site Folder on your Mac. This contains the modification date of each asset in the site (all files, all kinds, as published to the remote server). It probably also contains a signature of the remote server, although I’m guessing about this detail.

When you next try to upload the document, this database is compared with the current contents of your Site Folder (again, on your Mac) and the files that are different than last upload are updated. Also, files that are missing from the local Site Folder, but were present in the last _siteinfo, are removed from the remote server.

Here’s how (again, I believe, from long experience and inference) Transmit works:

When you set up your left and right panes to matching directories (local on your Mac and remote on your server) and click the Synchronize button, Transmit does a recursive discovery of both trees, and compares the file modification dates of any files it finds. Any files that are newer on the left than the right are overwritten on the right. Any files that are not present on the right, but are present on the left, are copied over, naturally. There is also a setting in Transmit (labeled in red and warnings pop up every time I use it) to remove files that no longer exist on the remote server. This scares me and I rarely use it. Transmit also caches these results, so the first synchronize is slow. But if you leave the window open and do this again, subsequent synchs are much faster – although prone to errors, because Transmit tolerates a certain amount of “clock slop” between the two sides, and it can take quite a few “saves” to get the Mac side to wake up and notify Transmit that the modification date is newer.

These are fundamentally different approaches to the same problem, and it’s understandable that you might think Freeway was doing the Transmit thing, since that’s how many/most FTP applications work.

Walter

On Jan 31, 2015, at 11:51 AM, Earthcat email@hidden wrote:

When sites are uploaded, no matter the app or ftp client, I have been under the delusion that the files already on the server are checked against those that are being uploaded and that only the changes that have taken place are put into place.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

believe, from long experience and inference) Transmit works:

That is when you use the Synchronise feature in Transmit - not applicable if you are simply dragging/dropping.

As I am not a Fetch user I cant speak with any authority on its use but I would assume that any ‘Synchronise’ feature in Fetch would operate under the same principles as Transmit.

I can see this is timeout issue, not sure who is cutting it off, Freeway or the host.

Or your Broadband provider?

FW pretty much blindly uploads the files - if there is a bottleneck it is likely with your BB supplier or your Host receiving (provided your upload settings are correct).

David


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

That’s a good point. Freeway uses the libcurl library built into Mac OS X’s networking layer. It’s a very fast, very agnostic system which is capable of fully saturating your network connection with outgoing data. If your host reads that onslaught as abuse, they may try to throttle the connection. That’s all a guess on my part, I know the first part is true, but I am speculating about the rest.

Walter

On Jan 31, 2015, at 3:31 PM, DeltaDave email@hidden wrote:

FW pretty much blindly uploads the files - if there is a bottleneck it is likely with your BB supplier or your Host receiving (provided your upload settings are correct).


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

With regards to the _siteinfo file within the site folder - if this file stores information about what files should be in the site folder does it get updated each time I republish the site?
The _siteinfo file has the date modified as 2010 - is that right? Why would it be so old?


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

It gets updated each time you successfully upload – from within Freeway. It does not track publishing, only uploads. It only updates after all of the files in your site have been uploaded, so if there are any interruptions in that process, it will not be touched. But with that much time elapsed, I would imagine that either you have been using a third-party application to do your actual uploading, or you have another Site Folder somewhere else.

Walter

On Feb 13, 2015, at 10:04 AM, Misty Ann email@hidden wrote:

With regards to the _siteinfo file within the site folder - if this file stores information about what files should be in the site folder does it get updated each time I republish the site?
The _siteinfo file has the date modified as 2010 - is that right? Why would it be so old?


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