Biblio, CCK dependency/support
janusman - May 20, 2009 - 19:09
| Project: | Millennium Integration |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | task |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Version 1.x depended on Biblio module, and the current 2.x-DEV version does not.
I am not so convinced the module should require Biblio again, since IMO Biblio is reproducing a lot of functionality from CCK/Views; my gut feeling is that Millennium module could *support* it in a basic way (allow importing into Biblio-type nodes) but not at all depend on it.
To be fair, Millennium module 2.x-DEV is also reproducing a little bit of Biblio, but just the store-and-show-bibliographic-data part.
I would prefer to move 2.x into requiring CCK; then we'd have views & more automatically.
I need to read issues like #397332: Conversion to CCK data model. Post more issues or links here.
#1
To programatically create CCK content types, see:
http://drupal.org/node/458578#comment-1573848
http://groups.drupal.org/node/5272
http://blog.daveslist.co.nz/drupal6/2008/10/01/define-content-types-and-...
#2
rjerome mentions biblio probably won't be CCK until D7: http://drupal.org/node/397332#comment-1344572
#3
Useful link for creating CCK fields upon module installation:
http://drewish.com/node/134
http://drewish.com/node/118
#4
Tagging this as critical; I think this is the next thing to take care of (whether using CCK or Biblio) in order to gain Views and other support.
I'm leaning towards CCK instead of Biblio.
#5
Not very familiar with Biblio. However, CCK seems to be a safe bet, with the D7 core integration and stuff. So maybe I would vote for CCK.