Hi Will,
I already posted a little on this with TopPosts where it isn't respecting the Server Time Zone setting of AF. However I thought I'd elaborate a bit more now I've had time to observe general operation after a necessarily hurried go-live.
A bit of background - my site and server are configured for GMT+10 (UTC+10, whatever you prefer). The SQL Server I use is a shared one which is in a timezone of UTC-7.
Setting AF to UTC-7 seems to have the effect of allowing AF to calculate the time difference accurately and to post the correct date based on user time zone. This is terrific but I'm finding some inconsistencies.
If I reply to a topic:
- In Forum view, AF will show the correct date/time (for my local timezone) for last post while I'm logged in
- In Topics view, AF shows a date/time that is in the future for me - ie. it's actually showing UTC+17!!
- In Topic view, AF shows the correct date/time.
If I post a new topic:
- In Forum view, AF shows the correct date/time for last post
- In Topics view, AF shows the correct date/time for the post
- In Topic view, AF shows the correct date/time
When quoting:
- When quoting it appears to be showing UTC-7 time
Top Posts
- As mentioned Top Posts doesn't respect the setting & all dates appear as UTC-7. This is irrespective of whether logged in or not.
When not logged in:
- A new topic shows as UTC-7 in all views
- A reply to a topic shows as UTC-7 in Forum view, UTC+10 in Topics View, and UTC-7 in Topic View.
Search seems to be consistent - ie. when logged in it will show in UTC+10, when not logged in it shows as UTC-7.
Essentially my largest concern is of course where a user is logged in & the date is not displayed in their own timezone (UTC+10 for the most part). I'm most eager to get this consistent in all cases.
A secondary concern for me would be that ideally when a user is not logged in, they would view the site times at the default timezone, ie. use the portal's timezone setting and the AF Server Timezone setting to calculate time as UTC+10 when an anonymous user is on. When logged in the behaviour is then that it shows as their own timezone.
I hope all this makes sense & is useful. If you need anything else, feel free to ask :-)
I tried logging a case about this but it truncated the post :-(
Cheers,
Matt