Watchers vs. Synchronization

[danny-bonnaducci]

I am new to the software, just purchased it last night, so far so good for the most part.  I did try and setup some sync's but I kept running into an error about a file not existing on my mac.  When this occurs, the sync stops, not sure why..  As I was searching help to see what I missed, I came across the FTP watcher feature.  I have this enabled now, but I am not sure what I should really be using..

I have the following scenario:

2 iWeb websites that I need to publish to a folder on my Mac and then upload upon changes to my server account
1 folder of files that I need to publish to my server account when there are local changes

Suggestions?  Also, will the watchers run if Yummy FTP is not running?  Do I need to drag them to my doc and set them to open at login to ensure that they run after a reboot?  I am fairly new to the Mac, but pretty experiences in terms of web and systems in general.

Any and all help is greatly appreciated-

-DB

[JD]

Unfortunately, iWeb's design causes it to re-create the whole website from scratch each time you publish it. This means that all the files for the web site have newer dates than those on those server, and the result is that you cannot use any synchronization tools since the modification dates are the deciding factor of whether a file should be transferred or not. In the end you end up having to re-upload the whole web site anyway.

The only thing I can advise is to either publish to a .Mac account, which does only upload the changes (as far as I know), or to use a different web site creation tool.

In any case, please use the latest stable build to see if the error message goes away:

http://www.yummysoftware.com/beta/1.7.1b13/YummyFTP.dmg

I am working on a newer build which will be released publicly shortly.

[danny-bonnaducci]

Unfortunately, iWeb's design causes it to re-create the whole website from scratch each time you publish it. This means that all the files for the web site have newer dates than those on those server, and the result is that you cannot use any synchronization tools since the modification dates are the deciding factor of whether a file should be transferred or not. In the end you end up having to re-upload the whole web site anyway.

The only thing I can advise is to either publish to a .Mac account, which does only upload the changes (as far as I know), or to use a different web site creation tool.

In any case, please use the latest stable build to see if the error message goes away:

http://www.yummysoftware.com/beta/1.7.1b13/YummyFTP.dmg

I am working on a newer build which will be released publicly shortly.

Yeah, as I worked through things I started to notice that iWeb removes everything previously existing and creates things each time.  I cannot move to .Mac, so I will need to figure out another option.  I also do not think I can use an FTP watcher for by website directories as from what I read in the help I need to put the watcher script in the same directory as my files.  Well, due to the way that iWeb works, I will loose the script each time I republish...  My question though, I should be able to sync in the sense that I will copy everything over on each attempt right?  I am downloading the updated version you mentioned, hopefully that will get rid of the error message.  Also, I am having issues with the application crashing, again, hopefully the new version solves this issue.  Should I expect anything I setup to be on a sync schedule to be saved after re-starting the application?  This is not happening now...

Thanks-

-DB

[danny-bonnaducci]

By the way, the error is now gone after installing the new version.  Just curious, shouldnt the scheduled sync's I setup remain after I re-start the application?

-DB

[danny-bonnaducci]

By the way, the error is now gone after installing the new version.  Just curious, shouldnt the scheduled sync's I setup remain after I re-start the application?

-DB

Opps, I was wrong, this is still happening...

-DB

[JD]

Glad to hear the new version is error free

To have the scheduled synchs saved requires you to configure them in a Bookmark. If you're using a connection initiated from the New Connection and you don't save is as a Bookmark when prompted then you'll lose the settings for it, including any scheduled synchs.