Disabling Paperclip asset timestamp keeps you from committing genocide

Know what’s frustrating? Having a flash app that pulls xml from a controller not function. What’s even more frustrating is finding out it’s because of asset timestamp caching. That’s right, that stupid little ‘?293636′ is a form of caching, and works fine, except when it’s being swallowed by flash via XML. I forgot to write about this a while ago, then ran into it again and it reminded me, some of you may be tools and need help, so here ya go.

1
<%= image_tag @image.source.url(:large, false) %>

See that false, it says to disable the timestamp caching. Simple, right? You bet. So, next time you have flash pulling in XML and pictures aren’t showing up, it’s probably because the image path in your XML is using timestamp caching. Peace, I’m outy 5000.

Related Posts

  1. Paperclip before_process For Your Habitual Pornographic Needs
  2. Paperclip Resized Image Details In to_xml
  3. Inherited_resources fondles swfupload and you didn’t even know it
Programming, RubyOnRails

If you enjoyed this post, please consider to leave a comment or subscribe to the feed and get future articles delivered to your feed reader.

  • Good stuff, mate.
  • theRemix
    good shit, keep em coming
blog comments powered by Disqus