Hey, I might be late, I’ve just got the idea for a feature request (cause I’m affected).
Publishing a site without being forced to save the project.
You may wonder now, whats the sense behind this? Well, I’m creating a site for a client and wanted to upload a little update for him to see how its going on…an RW says it cannot save the project. ‘Save as’ isn’t working to. And all my changes are lost now (this little annoying bug is only fixable (for some weeks) by restarting the mac). And its not the first time this happened.
But if I was able to upload all the stuff without having to save the project, I could later download the backup rw made on upload and everything is fine
So, if its possible, please do it.
This used to be possible. Sometimes publishing failed or locked up the app, then the changes were lost. The lesser of two evils was to force saving first. As has already been recommended, it is best to duplicate the project and make changes with revision numbers or some other method of tracking for your benefit.
Publishing is getting stuck on one particular project for the same files, regardless of how many connections I try using. I’ve tried 6,3 and 1 connections and get the same result.
Mode is set as Extended Passive (default).
Method is FTP
These files are part of Easy CMS but other projects I have on the same hosting server with Easy CMS publish OK so I’m baffled about what the difference might be.
I can currently get round this problem by using Filezilla to upload the site but its not the way I want to be working, long term.
My publishing issues are still there: RW 7.4 crashes just before generating the checksum. (I had the same problem at exactly the same moment with RW 7.3.3
Publishing on a ‘page’ basis is boring and time consuming!
Still cannot publish. Still says “Cannot connect to ftp” tried all the things suggested in forums. Changing to Extended Passive. Changed server with host, Changed passwords, Published to ftp address instead of site name. Changed speeds etc etc etc. All this happened after upgrading to RW7 never had this problem before.
Go Daddy blaming RW. RW blaming Go Daddy. Basically have a site that won’t publish. After ten years with RW i’m considering jumping ship to Weebly… very sad.
Thanks. Although i did upgrade to 7.3.3 with the same issues. Go Daddy tested going to different server and i still couldn’t connect even though the server was testing fine. So the issue must lie with RW7 somewhere