Add a relation between IDF_Project and IDF_Tag (again), this time

its a many-to-many. We store project tags in IDF_Tag with a project
id "0" (this has minimal to no impact on existing code) and therefor
only need to ensure that the new relation table exists in the migration.

Then just the project summary configuration and the admin's project
create and project update forms and views needed to be adapted to
be able to render, create and update project tags.
This commit is contained in:
Thomas Keller
2011-12-11 01:38:56 +01:00
parent 14be872724
commit 95faf0468a
13 changed files with 356 additions and 28 deletions

View File

@@ -86,6 +86,13 @@ class IDF_Project extends Pluf_Model
'verbose' => __('description'),
'help_text' => __('The description can be extended using the Markdown syntax.'),
),
'tags' =>
array(
'type' => 'Pluf_DB_Field_Manytomany',
'blank' => true,
'model' => 'IDF_Tag',
'verbose' => __('labels'),
),
'private' =>
array(
'type' => 'Pluf_DB_Field_Integer',