nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Timezone for saved contents

Amit_LnT

Hi,
I have a question for the saved content about the timezone in which it is saved. When an user saves any content on TS server, it takes the time where the TS server is located. Our TS server is located in US (EST). And it is accessed across the globe. When any user from UK tries to check the saved/modified time for the content, it shows it in EST. The user wants it to see it in their local timezone. Is there any way, like we can set few parameters on TS server that reads the client timezone and displays the time accordingly on the client browser?

Env: TS 6.5 SP2 on windows server 2003

Thanks,
Amit

Find more posts tagged with

Comments

vpatel

This would be a customization. I have seen some customers use GMT as their "standard" -- I am not sure if that'll work for you. But in any case this would be a customization that you'll have to do. I have never done it and I think it MAY BE (again MAY BE) doable but it'll be a bit tricky.

Adam Stoller

Hi,
I have a question for the saved content about the timezone in which it is saved. When an user saves any content on TS server, it takes the time where the TS server is located. Our TS server is located in US (EST). And it is accessed across the globe. When any user from UK tries to check the saved/modified time for the content, it shows it in EST. The user wants it to see it in their local timezone. Is there any way, like we can set few parameters on TS server that reads the client timezone and displays the time accordingly on the client browser?

Env: TS 6.5 SP2 on windows server 2003

Thanks,
Amit

Check with Support. I know this question has come up before, but I don't recall the resolution (if any). It's possible that this may have been addressed in later versions of the product - it's also possible that this issue may never have been officially filed - if that's the case, you should make a point of doing so when interacting with Support.