If a plugin is installed on a client site that’s using timezone Amsterdam (UTC+2), that is logged and visible in the Site Changes log on my MainWP dashboard (also using timezone Amsterdam), but it’s showing in the log as UTC+4, so it looks like it’s logging the local time and handles it as UTC causing a double timezone correction.
This results in incorrect timestamps and changes made in the future. 
I have a ticket open for this exact issue but we have not made any progress.
I’ve checked some things in the database.
The record in wp_mainwp_wp_logs has the field created with a timestamp. That is the timestamp as local time. So the code that shows it on the dashboard handles it like it’s GMT.
On the child site these changes are logged in the wp_options table in mainwp_child_actions_saved_data and that has the exact same timestamp.
So the client plugin logs it as local and the dashboard thinks it’s GMT.
Thanks @7thcircle and @josklever for reporting this.
The development team will look into and I’ll update you once we have more information.
I’ve sent you pre-release version of MainWP Child plugin via a DM that includes a fix for this.
Please install it on one of the affected child sites, and let us know if that helps resolve your issue.
The pre-release seems to be working well.
Same for me, so this is solved. I understand this fix will be released in the next update.
The fix for this issue was included in the v5.4.0.6 of MainWP Dashboard released on 04-22-2025.
Thanks again for reporting this to us.
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.