As I understand it from @nikf, the issue is with the hosts… there are so many hosts that have different configurations for their set-up that it is nearly impossible for RapidWeaver FTP to work 100% of the time.
Host:
Plan level:
Connection Type (ftp, sftp, ftps):
Using passive, active, other:
Publishing via specific server port:
Using SSL or not:
Using PGP keys or not:
Number of connections:
Root publish folder configuration (/public_html, /public, public, etc):
The more details Realmac Software get regarding this information the better they can make the FTP side of things…
I thought this would be the issue but have reduced number of concurrent uploads to just one and it still happens. Put it back to 4 and it happens roughly the same. Curious about the times when I get the error message but RW appears to have fully published. has it or not?
Sometimes RW works and sometimes it doesn’t but I still don’t feel I can rely on it for FTP uploads. I never have issues with Yummy FTP and though it requires an extra step at least it goes up first time, every time without issues so I am never left wondering. In the past I’ve had times when something on the site appeared to be broken but simply uploading again with Yummy fixed it.
Something I find perplexing about RW uploads is that if I tell it to republish all it might say there are 300 items but if I use Yummy on the same site there are likely to be around 330 from the same exported site. There are many reasons to like RW and it’s my clear choice for web design but FTP has always felt like a weak point in RW6.
Might be - but never used to get this issue prior to recent updates and my broadband is faster than it was then. So many others getting the problem indicates not
Hosting Company
Plan
Server type (IIS, Linux)
PHP version
Connection Type (FTP, SFTP, etc)
OSX Version
RW Version
You can even send them login credentials for them to test with to see if it is indeed a RapidWeaver problem or not.
The issue is every host has the ability to configure their servers the way they wish, it is impossible for RapidWeaver to ‘guess’ at the proper communications methods that every host configures.
Just look at the recent discussion about DreamHost… man oh man… the person even contacted the Hosting company and was given incorrect information by the support department… go figure…
Anyway, there are a number of variables at the Hosts side which are not communicated back to RapidWeaver for whatever reason (RapidWeavers fault or Hosts fault). The best solution is to report the issues to the proper channel with the required details.
I see this thread is still going strong after 6 months! I abandoned the RW Publish and now use an FTP program to avoid using the RW Publish system. I have tried a few FTP programs and they all work considerably faster than the RW file upload, they have never once failed to upload, and I have never had to make any adjustment to the concurrent uploads. A good FTP such as Forklift, Transmit or Yummy works like a charm. Even the super cheap YummyFTPAlias works brilliantly.
I do hope that RW7 will have a completely new and robust publishing system.
I too have issues publishing websites and/or updates from within RapidWeaver, version 6.3.8. Actually, this has been a problem for some time now, long before this particular version.
I just decided “fuck it” and exported to a local folder and then uploaded to my web server (without any issue) using FileZilla.
Not sure what is going on over at realmacsoftware but if this continues I’m opting out. Drupal and sadly, WordPress are presenting themselves as deeper, more reliable, cost friendly and increasingly more user friendly platforms.
If it wasn’t for the robust developer community providing themes, stacks and plugins, RapidWeaver wouldn’t exist. So how about fixing the publishing problem?
Understand this, but we didn’t used to get these publishing errors anywhere near as routinely. Are we to assume that RW has come up with a super fast and smart publishing system that would be great if all hosts were on the same wavelength? Because if so, I would suggest that the variation amongst hosts was known some time back and this publishing project should have shelved before it was started.
It works less than 50% of the time for me no matter what the settings I use. And sometimes it says publishing has failed but the project shows everything as ‘published’ - even more frustrating because you don’t know either way when this happens!
