Here's the code, converted from a function that returns a boolean into a console app to log out eh values. I know this is what's causing the problem, but I'm not sure of the best way to resolve this. This appears to be because my time range in CST actually spans 2 days in UTC time (1pm until 1am the next day), and i am basingmy times off of the UTC date. Right now there is a bug where this says you are outside of the time range at 6pm CST, which is an hour too early. (I work remotely and when I run the project locally on my machine, it's in Eastern time for example) The support staff are located in Central time, but the servers that our site is hosted on could be in any time zone. ![]() ![]() ![]() My company has support staff that are available from 7am to 7pm CST, and we try to reflect that on our website by showing either a button to initiate a chat, or a message saying that they are not available.
0 Comments
Leave a Reply. |