After updated to v1.5.2 via git, I found every entry in Recent tab became something like:
added { {count} } minutes ago by xxx
or
added about { {count} } hours ago by xxx
And I also got the below error when trying to resubmit a signup request:
All Account Requests are subject to review.
{ {count} } errors prohibited this { {model} } from being saved
There were problems with the following fields:
{ {attribute} } { {message} }
{ {attribute} } { {message} }
I've never meet this problem before... This problem happens on both ubuntu and fedora, postgresql and mysql... Is there anything need to pay attention to after updating to v1.5.2? Any help would be appreciated. Thank you!
Are you saying that there are entries under the recent tab that are now reading "added" but should be "edited"? Meaning, if you edit an existing card, it still shows up as "added"? As you can see on our site at wagn.org/recent, there are a lot of entries that look like that.
Re the signup error, if you're seeing an error from "re-submitting" a request, the problem is probably that the email is in the user's table, and therefore it can't be submitted again. Does the same problem occur with a new request? In general, Wagn 1.5.2 does not significantly tamper with the signup process, so I'd be surprised if this were a new error.
I understand that there may be some information about the errors you'd rather not share, but if you could show the actual error messages under "There were problems with the following fields", it might be helpful.
OH!, you mean it's literally saying "
". Ah, I didn't understand that. Let me have another look. could you include that screenshot in +example?--Ethan McCutchen.....Mon Feb 07 08:53:48 -0800 2011
It looks to me like this is not a wagn-specific issue. Did you recently upgrate to ruby 1.9? We've been testing in ruby 1.8.6 and 1.8.7 -- it may not work with ruby 1.9 yet.
The code that calls this in wagn looks like this:
<%= time_ago_in_words card.updated_at %> ago by
... and here is someone reporting a similar problem in a non-wagn issue report:
http://stackoverflow.com/questions/4330403/time-ago-in-words-in-count-days
So, even though the
syntax looks like a wagn inclusion, it's just a coincidence. If this is a ruby 1.9 issue, please let us know; we'd like to get wagn working in 1.9 soon.
-ethan
--Ethan McCutchen.....Mon Feb 07 09:25:52 -0800 2011
This seems to suggest that the problem may be in the i18n gem?
http://stackoverflow.com/questions/4827767/getting-count-with-time-ago-in-words
--Ethan McCutchen.....Mon Feb 07 10:47:32 -0800 2011
Yes, you are absolutely right! After downgrading to i18n v0.4.2, everything returns to normal. Thank you very much!
--evanyw.....Mon Feb 07 13:54:26 -0800 2011
We'll have to add that to our gems version list ;)
--Gerry Gleason.....Mon Feb 07 15:51:46 -0800 2011
You mean What gems do I need and what version should they be?
--John Abbe.....Mon Feb 07 18:35:35 -0800 2011