Jgarber RedCloth → 4.1.1

Carried over from #80:

Jason

I had everything working fine on my development machine; Rails 2.1.0, gem 1.2, RedCloth 4.0.3. Then I pushed a deployment out to a VPS slice running Ubuntu 8.04 64 bit, with Rails 2.1, gem 1.3.0. I installed the latest RedCloth, 4.1.0 and everything fell to pieces.

My initial problem was the issue with the capitalization in the require statement. In my development machine it had to be RedCloth, which didn't work on the deployment machine. (I've tried updating my gem version but the update process falls over - that's a separate issue).

The earlier gem version 1.2 will choke on "require 'redcloth' " with the echoe error So it has to be "require 'RedCloth' ", the new gem version will fall over with "require 'RedCloth' ", so it has to be "require 'redcloth'". Though version 4.0.3 of RedCloth will accept "require 'RedCloth'" using both gem versions 1.3 and 1.2.

Gem version 1.2 doesn't recognize that echoe is a development gem which is why you must use "require 'RedCloth'". Gem version 1.3 does recognise echoe as a development gem, but barfs on the camel cased require, which is why you must use "require 'redcloth'".

So if you're like me, stuck with a gem version 1.2 on a development machine, but loading up gem version 1.3 on a production machine, you can only use RedCloth 4.0.3.

To try out these different variants you could use Amazon EC2. That's a cheap and easy way to set up new installations, try things out and throw them away when you're finished. If you've not used it before, email me and I'll send you some links to get you started.

Cheers

John Small