We've recently made a change to the ITFlow APP by disabling the automatic timezone configuration feature. Users can still manually select a timezone, but by default, the application will now use the system's timezone settings. This adjustment was prompted by the discovery of discrepancies between PHP and MySQL time settings. Specifically, MySQL was operating on the system's timezone, whereas PHP was using the user-specified timezone. This discrepancy led to issues, such as records not appearing until the set timezone aligned with the system's timezone.
Additionally, this inconsistency caused various other anomalies within the app, contributing to several reported issues on our forums, including problems with adding new clients, payment receipts remaining in the queue, and the quote-to-invoice process.
Our own instances were unaffected by this issue because we synchronized the system timezone with the ITFlow timezone setting.
To address these challenges, we've released an update that disables the ITFlow timezone setting, ensuring the application solely relies on the system's timezone. We recommend users to adjust their system timezone to their local time using the command