Closed (duplicate)
Project:
Feeds
Version:
7.x-2.0-alpha6
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
11 Oct 2012 at 01:11 UTC
Updated:
6 Sep 2013 at 08:14 UTC
Jump to comment: Most recent file
Comments
Comment #1
twistor commentedIt's really surprising that you would expect anyone to help you at all.
In the node processor settings, you need to select "Update existing nodes (slower than replacing them)".
One of the settings is indeed to rewrite the entire node.
Comment #2
back from 7 commentedThat is exactly the problem. I selected that option.
The only fields that were on my .csv import were nid and terms. My mappings were nid and term
The feeds module decided to delete all photos that were uploaded on the nodes. The fields that were intended to be updated were updated successfully.
Comment #3
back from 7 commentedSorry for my written frusteration. I have to deal with 20,000 nodes now missing photos.
Comment #4
twistor commentedCan you give me an export of your importer?
Comment #5
back from 7 commentedI deleted the entire site out of frusteration and now have a backup running. My advice to everyone is to test Feeds importers on a couple of nodes before updating all of your nodes. The setting "Update existing nodes (slower than replacing them)" did not work properly and I wish I documented what happened properly for maintainers.
TEST TEST TEST.
Again this is an awesome module overall! I was frusterated when I lost all my images.
Comment #6
back from 7 commentedThis happened again.
My .csv file had "Title" "Nid" and "Feature Type" and the importer deleted my photos that were not included on the importer csv file.
Nothing else was deleted but the photos were. I am not making this up. This time I only tested on 5 nodes, so I wouldn't lose thousands of photos.
It seems that Feeds is rewriting the entire node somehow and images are being stripped in the process.
Comment #7
back from 7 commented$feeds_importer = new stdClass();
$feeds_importer->disabled = FALSE; /* Edit this to true to make a default feeds_importer disabled initially */
$feeds_importer->api_version = 1;
$feeds_importer->id = 'featuretaxtypeupdate';
$feeds_importer->config = array(
'name' => 'FEATURETAXTYPEUPDATE',
'description' => '',
'fetcher' => array(
'plugin_key' => 'FeedsFileFetcher',
'config' => array(
'allowed_extensions' => 'txt csv tsv xml opml',
'direct' => FALSE,
),
),
'parser' => array(
'plugin_key' => 'FeedsCSVParser',
'config' => array(
'delimiter' => ',',
'no_headers' => 0,
),
),
'processor' => array(
'plugin_key' => 'FeedsNodeProcessor',
'config' => array(
'content_type' => 'feature',
'expire' => '-1',
'author' => 0,
'authorize' => 1,
'mappings' => array(
0 => array(
'source' => 'Nid',
'target' => 'nid',
'unique' => FALSE,
),
1 => array(
'source' => 'Title',
'target' => 'title',
'unique' => FALSE,
),
2 => array(
'source' => 'Type',
'target' => 'field_feature_typetax',
'unique' => FALSE,
),
),
'update_existing' => '2',
'input_format' => '2',
'skip_hash_check' => 0,
),
),
'content_type' => '',
'update' => 0,
'import_period' => '-1',
'expire_period' => 3600,
'import_on_create' => 1,
'process_in_background' => 0,
);
Comment #8
back from 7 commentedCould someone explain the process of updating certain fields on a node through feeds.
I only want to update taxonomy terms on nodes and not touch any other field that is populated. My current importer above is stripping image fields that are already populated.
Anyone?
Comment #9
Michsk commentedI have the same issue. It seems that when you want to update an existing node that has images in it, but you're new source does not have images defined, it removes the image (even the file itself).
Comment #10
Michsk commentedi think this also is for you : https://drupal.org/node/2049341
Comment #11
johnvIf your csv file contains columns for all fields of a node, then Lasacs options are for you.
If you have a csv-file with only the fields you want to change, see #1047894: Behavior when fields/columns are not in import file: do not clear field, but leave field untouched.
Comment #12
johnvI gues we can close this as a duplicate of the issues mentioned in #10 and #11