Posted by adrian on September 26, 2009 at 2:11pm
| Project: | Hosting |
| Version: | 6.x-0.4-alpha1 |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs work |
Issue Summary
During the 0.1 development we had some basic support for views 1.x, but we ended up removing it because it would have taken too much work to support fully, and then we would have to rewrite it entirely for views 2.x
Now that we have a stable D6 release, it's time to work on views 2.x support for Aegir.
Comments
#1
I think we should avoid *depending* on views and keep on doing our own stuff for now. Adding views hooks so that fields show up in views and can be part of filters is fine, however.
#2
Here is a start, I think it defines almost all the main fields and there are a few filters as well, it probably needs a little more work, but its functional and you should be able to generate a lot of the current tables used in the hosting front end with this views support.
#3
this is excellent so far, but there needs to be some special handling regarding relationships.
it is giving us 'hosting site => platform id' and 'hosting site => profile id', but what it should be doing is generating a text field linked to the right node.
but really, this is almost committable.
#4
I spent some time working on this , replacing the fields being exposed with relationships.
http://skitch.com/vertice/d1177/t
It also provides a new plugin type for site tables, and a default view with all the related fields.