Hi Robert, Interesting that you should mention date fields. This is the only barrier to cross before I start using CCK on my site. Care to share your code or getting it committed to the CCK project? Best regards. Frank On Sunday 11 June 2006 00:02, Robert Douglass wrote:

Unrelated to chx's patch, but befitting of the thread subject, I just started a CCK group: http://groups.drupal.org/content-construction-kit-cck

Having spent the day programming my first widget (date fields!), I can say that if you haven't considered developing CCK stuff, you're missing out. This is an incredible module. Join the group and let's get more people up to speed on programming CCK widgets and fields.

-Robert

Karoly Negyesi wrote:

...

Hi,

The first step of getting CCK closer to core is http://drupal.org/node/62340 . This was in the queue already but as Dries asked for reviews on it, webchick and I worked on it, so now it's really ready for reviews -- we have not found any obvious bugs.

Regards

NK

Interesting...

...

...

http://drupal.org/node/62340 .

Not, it's not interesting, it's thread hijack. What's interesting here is the patch. Go review, folks!

On 11-Jun-06, at 7:42 PM, Benson Wong wrote:

I was mucking around with the CCK for a little while. Great work so far. Is anybody working on a node type export/import?

I was definining some custom node types and thought it'd be nice if I could just export my new type to a simple text file and import it on another site.

Much like views. It's a good idea. Actually, considering our recent discussions about install profiles, exporting this in a format that would be compatible with install profiles/installer would be great. -- Boris

On Mon, 2006-06-12 at 09:32 -0500, Mark Fredrickson wrote:

...

Much like views. It's a good idea. Actually, considering our recent discussions about install profiles, exporting this in a format that would be compatible with install profiles/installer would be great.

I've spent some time on that:

http://drupal.org/node/58153

The difficulty is faking a form submission. All the saving/updating code is right in the _submit functions, so it is hard for modules to use CCK programmatically.

I've been debating factoring this out, but it is a large task. I haven't seen any love on my patch anyways, so I'm wondering if the effort is worth it, or if I should just wait for Jaza's generalized import/export API or FAPI 2.0 (which should make faking form submissions easier).

I'd say go a head and factor it even if you just create a cck_nodeapi_save() and pass through all the variables.... You can also call the hooks directly with the right parameters, but that just bugs me :)...

In penitence for my supporting the thread hijaking, I promise to review the original patch.

-Mark

Karoly Negyesi wrote: We're just keeping it alive for you =)

Noone has better things to do -- like reviewing http://drupal.org/node/62340 -- than hijacking this thread?

On 6/12/06, Benson Wong <mostlygeek@gmail.com> wrote:

Is anybody working on a node type export/import?

I was definining some custom node types and thought it'd be nice if I could just export my new type to a simple text file and import it on another site.

I am working on export / import of node types, and much more. See my Google SoC project, the Import / Export API: http://drupal.org/node/67043 Easily sharing things like CCK node types between sites (and even being able to create a public library of 'templates', consisting of exported node types and other things) is one of the key things that the API will let you do. Cheers, Jaza.