Generally, with most applications there is either a sitewide timezone setting (like in Wordpress) or a user-specific timezone setting in the user's profile.
I've got an account that the application sometimes has a logged in user that has a user specified timezone, and other times it's just a general user that is not logged in. I would guess it's "safe" to set the default PHP timezone for the entire Cpanel account to the server's timezone. The only circumstance I can see it causing a problem is if there was some sloppy code that had to write UTC datetime to a database record and just assumed the default timezone was UTC without specifically setting it. Am I overlooking anything?
What about setting the default PHP timezone for ALL accounts to the server timezone and then let that be overridden as necessary on a per account basis (especially if if all the current accounts are associated with companies all in the same timezone?) Or is that a bad practice?
I've got an account that the application sometimes has a logged in user that has a user specified timezone, and other times it's just a general user that is not logged in. I would guess it's "safe" to set the default PHP timezone for the entire Cpanel account to the server's timezone. The only circumstance I can see it causing a problem is if there was some sloppy code that had to write UTC datetime to a database record and just assumed the default timezone was UTC without specifically setting it. Am I overlooking anything?
What about setting the default PHP timezone for ALL accounts to the server timezone and then let that be overridden as necessary on a per account basis (especially if if all the current accounts are associated with companies all in the same timezone?) Or is that a bad practice?