Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
Minimum ACs
- "Batch Op Log" entity that will track the following
- What script ran (string) - the main identifier
- What ran it (drush, UI, hook_updateN, post update, deploy hook, post deploy)
- Who ran it (user entity reference)
- when it started (timestamp)
- when the last operation ocurred (timestamp)
- Whether the operation was completed (boolean)
- Log (long text) - Concat text (appended to by each processOne()} (as though watching in the terminal)
- any caught errors or exceptions (long text)
- Needs a separate "View batch operations log" permission
- Documented in the README
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Issue fork codit_batch_operations-3425026
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
swirtComment #3
swirtComment #4
swirtComment #5
swirtComment #7
swirtComment #8
swirtThis is driving me a bit nuts. I am sure something obvious is staring me in the face, but I don't see it yet.
The route exists. It is revealed with drush route --path=/admin/config/development/batch_operations/log/1
But going to the location after creating the first log entity returns page not found. Same for the collection page.
Comment #9
swirtIt now has the ability to #3425751: Add list View to see all script logs and delete them... but still can't view them
Comment #11
swirtThis has been merged.
Comment #12
swirt