This is something @dan, @ben, @tpbradley, and @Aaron should change in RW8–if not in RW8 then certainly in RW9.
Yes. I’ve had a RW publishing problem for weeks. Publishing via RapidWeaver seems the most-consistent whine on the RW-Forum, if I had to guess.
My circumstance:
I changed my hosting company because support times took forever and never helped. When publishing to the new host server, my RW project file had the same name–which was carried over from when it was first published on my previous host’s server.
When I entered the new publishing settings for my new host, then tested, and it tested as good, but then when going to actually publish, it wouldn’t publish and said my settings were bad, that it “Couldn’t sign in to your FTP server”–when it just tested successfully 30 seconds prior.
2.
Here’s what’s going on, and it took those clever lads at ChillidogHosting.com (@barchard et el) to figure it out.
Even after changing settings and successfully testing those settings, RW defaults back to the publishing settings from the previous host.
RW defaults back to the first settings because RW allows the title of the project’s publishing settings to remain the same.
This has to be a simple fix. If RW just tested the connection and confirmed that it’s good, how can the same file then not publish because of incorrect publishing credentials?
Possible solutions:
-
RW8 (and certainly RW 9) should force a change in name/title when updating settings–if the older publishing profile is retained–especially if it has the same name.
-
Or ask if the older settings should be overridden.
-
Or create a new default–to the newer settings–which just-successfully-tested.
-
Or something else to clue a RapidWeaver user in on exactly what’s going on.
The good news, the great news, once the FTP connection to publish is actually made, it’s like a rocket and just great.