Using CCK field does not work [#827128]

Comment	File	Size	Author
#6	node_import_update_01072011.patch	3.56 KB	jmrivero

Comment #1

jimmi61 commented 15 June 2010 at 14:29

Title:

Using CCK field does not work

» Things that work and do not work, IMHO of course :) [was: Using CCK field does not work]

I spent sometime in testing this nice addition and, compared with my expectation, I had the following problems:

- I did several tests, changing the hard coded settings and name of fields, but I was not able to use a CCK field as unique identifier.

- It is not working with Node Import via cron. The patch #422282-13: Update existing nodes on import does it and, moreover, allows to choose the unique identifier in a list, working also with CCK fields. Perhaps merging the two codes would be an improvement.

- One feature I really need is to update only the fields that have a value, leaving empty fields untouched, but it seems not to be an easy task.

I ought to help you guys in developing these nice things, but my skill is still not that good. I will try looking into the code and see if I understand anything.

Thanks for now
Jimmi

Log in or register to post comments

Comment #2

Krotty commented 22 June 2010 at 13:08

Title:

Things that work and do not work, IMHO of course :) [was: Using CCK field does not work]

» Using CCK field does not work

Fix for "CCK field as unique identifier"

      // Check if item already exists
      if ($IMPORT_UNIQUE_ID_IS_CCK) {
        // get unique id from cck fields
        //$unique_id_value = $form['#post']['cck:field_import_id:value'][0];
        $unique_id_value = $form['#post']['cck:'.$IMPORT_UNIQUE_ID_NAME.':value'][0];
        // build query
        //$query = 'SELECT c.nid, c.vid FROM {content_type_%s} c WHERE c.%s = "%s"';
        $query = 'SELECT c.nid, c.vid FROM {content_type_%s} c WHERE c.%s_value = "%s"';
      }