More Bigger & Better Publishing Woes

Folks,

I swear uploading a site is getting worse, not better. I’ve been trying to get mine uploaded since last night - left it overnight in the end, but it didn’t work. I’m now reduced to doing individual pages one at a time. I’m getting ‘time outs’, ‘can’t connects’ and more. But the most annoying thing is this:

  1. publishing a page and RW declaring there are 39 elements to upload
  2. having that publishing process hang at 38 elements
  3. restarting the process immediately (without changing a thing) and being told there are 453 elements to upload

Can someone explain how that can possibly happen? Where did the other 400 elements suddenly come from?

I’d export and use Filezilla, but the export seems unable to actually export the whole site - so when I did that, half the elements didn’t work. I’m no novice - I used to hand code in the mid-nineties, have set up and run servers, etc. So I do know something that is broken when I see it.

As I write, RW is uploading some .doc files from resources - these have no relationship whatsoever with the page I am uploading. I love RW, but publishing is so broken it takes all the fun out of the rest of it. Can’t upload a project file, I’m afraid - it’s too big.

But please, please, please could you sort this out before you add in any unnecessary bells and whistles next time round?

Thanks,

Gavin

It’s that bad, I’m replying to myself…

I have a video background on my front page. It’s been uploaded about 30 times so far. It’s currently being uploaded again as part of publishing a page which has no connection with the video at all, nor any connection with the front page.

Thanks for your thoughts - and your time. I’m removing the video today, anyway. And yet…

Even if I am using a video, RW shouldn’t have to upload it myriad times when I’m uploading pages on which it is not used. It also shouldn’t vacillate quite so wildly between claiming there are 39 elements to upload on a page and then over 400. If one video file confuses the publishing process so much, is there any point going on?

Steve,

I’ve got way bigger files than a piffling 16mb video on that server - and FTP way bigger files both ways every day. I have a strong connection, and FileZilla copes with large transfers to and from the server every day. If RW can’t transfer a 16mb video (actually it can - it’s done it about 60 times already today whilst attaching it to various pages in my site which don’t actually feature the video) then it’s a pretty pointless piece of web design software.

I design a lot of sites in RW, too, and get paid for them - but the file changing nightmares and the FTP nightmares continue. They eat into my professional time, and my personal time. For a piece of software which costs a bit (and quite a bit more if you actually want to do something with it, it’s unacceptable.

I know it’s not the done thing to criticise - or perhaps it’s the done thing to whistle through the issues, but some days RW really doesn’t perform like a professional piece of software at all.

I do believe I could warehouse all my files, but RW would carry on using up half my day on a process which should take twenty minutes. I appreciate your time - but this not a server issue, not a video issue, not a connection issue - this is an issue of something that doesn’t perform a core function well at all.

Gavin

1 Like

I totally sympathize with Gavin. My experiences with RW publishing are exactly same.

While I agree with Steve’s comments and tips, I must say that the whole publishing engine in RW should be the first and only problem on RMS developers list of problems to fix. What’s the point in introducing new features when one of the most important features is broken and dysfunctional for many years, throughout many versions?

I stopped using RW’s publishing altogether couple of years ago. I just export locally and use Transmit to upload and do all the maintenance of my sites on a server. That process has never failed me – not even once. I can’t put up with all the nonsense of RW’s publishing, no matter how much more inconvenient it is to publish manually. In the end, I am saving time anyway, because my way of publishing is predictable and never fails.

So, please, RMS developers, get your *hit together and fix that damned publishing once and for all. This is your greatest failure and shame since the beginning of Rapid Weaver…

1 Like

Absolutely agree. The FTP should be ditched from RW and perhaps a new feature could be added. Look how fast that Blocs App is developing because the single developer who creates it spends every hour adding new features and not trying to fix the FTP because Blocs App has no FTP. It is a flawed strategy to include FTP in a web development app IMHO.

The user solution is just to Export and ditch the inbuilt FTP and use a free or paid FTP app that will work flawlessly 100% of the time, be quicker with none of that 6 settings nonsense and can also be used to transfer images for image warehousing.

3 Likes

“I just export locally and use Transmit to upload”

Agreed this works well.

Life is give and take.

Dreamweaver has more features and is also more expensive than RW but its FTP works better but not as good as Transmit or Filezilla.

David,

I started with Dreamweaver when it came out, and abandoned it around 2004 when I stopped having to make websites for a living. I have to say I found their FTP extremely reliable, and - working as a team - the check in / out system robust and very useful with a team of twelve working on a large site.

It’s not going to stop me using RW, because the stacks people make are generally top notch and save me a load of time now that web design is not my main job, but simply part of the work I do. I have to say, though, that it seems to me to be a pretty fundamental aspect of a web design package that one be a able to upload the site one has created…

Gavin

Gavin,

Wow Dreamweaver has been out for a very long time - you must be very
experienced.

It has been a while since I used Dreamweaver but I never liked their FTP
client software. Did it basically work ? Yes. but not as well as Transmit
which I use now. Of course maybe DW FTP has improved meanwhile?

Webdesign is not my main job I am a craft business person who likes control
of as much of what we do as possible.

“I have to say, though, that it seems to me to be a pretty fundamental
aspect of a web design package that one be a able to upload the site one
has created…”

You may be correct - but to me it is a feature as opposed to a fundamental
part - at least on the one person level.

If you have a team you probably must have a way to work smoothly together
with DW type software.

I don’t like free software and I am not comfortable with subscription
software so RW is something that I can work with that is almost free. Is
it perfect - no Is support fast - no does it get most of what I need done
yes.

Good luck with your current project.

David