John W. Long wrote: > created_at and updated_at are automagically updated by Rails. So they > are using whatever algorithm Rails uses to calculate the time. Published > at doesn't do anything special. It uses Time.now: > > http://dev.radiantcms.org/radiant/browser/trunk/radiant/app/models/page.rb#L81 > > What would you suggest? > > -- > John Long > http://wiseheartdesign.com
Hi John. Tis a strange one indeed. I assumed that would be the case, yet it seems random that other rails apps on this host don't have the problem, just radiant apps. I have tried creating new radiant apps, using the .zip and also via the gem, running in application or dev mode, creating new databases etc and still all updated_at and created_at timestamps are 10hours behind. In regards to the link you posted I am having trouble getting onto the radiant site at the moment (just times out), but I imagine you are referring to the line where published_at gets populated with Time.now. I had a look at that and as I said its working fine. Only the internal rails operations have the issue… It must be something local... It could be a whole host of things, including the mysql server I guess. I shall continue to investigate and post my findings here. Regards, David -- Posted via http://www.ruby-forum.com/. _______________________________________________ Radiant mailing list [email protected] http://lists.radiantcms.org/mailman/listinfo/radiant
