Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.These are the plans for the short-term development of this module.
This mostly concerns the refactor and improvements for a 2.x branch, without backwards compatibility with the 1.x branch.
Once this is done, the 1.x branch will be marked as unsupported, and all new development will happen in 2.x.
Must-haves before tagging 2.0-alpha1:
Could haves:
| # | Feature / Task | Issue(s) | Branch |
|---|---|---|---|
| 1 | Refactor plugins architecture to make plugins lighter | #2950246: Make tracking plugins lighter | 2.x |
| 2 | Make it easier to get relationship chain | #2949952: Make it easier to retrieve full relationship chain | 2.x |
| 3 | Add tracking information to status report | #2871390: Create a message in status page reporting the number of relationships tracked | 2.x |
| 4 | Refactor tests | 2.x | |
| 5 | Unify ::add() and ::delete() API methods |
#2951751: Simplify API methods and create new helpers | 2.x |
| 6 | Improve list usage page: - Add new info (revision, language, fields, etc) - Make it more user-friendly (use labels instead of machine names, link to correct languages, etc) |
#2952210: Improve list usage page | 2.x |
Done:
| # | Feature / Task | Issue(s) | Branch |
|---|---|---|---|
| Refactor embed plugin to use base class | #2927857: Support for the Linkit module | 1.x / 2.x | |
| Plugin for LinkIt | #2927857: Support for the Linkit module | 1.x / 2.x | |
| Add "Usage" tab (local task) on all tracked entities | #2932559: Make it easier to access entity usage list of an entity | 1.x / 2.x | |
| Plugin for Link fields | #2949950: Add plugin for tracking trhough Link fields | 1.x / 2.x |
Comments
Comment #2
marcoscanoComment #3
marcoscanoComment #4
marcoscanoComment #5
marcoscanoComment #6
marcoscanoComment #7
bryandenijsComment #8
marcoscanoComment #9
marcoscanoComment #10
marcoscanoComment #11
marcoscanoComment #12
miro_dietikerYeah sounds like a plan.
To reduce pain, i thought we should put bulk regeneration to the roadmap to cycle through all source data (entities?) and extract the usage references after the usage data/schema changes. Then we could simply delete our plugin data and don‘t need to care about stale records or data updates.
Comment #13
marcoscano@miro_dietiker thanks for the feedback!
Yes, I definitely think we should regenerate all the records after changing the schema. Actually the easiest way to do it IMHO is: 1) drop the table, 2) re-create the table with the new schema, 3) trigger the batch for bulk updating all statistics.
The only drawback I can see by doing this, is that by the time this code is released, we will probably have included new plugins at the same time of this upgrade, so maybe after running the DB update people will have way more statistics than they had before (once we plan to enable all tracking methods by default). But again, once our data can always be re-calculated, if people are not happy with all the new data, they can always disable some plugins, then navigate to the bulk-generate page again and trigger it manually.
Comment #14
seanbCommitted to 2.x so far:
#2950743: Missing method parameter in delete method
#2951723: Expose batch update form in UI
#2951720: Remove method column from usage tab
#2950686: Allow more flexibility to enable or disable usage tracking for specific sources/destinations/fields/processors
#2951584: Change terminology for module
#2949951: Add field name information to schema
Updating the IS.
Comment #15
seanbComment #16
marcoscanoAdding some follow-ups to the IS.
Comment #17
marcoscanoUpdated IS with the hook issue done and other UI improvement on the batch update form.
Comment #18
marcoscanoImplemented the triggering of bulk update inside the update hook.
Comment #19
seanbCommitted #2922418: Refactor multilingual tracking to 2.x unstable. Still needs tests, but so do a lot of other new features. We might want to make a new issue to refactor the tests architecture to make it easier to test all the different cases and plugins?
Comment #20
marcoscanoYep, I've created #2952008: Automated tests: Refactor existing and add missing coverage do specifically deal with the tests (existing and missing).
Thanks!
I've also opened #2952007: Usage is not erased when field storage is deleted and added it to the must-haves, once it's a pretty important bug.
Comment #21
seanbCommitted the revision patch and opened followups:
#2952210: Improve list usage page
#2952187: Entity usage for revisions not correctly removed (2.x)
Comment #22
seanbComment #23
marcoscanoComment #24
marcoscanoComment #25
marcoscanoComment #26
marcoscano2.x-1.0-alpha1 is out. Thanks everyone who contributed!