You'd have to invoke some SQL commands directly on the database. Dates are stored as integer values, so you could write a SQL command that substracts 8*60*60 seconds to all the integers whose values are in the invalid time range - then install a NTP client on your server ;-)
If you're using SQLite, you can use the sqlite3 tool on the <project>/db/trac.db file. To not forget to back up this file first... You can fix wiki and ticket dates this way. If you also want/need to fix SVN commit dates, you'll have to edit the svn:date revision properties with a SVN client, then run "trac-admin resync" to resync Trac cache from the SVN repository. HTH, Manu On 9/6/07, Richard <[EMAIL PROTECTED]> wrote: > > Hi, > I have a server running trac (.11dev), who's system clock has been 8 > hours ahead of time for the past 3 days. > > I have now corrected the time on the server, but (understandably) all > activity in the timeline for the past 3 days is recorded as 8 hours > ahead of time - is there an easy way to fix these dates/times? > > Thanks > > > > > -- Manu --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
