Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I 'upgraded' from -alpha2 to -dev, both from 25dec2010.
Now, the following scenario does not work anymore:
- create a Feeds importer
- 'Import' nodes from a csv file. Afterwards, status says 'Importing - 100 % complete.'
- discover that some/most/all of your node are incorrect, so correct the data in the csv-file
- 'Delete items' . Afterwards, status has extra message 'Deleting items - 100 % complete.'
- 'Import' nodes again from csv file.
In -dev version, the last step is not possible anymore: the Import-button is greyed-out, as if the delete-process is still going on. Also, the Import button has the text 'Deleting (100%)'
It seems that some internal status is not set 'complete'?
I can work-around this issue by cloning the Feeds. (which works fine in -dev, not in -alpha2)
Comments
Comment #1
ymeiner CreditAttribution: ymeiner commentedYes, it happened to me to. any luck with that?
Comment #2
johnvI now can 'reset' the Import the following way:
- open www.example.com/phpmyadmin and choose the database
- goto table 'feeds_source'
- reset the fields 'state' and 'fetcher_result' by setting the values to 'b:0;' (copy from other record to avoid typo's)
I do not know (anymore) if this is caused
- with any importer;
- only with existing importers after an 'upgrade' from -alpha2 to -dev;
- only for importers that are created via a feature.
I also had the impression that it was provoked by running multiple importers simulaneaously in different tab's of my browser.
@ymeiner, what is the history of your Importers?
Comment #3
johnvFYI: I encountered one case where I could clear the status by starting cron: admin/config/system/cron
For a bigger importer I needed to start cron multiple times. Normally I do not set 'Process in background' and my cron is not running on my dev-installation.
Comment #4
sonar_un CreditAttribution: sonar_un commentedI ran into this issue, but unfortunately, johnv's suggestions didn't work for me. Though it did point me in the right direction.
In PhpMyAdmin, I found the table 'feeds_source' and looking at the 'state' field, this is what I had.
a:5:{s:5:"fetch";O:10:"FeedsState":8:{s:8:"progress";d:1;s:7:"pointer";N;s:5:"total";i:0;s:7:"created";i:0;s:7:"updated";i:0;s:7:"deleted";i:0;s:7:"skipped";i:0;s:6:"failed";i:0;}s:13:"process_clear";O:10:"FeedsState":8:{s:8:"progress";d:1;s:7:"pointer";N;s:5:"total";i:0;s:7:"created";i:0;s:7:"updated";i:0;s:7:"deleted";i:0;s:7:"skipped";i:0;s:6:"failed";i:0;}s:10:"start_time";i:1304024171;s:5:"parse";O:10:"FeedsState":8:{s:8:"progress";d:0.9994469463537962727883723346167244017124176025390625;s:7:"pointer";i:189750;s:5:"total";i:189855;s:7:"created";i:0;s:7:"updated";i:0;s:7:"deleted";i:0;s:7:"skipped";i:0;s:6:"failed";i:0;}s:7:"process";O:10:"FeedsState":8:{s:8:"progress";d:1;s:7:"pointer";N;s:5:"total";i:0;s:7:"created";i:1995;s:7:"updated";i:0;s:7:"deleted";i:0;s:7:"skipped";i:0;s:6:"failed";i:0;}}
-------------------------------------
Where the "{s:8:"progress";d:0.9994469463537962727883723346167244017124176025390625" obviously looked strange to me as the rest of the indicators said it should be d:1. I changed it to this:
{s:8:"progress";d:1;s:7:"pointer";i:189750;s:5:"total";i:189855;s:7:"created";i:0;s:7:"updated";i:0;s:7:"deleted";i:0;s:7:"skipped";i:0;s:6:"failed";i:0;}s:7:"process";O:10:"FeedsState":8:
After the change (I had to change the source in two of my importers), the fix worked!
I hope this helps.
Comment #5
fultonchain CreditAttribution: fultonchain commentedI can confirm this and also that the fix in #4 also worked for me.
If it sheds any light on the matter, in my case the issue only arose with one of several CSV files. It seems likely that the import/deletion was failing to complete because of a character encoding or formatting issue.
Unfortunately, I no longer have file available for examination.
Comment #6
TrevorBradley CreditAttribution: TrevorBradley commentedAlso had this problem, very annoying.
Comment #7
Inarus CreditAttribution: Inarus commentedHave the same problem on alpha 4. I can import and/or delete only 50 nodes. I have "d:0.9994469463537962727883723346167244..." instead of "d:1". Need to import over 250K nodes so this it`s huge problem for me. I`ll try 7.x-2.x-dev
Comment #8
Inarus CreditAttribution: Inarus commentedThe same story at 7.x-2.x-dev. Importer grab ~13000 nodes and stops :/
Comment #9
ehmprah CreditAttribution: ehmprah commentedSame here: importing exactly 24600 nodes, then aborting with a 504.
Comment #10
zambrey CreditAttribution: zambrey commentedSubscribing. Very annoying bug.
Comment #11
Yorgg CreditAttribution: Yorgg commentedSame issue here.
Subscribing
Comment #12
Yorgg CreditAttribution: Yorgg commentedI thought this was the case though it's not. Good luck.
Comment #13
NicoB CreditAttribution: NicoB commentedSame "NOP" here.
Subscribing.
Comment #14
mwbyrd CreditAttribution: mwbyrd commented#4 Worked for me. Thanks Guys!
Comment #15
johnvgood idea mbbyrd: giving feedback: indeed, using #4 is a good workaround!
Comment #16
MrHaroldA CreditAttribution: MrHaroldA commentedA 'reset' button for crashed imports would be very helpful!
#2 is indeed a good workaround, but unacceptable for (most) users.
Comment #17
Dave.L CreditAttribution: Dave.L commented#2 did it for me...THX.
cancel button would be nice indeed :)
Comment #18
johnvFYI, The following issue seems to provide a UI for this problem: #1454666: Add tool to reset locked feeds
Comment #19
alexmc CreditAttribution: alexmc commentedI too have this problem. The "fix" of going in to my database to tweek a value by hand is not acceptable when I have thousands of records to import and it is falling over lots of times for unknown reasons (mostly character sets).
PS The Status of the feed is shown to be "Importing - 22 % complete." and has been for several days. I don't know how that maps to
if ($progress == FEEDS_BATCH_COMPLETE) {
It sure is not "ACTIVE" but the greyed out button saying "Importing (22%)" means that the module thinks it is.
Comment #20
Julien Verkest CreditAttribution: Julien Verkest commentedThe fix in #4 also worked for me. Thanks sonar_un
Comment #21
Jim Kirkpatrick CreditAttribution: Jim Kirkpatrick commentedWorks for me too... updating.
Comment #22
trillex CreditAttribution: trillex commentedThe fix in #4 always cancels the import for me. I'm having the exact same issues as #7 but the workaround, for me, was to untoggle "Process in background". This is on a minimal Drupal installation.
Comment #23
franzRTBC without patch?
Comment #24
iAugur CreditAttribution: iAugur commentedI had this same issue even with the latest dev version (7.x-2.x)
Feeds that had imported couldn't be used again - stuck on 'Initializing.'
I came up with a solution that may help someone else!
I had enabled the Title module to replace the node (entity) title field (actually product Title in a commerce install).
Deleting this replacement title field and reinstating the entity title enabled the feed to be run again!
Hope that helps someone else.
If this is the issue in your case then see #1613514: Importing nodes in bulk fail to create titles for all nodes after the first one for a related issue.
Comment #25
johnvLet's close this issue, since it should be resolved since June 27th, with this patch: #1454666-22: Add tool to reset locked feeds.