Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.At the moment, all the reports are generated by helper functions => theme functions.
It would definitely be a step in the right direction to implement views support and ship with some defaults.
I've never done this myself, I'm up for the challenge but don't have a whole lot of time for the next week or so (any takers?). Also, if anyone knows any good example modules to show the hooks that are needed for this, that would be awesome as well.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | licensing.module.patch | 831 bytes | mradcliffe |
| #3 | licensing-views.tar_.gz | 1.3 KB | mradcliffe |
Comments
Comment #1
mradcliffeI can tackle this pretty easy.
Comment #2
nicksanta commentedThat would be sweet @mradcliffe.
Comment #3
mradcliffeI have basic views support for the current schema working, but it will probably need a custom relationship handler depending on how #643492: Abstract uid in the schema turns out.
I can create a cvs patch, but I'm not sure where to put the views and handler directories. I have it setup as views/ and views/handlers/ respectively, but cvs diff -upN is not grabbing the diff because the views and views/handlers directories do not exist. So the patch only has the change to licensing.module.
The other attachment contains the new files.
ninja edit: there is a new base table for views, license key, and a relationship to the uid field. Again that should be completely different when schema is different. But for now it works for users.
ninja edit 2: this is fairly complete until schema changes.
Comment #4
nicksanta commentedAwesome job mradcliffe! That's been committed, I'll create a new alpha release now too.
I'll mark this as 'fixed', and if schema changes affect the views integration we'll just reopen it.
Comment #5
nicksanta commentedActually, on second thoughts it might be good to keep this open until all the reports are views.
Until then, I won't add views as a dependency.
Comment #6
nicksanta commentedThe next major step has been completed - there is now an 'operations' field. The last job is to create all the various views to replace the current reports and then add views as a dependency.
Comment #7
nicksanta commentedI've added in 2 reports using views.
1. The administration view at admin/settings/licensing/view
2. The user specific view at user/%
I think that wraps this up as a feature request. Any bugs regarding the views integration should have their own issues.