Open ditsuke opened 3 years ago
@ditsuke Did you think about logging of task execution? It would be nice to see the log of executions per task via i.e. #__scheduler_log table where each task execution is recorded with start/end datetime and any text log which can be filled by a task code.
@ditsuke Did you think about logging of task execution? It would be nice to see the log of executions per task via i.e. #__scheduler_log table where each task execution is recorded with start/end datetime and any text log which can be filled by a task code.
@Denitz Thanks for bringing this up!
As was initially proposed by @PhilETaylor, tasks currently have an (optional) per task log file that can be enabled from the Task configuration view.
I really like your idea too and think we should consider routing the logs to the database entry for access through the administrator interface. I'll update this after having a discussion with my mentor about this idea.
See #49 for SQL fixes.
See #50 for updating the list of core extensions in the extensions helper so that on update of the core. the manifest cache is updated for the new core extensions.
@ditsuke Would be good to get the CMS PR updated soon by the last changes here so we get better update packages built by drone there.
@ditsuke Would be good to get the CMS PR updated soon by the last changes here so we get better update packages built by drone there.
@richard67 all done, thanks for the heads up. 🙂
Summary of Changes
Testing Instructions
Actual result BEFORE applying this Pull Request
Expected result AFTER applying this Pull Request
Documentation Changes Required