Domain Relationships Additions or Fork
| Project: | Domain Relationships |
| Version: | 6.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
First off, thank you for working on this module. The module seems very close to fulfilling requests that I have received from a client. I would like to describe my needs and plans for solution. I would like to identify if you plan to add such features to Domain Relationships, if I should work with you to add such features, or if I should develop my own module.
My client is running hundreds of sites with domain access. The client would like, eventually, to be running thousands of sites on Domain Access. There are a number of interfaces listing domains that become quite unwieldy with a high number of domain names. Additionally, some administrative tasks become inefficient and would be easier to manage with bulk actions.
Our concept for solving this problem is to create groups of domain names. Any list display of all domain names would be replaced by a single group of domain names along with a filter to select a different group for display (via AJAX — we want to avoid having to render in HTML the entire list of domains on each page load). I envision a 'select all' checkbox for each group.
I think what I'd like fits your data model for Domain Relationships. I would rather have the parent of a set of domains to be a independent label of some sort instead of a specific domain but such is only a small concern.
I am wondering if the sort of interfaces I have imagined would be something you'd like as part of Domain Relationships. I would be happy to work with you and add such to your module. Would I be better off working on my own module?
Am I being clear? Any questions?
#1
I absolutely think that you should base your functionality on this module.
Whether the interface would belong in this module or not depends on how useful it would be for the common user of this module. I don't believe most users of this module have thousands of domains and perhaps some of the features of the interface would be unnecessary clutter for them.
What I suggest you do is to start to build the interface as a separate module built upon this module api. Any modifications necessary in this module to support your module can be suggested through patches and when you have a version of your module to show we could work together to incorporate features where it feels it can contribute to the existing interface.
I think that would be the easiest solution giving you the most flexibility in maintaining and innovating while still improving this module as mush as possible without cluttering it or slowing down or smothering any of your efforts.
#2
Thanks for the response!
I have completed a first version of my module, which I'll call Domain Autocomplete, and I will release it soon. I ended up coding it only with hook_form_alter, validation, and AJAX routes. The module replaces Domain Access checkboxes with a single textfield input that autocompletes on site names and accepts multiples comma-separated values. I modeled the behavior on standard tag inputs.
I'll post a link in the next week when I have it all packaged nicely.