Tag Cloud
« Google Personal vs Netvibes — Flock, Firefox social web clash? »
Adobe Contribute is broken
Thursday, 5 April 2007 — by Wayne Smallman
I say this with some degree of confidence, making up in part for my lack of authority, as I’m neither a software developer, nor an avid user of Adobe Contribute. But that’s besides the point. The fact is, Adobe Contribute just doesn’t work properly because I think it’s broken.
I’ve had dealings with Adobe Contribute before. I bought version 2 ages ago and never got any real joy out it.
To me, it felt like a very typical Macromedia application (who were the developers, until being bought out by arch-rival Adobe) in that its quirkiness was an artifact of poor design and as a result, a colossal pain in the arse.
As an example of my seething contempt of Macromedia as a software developer, here’s an excerpt from an earlier rant of mine:
“Let’s face it, Macromedia software is one of the longest running beta tests in computer history.
I simply hate having to use Macromedia software. I took one look at Freehand and laughed out loud, I gave up on DreamWeaver at version two and threw my hands aloft with Fireworks shortly after … I detest using [Macromedia software] because of the utterly incomprehensible departure from the default keystrokes and user interface methodology, which Macromedia re-invent with each & every new or updated software package.
Complete and utter lack of user interface philosophy is a trade mark of Macromedia,…”
[/rant]
Don’t get me wrong, they’ve had some nice ideas. Problem is, they’ve been singularly incapable of delivering on those nice ideas.
And so it goes that Adobe should pick up the baton and race to make something of a silk purse from the sows ear that is Contribute. But alas, my famed love of Adobe softwares’ brilliance has left me feeling chilled to the bone.
Version four of Adobe Contribute is as detestable as those that came before it.
Let’s not contribute, let’s instead hinder things, OK?
During the mid part of last year, I won a new client, who I’ve since done a decent job of sprucing up their product web pages with a little SEO pixie dust.
Prior to my involvement, they were with some other outfit who vastly over-charged them for a very weak CMS and a website that’s a mess of largely broken and poorly-formatted HTML code.
Also, this previous agency put Adobe Contribute in the hands of the client for reasons I’m still not sure about, but that’s history.
While the website sat with the previous agency until we began the transfer away, Adobe Contribute started acting up. In the end, only one colleague could make changes without error.
I moved the website to a new server and the problems persisted, so I got in contact with Adobe technical support, who quite kindly flushed the server of all of the Adobe Contribute files (of which they were many) so we could start from scratch.
The problems persisted.
Contribute this!
After a frustrating series of slow responses and several issues involving the hosting provider losing the majority of my support tickets, Adobe’s final excuse was that the server isn’t properly configured to allow Adobe Contribute to work to its fullest (permissions required to edit files et cetera) and I get the feeling that they’ve washed their hands of the matter.
Now here’s the funny thing, and it’s a kicker, one which I’ve actually put to Adobe technical support, which I imagine they’re too embarrassed to answer to.
If I can do the self same thing that Adobe Contribute purports to do with Transmit (an excellent FTP client) and BBEdit (a bafflingly large text editor), why can’t Adobe Contribute?
Recommended reading
« Google Personal vs Netvibes — Flock, Firefox social web clash? »





I agree with every word that you said about contributie. I have always done everything by hand, never had much of a problem, until my current client’s website, which has been created and edited for the better part of a decade in contribute. I have been using the program and it seems every day I get some new error message or some other bizarre obstacle…