I've uploaded my development project to my production server, and am
experiencing an odd effect.
All database find methods in which the date is passed as a param are
coming up nil -- it seems that there's an incompatibility in the date/
time format in there somewhere.
E.g. in the view, obtaining @date from the controller to the index
Then in the index view,
<% for date in @dates %>...
<%= link_to ... :date => date... %>
Then back in the show method in the controller:
@date = params[ :date ]
then
LabData.first ... :conditions => ... 'labs.drawn' => date
isn't finding it on the production server, but it was on the
development machine.
I've tried fiddling with the time zone settings on the production
server, no luck.
Has anyone encountered such a problem? Any ideas how to fix it?
I've uploaded my development project to my production server, and am
experiencing an odd effect.
All database find methods in which the date is passed as a param are
coming up nil -- it seems that there's an incompatibility in the date/
time format in there somewhere.
E.g. in the view, obtaining @date from the controller to the index
Then in the index view,
<% for date in @dates %>...
<%= link_to ... :date => date... %>
Have you checked the html of the page in the browser to check that the
links are correct? Compare the html with that seen in the development
environment.
Then back in the show method in the controller:
@date = params[ :date ]
Have you checked the log to see whether the params are the same in the
development and production environment. You may have to change the
logging setup in config/environments/production.rb to see this.
then
LabData.first ... :conditions => ... 'labs.drawn' => date
Again check the log to see what sql is being used.
Have you checked in the db that the records are there?
Hopefully one of the above will give you some clue.
Checking the html, the database entries with phpMyAdmin, and the log
file were where I went first--I should have written that. It's all
there, just like the development environment. The log file was what
pointed me to the database call, and I mocked it up with a script/
console call that mimicked the one in my model. That's when I
discovered that it looks like the date format isn't being passed
correctly in the params hash, which I find really weird. It is, after
all, coming from the database originally.
I think it may be how I pass the dates to the index view, as an array,
is where the formatting may change
Has anyone ever experienced a problem with date formatting like this?
And if so, how did you fix it?
Another question for you gurus is, when I put a raise ---.to_yaml in
the production server code, those only appear in the logs, the
"errors" are prettily concealed on the production views. Any way to
temporarily shut that behavior off while I'm debugging the production
code?
Checking the html, the database entries with phpMyAdmin, and the log
file were where I went first--I should have written that. It's all
there, just like the development environment. The log file was what
pointed me to the database call, and I mocked it up with a script/
console call that mimicked the one in my model. That's when I
discovered that it looks like the date format isn't being passed
correctly in the params hash, which I find really weird. It is, after
all, coming from the database originally.
If the html is correct then it must be getting it out of the db ok so
it is not a problem there. Yet you say the params are getting passed
incorrectly from that html? is that in the log file you see that or
after you get into the action? So what params are you seeing there in
development and what in production?
I think it may be how I pass the dates to the index view, as an array,
is where the formatting may change
You say the html is correct in the index view so it cannot be an issue
passing the dates to the index view, or you would see the wrong dates
there.
Thanks for helping with this. What I see in the development html is ?
date=2010-03-31+18%3A19%3A00+UTC
and what I see in the production html is ?date=Thu+Apr
+01+23%3A02%3A00+-0500+2010
and I'm wondering if somehow it's choking on the date format on the
production server...
Am I right in assuming that is what is contained in the <a href link
in the html? If so then the first thing is that they are in different
timezones. Can you confirm that you are definitely seeing the above
dates with the same version of the code. You said you had been
experimenting with setting the timezone in rails, are you sure you
have updated the production server and restarted it with the same code
as on your development system.
Do you want to see a local time there or UTC?
What have you currently got the timezone set to in environment.rb?
The second thing is that they are formatted differently. How are you
formatting it in your erb code? If you have not got explicit format
it might be worth doing so.
Am I right in assuming that is what is contained in the <a href link
in the html? If so then the first thing is that they are in different
timezones. Can you confirm that you are definitely seeing the above
dates with the same version of the code. You said you had been
...
Do you want to see a local time there or UTC?
Thanks again--the difference was that I had this in the development
config/enviroment.rb
config.time_zone = 'UTC'
But not in the production file. I uncommented it in the production
environment.rb just now, and lo and behold, that part is now working.
Except--I now remember I had in commented out of the production server
as another part of the code which displays the "created at" field for
a record was giving the wrong time. E.g. if I run date in a terminal
I get Fri Apr 2 17:13:05 CDT 2010
(Which is my time)
But for the created at for this record in the database I'm getting
2010-04-02 22:13:33
I don't seem to have that problem on my development machine (MacOS
laptop). The production server is a Redhat Linux machine.
Any idea how to "sync" created at and the system time on the
production server?
> Am I right in assuming that is what is contained in the <a href link
> in the html? If so then the first thing is that they are in different
> timezones. Can you confirm that you are definitely seeing the above
> dates with the same version of the code. You said you had been
...
> Do you want to see a local time there or UTC?
Thanks again--the difference was that I had this in the development
config/enviroment.rb
config.time_zone = 'UTC'
But not in the production file. I uncommented it in the production
environment.rb just now, and lo and behold, that part is now working.
Except--I now remember I had in commented out of the production server
as another part of the code which displays the "created at" field for
a record was giving the wrong time. E.g. if I run date in a terminal
I get Fri Apr 2 17:13:05 CDT 2010
(Which is my time)
But for the created at for this record in the database I'm getting
2010-04-02 22:13:33
I don't seem to have that problem on my development machine (MacOS
laptop). The production server is a Redhat Linux machine.
Any idea how to "sync" created at and the system time on the
production server?
Sorry for my sloppiness--I understand. I guess my main question is why
would it show the correct time in the view on one machine, but not
another?
datetime.strftime("%A %B %d %Y %I:%M:%S %p")
Is different for each machine. I'm busily writing code to detect
where the user is, and adjusting the time shown in the view
accordingly, but I'm still mildly confused by why the two views show
differently.
Fri Apr 2 17:13:05 CDT 2010 == 2010-04-02 22:13:05 (UTC) as CDT is UTC
+ 5 hours
Sorry for my sloppiness--I understand. I guess my main question is why
would it show the correct time in the view on one machine, but not
another?
datetime.strftime("%A %B %d %Y %I:%M:%S %p")
Is different for each machine. I'm busily writing code to detect
where the user is, and adjusting the time shown in the view
accordingly, but I'm still mildly confused by why the two views show
differently.
The above code will assume that you want to display it in local time,
if you change which timezone you tell rails it is in then that will
change the display of local time. Values in the db will always be in
UTC as far as Rails is concerned.
How are you detecting which timezone the user is in? I did not think
it was possible (other than asking him of course).
The above code will assume that you want to display it in local time,
if you change which timezone you tell rails it is in then that will
change the display of local time. Values in the db will always be in
UTC as far as Rails is concerned.
I've learned that from this exercise
How are you detecting which timezone the user is in? I did not think
it was possible (other than asking him of course).
In my new, improved design, I'm storing the time offset for the user
in the user database.
Last weekend I discovered my laptop has a feature that will try to
detect the current time zone, kind of like a cell phone. Perhaps that
will become a ubiquitous feature among operating systems, and then I
could use it for this...
OK, I finally figured this one out, and I'm thinking of it more as a
non-caught bug in my original code
When I pass a date into the params hash in the view, e.g.
link_to ..., ...path( ...:date => date.drawn )
I was getting something like this in my html link on the development
machine:
?date=2010-03-31+18%3A19%3A00+UTC
And something like this on the production machine:
?date=Thu+Apr+01+23%3A02%3A00+-0500+2010
So on the production machine it was making the date human readable
before passing into the params hash--which I would think would be
intended behavior. I solved it by uncasting it in the view:
