CCK

Buenos días a todos.

Les escribo porque otra vez me surge una situación que se va haciendo cada vez más frecuente (por lo menos, para mí) y no se cuál sería el enfoque más adecuado desde lo semántico y desde lo técnico. ¿Cómo gestionar objetos compuestos dentro del Drupal?

This is just an idea.

We've built sites on Mambo/Joomla in the past. mosforms, an extension to build and output custom forms and store the input much like CCK works for Drupal, was yet a simple, but great component to design site contact and other forms for Joomla. mosforms has evolved and is available as Fabrik - Joomla Application Builder now. There is nothing that might compete with our CCK here, but the last line of the published roadmap for Fabrik sounds quite interesting to me:

Since several people expressed interest at our first meeting expressed interest in the Content Construction Kit (CCK), which is an add-on for 4.7 and built-in to 5.x, I wanted to highlight this article just posted at Lullabot:

What is the Content Construction Kit? A View from the Database (March 7)

Feel free to use this space to ask questions about CCK, talk about features, provide examples, or talk about the article.

I just published a pretty long and thorough article describing the basics of CCK inner workings:
http://www.lullabot.com/articles/an_introduction_to_the_content_construc...

Hope you like it, and hope it is useful.

I would just like to inform/promote a site that I have worked on for the Sustainable Living Foundation. It is still a work in progress after nearly 2 years of involvement. Now, I have not spent all that time on this site and have built about 15 other sites in this time with drupal among other things. This site started with drupal 4.6 and has made it to 4.7.4. I can't remember all the modules I have utilised or trialed in this period along with two whole themes developments. The theme is shared across all six proposed multi sites but has a specific style file for each site.

There is no real 'announcement' system for CCK developers, so hopefully everyone who maintains a CCK module is subscribed to this group and will see this item. I want to forewarn everyone that we are about to make changes to the tablenames for CCK due to a new problem that emerged in 5.x with user-configurable content types. The problem is that our current system is to create a table for each content type called 'node_example' where 'example' is the name of the content type.

Torrent for my high quality screencap of the Fourth Lesson is up!. The whole thing is 2:20 and about 180mb.

If you want to post a recode or other derivative, drop a link in the comments here and I'll flesh out the main node with more downloads.

[scroll down for English version]

Ayer fuimos cinco que nos reunimos en lo que es "el bar de siempre" ("Meeting Place", sobre la esquina de Lavalle y Montevideo).
Charlamos sobre cómo estamos usando Drupal, de cómo usamos Drupal en nuestros lugares de trabajo, y vimos una presentación de una aplicación de una base de datos de contactos y empresas y seguimiento de llamadas creado utilizando Views y CCK (más theming y scripts para importación de los datos) con Drupal 5.0 rc2.

I am trying to weed out the many broken or duplicate flexinode fields.

The first differentation I want to make is between critical and non-critical fields. With a new release (4.7 and 5.0) the critical fields should all be released and working. Non-critical fields can be updated later.

I want to know what you consider critical fields, my personal list is included below.

• textfield
• textarea
• datefield/timestamp
• number
• image
• general file
• selectlist
• checkbox
• url
• email
• multiselect

Please leave your list in a comment.