As mentioned in #247635: Journal roadmap, advanced developers should be able to create a list of applied hacks and patches on a site:
- From all enabled modules, select the involved module(s), enter a description, and optionally a d.o issue #number.
- Journal should provide a list of all patches/hacks.
- If d.o allows, automatically retrieve issue statuses periodically.
- If update(_status) module allows, add a warning to each patched/hacked module on the module update status report page.
Anything else to consider?
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | journal.patch-log.patch | 10.06 KB | smk-ka |
| #2 | journal.patch-log.patch | 9.74 KB | smk-ka |
| #1 | journal.patch-log.patch | 9.77 KB | sun |
| #1 | journal-patches.png | 39.83 KB | sun |
Comments
Comment #1
sunThis is how I imagine the base functionality of this feature.
Attached patch implements the ground-work.
Comment #2
smk-ka commentedRerolled for DRUPAL-5.
Regarding PostgreSQL: not sure, though, why columns, which have already been specified as primary key need to be put in a separate index again. Postgres normally implicitly creates the index for you.
Comment #3
smk-ka commentedUpdated patch containing:
- CSS and theme fixes
- issue number to URL expansion
- display fixes.
Comment #4
sunPorted to 6.x and committed to all branches.
Comment #5
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.