Method Community

Hi 

For some time now, all my devices are showing the local time onthe Field Service calendar in 'Morocco Standard Time'.  I've treid resetting the browser and celaring cache etc but to no avail.  I should be seeing GMT British Summer time or similar being in Scotland...

anyone else getting this? - it seems to be across browers - and devices - Apple safari, Windows using Google chrome and Mozilla firefox.

Hi taurusgardening,

Try checking the time zone on the computer you're using to sign in to Method, that's where will pull the time zone information from.

On Windows, right-click the time on the Windows taskbar in the bottom-right corner of your screen and select Adjust date/time. In the Window that appears click Change time zone....

On Mac, click on the date and time on the OS X toolbar near the top-right corner of the screen and click on Open Date & Time Preferences. Click on the Time Zone tab in the window that appears.

If the time zone is incorrect here, you should change it. To do this, follow these steps:

1. Sign out of Method
2. Close your browser
3. Change your computer's time zone as mentioned above
4. Reopen your browser
5. Sign back into Method

Let me know if this works for you and if not we'll try and figure something else out.

Hope this helps.

- Justin

hi Justin,

thanks for your response, this was the first thing i tried. i've just tried. few things, amongst them changing to a completely different timezone and most work and recognise the new local zone, but if I change it back to UTC for london, Edinburgh, Lisbon, when I reload, it reverts back to morocco standard time.

If you notice a yellow dialog box at the top of the screen when you login, please take a screenshot of it and attach it in a reply to this post. If you notice this box when logging into Method prior to or after you follow the below steps, please reply and attach that screenshot.

Try using the February version of Method. Log out of Method, go to the Method login page, and click on Switch to the February version at the bottom of the page. If you're already on the February version, click Switch to the October version. Login and see if that fixes the issue, let us know either way.

You could also try changing your computer's Region. It should be under Control Panel > Clock, Language, and Region > Region > Change location in Windows or System Preferences > Language & Text > Region in Mac.

If you could also go to whatismyip.com and post back with what country it says you're in, that might be of help, but please do not post your IP address here.

One other thing you could do is try changing your computer's timezone to Morocco Standard Time, just to see what happens. I'd be surprised if this fixes the issue but if something strange happens it will help us to know so we can look into it further.

Let us know how it goes and we'll see about next steps if necessary.

Hope this helps.

- Justin

I think I've found a fix Justin, at least for IE, trying to see if google chrome works in a mo.

It seems Windows 7 and 8 have a tick box section allowing you to 'copy your current settings to: 'Welcome screen and system accounts' and 'New User Accounts',

this is found by clicking to 'Control Panel', 'Region and Language', and after checking 'Location' is correct, clicking on 'Administrative' and clicking the 'Copy Settings' button.  In the new window, select the tick boxes the bottom 'Welcome screen and system accounts' and 'New User Accounts', and click 'OK'

AND, if you reset to the October Version in both Firefox and Chrome, the problem dissappears.

not sure if that would have happened if I hadnt done the above actions too, but the above action sorted out the issue on my Windows Surface outright.

Awesome news! Thanks for posting back with your solution. Let us know if it works in Chrome as well.

- Justin

I can confirm it works for both firefox and chrome Justin.

must be something in the February update.

Hi taurusgardening,

Would you be able to confirm that the error is still occurring with the February version? If so it may be something we can look into further.

Thanks for all your feedback, it really helps us to make sure everything gets looked after.

- Justin

Yep the error is still happening in the February version in Firefox and Chrome. so specific to that version it seems.