Hi Ryan,
I just released a new version of the gem (0.1.2 - may take a little
while to propagate) which attempted to address this issue but which I
found on further testing merely alleviated it.
I'll dig deeper tomorrow and sort it out in the next release.
I guess I need to start doing integration testing with Rails :S
Thanks for pointing this out - much appreciated.
Regards,
Sean
I've hacked a little more at it and now think I've fixed the problem.
I'd be grateful if you could check version 0.1.3 to see if it solves
the issue for you.
Regards,
Sean