I've got a strange situation here. Updated to from Rails 2.1.2 to 2.2.2, and Haml 2.0.3 to 2.0.6, tested at every step of the way and everything works fine on my local machine.
But when I deploy to my remote machine ":ugly" doesn't seem to have any effect (the rendered HTML is all indented). Absolutely everything else works fine though. The ":ugly" thing is the sole thing which is going wrong. It's nearly 5 in the morning here and I'm running out of ideas. Exact same code on both machines (verified SHA-1 hash), and everything frozen into vendor with no external bits floating around on either machine. Reverted to the last known-good version of Haml for me (2.0.3) and same behaviour continues, from which I conclude the cause is on the Rails side. Rolled back to my last deployment (Rails 2.1.2/ Haml 2.0.3) and everything's good. Any ideas on how I could investigate this further? I'm puzzled not because something in Rails broke Haml in the move from 2.1.2 to 2.2.2, but because the breakage only manifests itself on one machine... I don't really know the where flow of execution passes in the rendering layer in order to start poking around in there and find out at which point things are going wrong. Cheers, Wincent --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Haml" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/haml?hl=en -~----------~----~----~----~------~----~------~--~---
