distance_of_time_in_words shows {{count}} days instead of showing actual days

I have following code in view

<% if @next_topic %>
Time to show next topic <%= distance_of_time_in_words(Time.now.utc,
@next_topic.time_to_show.utc) %>
<hr />
<% end %>

Output:

Time to show next topic {{count}} days

Are you using internationalisation? If so then it could be an issue there.

Google for
time to show in words rails count
produced some possibilities including
http://stackoverflow.com/questions/4330403/time-ago-in-words-in-count-days

Colin

Colin Law wrote in post #968871:

Time to show next topic {{count}} days

Are you using internationalisation? If so then it could be an issue
there.

Google for
time to show in words rails count
produced some possibilities including
http://stackoverflow.com/questions/4330403/time-ago-in-words-in-count-days

Colin

From way back, I'm still having this problem. With rails 2.3.5 and ruby
1.8.7.

The problem does NOT appear in ruby 1.8.6, only 1.8.7.

It may be fixed in future versions of Rails, but future 2.3.x have OTHER
bugs I don't want, and I don't have time to do the complete upgrade to
3.x yet.

Very annoying! If anyone sees this and has any more info on it, please
do let me know. Otherwise maybe I'll just have to downgrade to 1.8.6
again. I upped to 1.8.7 because I had been reading people berating those
who had stuck at 1.8.6 instead of at least staying current in 1.8.x --
but this is not the only bug or weird thing I've run into with Rails 2.x
and 1.8.7 so far.

Jonathan Rochkind wrote in post #976328:

Colin Law wrote in post #968871:

Time to show next topic {{count}} days

Are you using internationalisation? If so then it could be an issue
there.

Google for
time to show in words rails count
produced some possibilities including
http://stackoverflow.com/questions/4330403/time-ago-in-words-in-count-days

Colin

From way back, I'm still having this problem. With rails 2.3.5 and ruby
1.8.7.

The problem does NOT appear in ruby 1.8.6, only 1.8.7.

I didn't think Rails 2.3 was compatible with Ruby 1.8.6.

It may be fixed in future versions of Rails, but future 2.3.x have OTHER
bugs I don't want,

2.3.10 fixes all bugs and security holes AFAIK -- and there *are*
security holes, so you really should give it a try.

Best,

I found the differences between 2.3.5 and 2.3.10 fairly minor, but my apps are all pretty small. Mostly it had to do with versions of various gems, and in my case the drive toward .10 was encouraged by new features I needed in a gem (vestal_versions), and the newer version of that gem only working under 1.8.7, which in turn drove me to 2.3.8, and then to 2.3.10 when all the foofaw about security raised its ugly head.

Walter