Probably yes, one of my co-workers (the actual maintainer of the API service) and me have been discussing the possibility to start using integers representing the timestamps in the logs instead of strings formatted for date and time [1].
Currently, when an hook is triggered by WordPress the plugin sends a request to the API service with information of the event, two months ago or so I started sending the a parameter “time” in the request identifying the local time according to the timezone configured for the site, this was to force the API to store this specific time and not the EDT of the server.
Unfortunately this was going to cause some issues with the logs of old plugin installations so we decided to keep storing the strings with the date and time using the EDT time, ignore the “time” request parameter, and try to convert the EDT to local time from the plugin during the parsing of the API response.
I will contact my co-worker again to see if we can run more tests.
[1] https://plugins.trac.wordpress.org/changeset/1165704
Thank you.
Please keep me posted.
Do you plan to add new features in the near future?
The issue reported here should be fixed with changeset 1172856 [1]. Regarding the plan for new features in this plugin, we have not decided yet what tools will be added in the future, internally I have to maintain other projects (like the Sucuri CloudProxy firewall) [2] which are bigger than this plugin so the time that I can spend here is limited, if you want to share your ideas let me know.
[1] https://plugins.trac.wordpress.org/changeset/1172856
[2] https://sucuri.net/website-firewall/
Thank you!
I am content with your fixes. I keep reporting till I am using this plugin.
I am very happy that there is a possibility to contribute by sending these reports.
