I have a Kentico 10 website that's hosted on Azure. I have configured timezones on the website by following the instructions here in the documentation. I have enabled timezones in (global) settings and applied the desired timezone to both the server and the site as below:
I have even set the user's timezone to the one I want:
However, in the pages app, when I go to a page's publish from and publish to properties (under the Form tab) and hit the 'now' link, the date and time that gets populated there always appears to be a UTC date and time.
This is not ideal and is confusing for website users. I would have expected the date and time that gets populated here upon clicking 'now' to be the time as specified in the time zone settings above.
I am not aware of the intricacies of hosting an Kentico 10 website on Azure and I couldn't find any documentation suggesting anything. I am aware that azure uses UTC times by default but not sure how or why that would be affecting the time zone settings specified here.
Any guidance would be appreciated.
Make sure the Server Time Zone setting reflects your server's time zone. I believe Azure's services run in GMT, so try changing your Server Time Zone setting from (UTC+10.00) Canberra, Melbourne, Sydney to (UTC+00.00) Greenwich Mean Time (UTC).
Related
I noticed That on a Team Site When I save a Date Time field with My now (Central Time Zone) The look at it with REST client, the Z time is with the right offset of 5 Hours.
But on another site that I do not know how it was created, Saving the same value, shows 7 hours offset with a REST client.
From what I know, there is no Time Zone of the Site Collection. Is there a setting somewhere?
I am counting on the consistency that SPO uses the browser's current time zone to determine the UTC offset.
Anyone Knows what is going on?
SharePoint store datatime as UTC, so if your sites' have different time zone, the time would be different.
Save UTC time to SharePoint as demo.
Site Settings->Regional settings
is there a way whereby I can use the time zones provided by ZoneId class provided by java.time?I want the the different time zones to reflect as a drop down in Hybris Management Console.
Did you try to editing java timezone list? Details are here about time zone editor tool: https://stackoverflow.com/a/40401351/2847159
I have submitted a second update of my application and its been two day, my app is in certification.where as, my first submission was passed within 2 hours.
App updates: resolved minor bugs and added a privacy policy criteria for ads. I have added ads in this update as well. I used myapppolicy.com site for making my privacy policy and added a link in the description while submitting.
I just submitted an app update on Saturday, but it wasn't until Monday that it was published - previously it took only a few hours. So, don't worry - it looks like app certification might have slowed down for some reason. If there's a problem with your submission, Microsoft will tell you.
I want to add some OSIsoft RtWebParts to a Sharepoint page. I want these trends to be shown in different timezones for different users. What I'm finding is that they are always shown in EDT.
Ideally, I want a solution for configuring the presented timezone by page or by user.
Michael,
I am the product manager at OSIsoft for RtWebParts.
The time zone is controlled by the SharePoint site, not the web server. One possible workaround it to create a SP site for each time zone that you would like to support. Unfortunately, you would then face the challenge of maintaining the content for multiple sites.
I would also like to make a correction to the workaround that is described above. The workaround should use the RtActiveView web part(which uses ProcessBook .pdi files), not RtGraphic (which uses ProcessBook .svg files).
Thanks,
Tamara
The official response from OSIsoft is: this cannot be done.
RtWebparts objects always use the timezone of the Sharepoint site hosting them. Period.
Other than spinning up a new sharepoint site for each timezone you care about, there is one unappealing workaround:
Create your display in ProcessBook wherein you configure the time offset as desired
Include the ProcessBook PDI file within an RtActiveView web part
Repeat for each timezone
You're still stuck with one timezone (set in the SVG) but now at least you can get multiple timezones without multiple servers.
I've got a hosted VPS hosted by a UK hosting company that for some reason is set to US settings. In fact, until recently, the regional settings were 'English - United States'. I've corrected the regional settings, but my application is still working with the wrong date format. See:
http://www.albaassoc.com/events/listevents.aspx
The default dates are supposed to be the current date to the date + 3 months, but as you can see, the dd and MM fields are swapped. Note: the AJAX calendar extender is manually set to dd/MM/yyyy so that is why the calendar pop thinks we are interested in June/July rather than January!
I know there are various ways to set a page or an application to use a particular locale, but I'd rather go for a global approach.
Is it possible to re-configure IIS to work in a different locale, or if not, can I tweak machine.config so that it is a once-only change?
I've got a ticket open with the host but I'm not going to hold my breath - they aren't going to want to reinstall IIS...
Thanks in advance.
Via the globalization element, you can set the culture and uiculture for a site (via web.config) or the entire machine (via machine.config).
I just got a similar issue (Windows Server 2008, IIS 7). I was able to fix it by editing the web config file, but like you I wanted a global fix.
The solution is in the config panel, regional settings. I don't know for you (what's your OS), but under WS2008, there is an administrative tab under regional settings. It allows you to copy the settings of your logged in user (you) to the administrative accounts (network services in this case). Rebooted and got it right.
The problem is often that the user running either IIS or the application pool your app belongs to is a system account which was created when the server was installed. They therefore inherited whatever the default locale was at the time.
If you can't fix it in regional and language options you can always try editing in the registry directly (with the usual proviso that messing around with the registry can seriously muck up Windows). The regional settings are all under HKEY_USERS\{userid}\Control Panel\International - if you compare what's there for each user with what you have under HKEY_CURRENT_USER\Control Panel\International it should be fairly obvious what to change. I've done this a few times on Windows 2000 servers and it's worked OK.
The other option is just to create a new user on the machine with the correct locale and then set both IIS and the application pool to run with that identity.
Bit of an old thread, but I still look after some legacy Classic ASP sites written by the now defunct Aztec civilisation in praise of their feathered gods.
A server move prevented all the date code from working and sacrificing a chicken was no help, so here is the very easy solution in IIS 7 that has not been mentioned, possibly because no-one else is suffering like me.
Go to IIS Manager.
Select either the root server node to apply to all sites, or select the site node you are having problems with if you want to leave the server default alone.
In IIS section, double click ASP icon.
Set Locale ID to your desired locale (2057 for UK).
This should take effect immediately.
Alternatively you could go buy a DeLorean, go back in time and kill the programmer who decided FormateDateTime(d, vbLongDate) was the best way of generating a date to be used in the database. Or persuade the client to give me a lot of money to replace the whole thing. Either's good.
I had a problem, with having the the date formatted mm/dd/yyyy when I wanted it to be dd/mm/yyyy.
I am using windows server 2003 and IIS 6
The solution was to add the following to any web config file, then reboot your server and it should work just fine.
<globalization requestEncoding="utf-8" responseEncoding="utf-8" culture="en-GB" />