Closed (fixed)
Project:
Feeds Excel
Version:
7.x-2.2
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
28 Nov 2016 at 09:18 UTC
Updated:
17 Dec 2016 at 20:14 UTC
Jump to comment: Most recent
I installed the module and the version 1.8.0 of the PHPExcel library.
I'm importing a quite simple XLS file, with one sheet, I trimmed it for testing purpose to just 3 rows.
I didn't change any default settings of the importer,
while importing, the feed keeps looping, creating a number of equal rows until I don't unlock the feed.
Note that there is no unique row.
Anybody had such issue?
Comments
Comment #2
mrromios commentedHi
Can you send me your XLS file?
I will be happy to help)
Comment #3
artsakenos commentedThank you Darth, the file can be downloaded here, togheter with the export of the feed importer.
The feed I created is pure new, I stopped all the running cron processes before trying again, I removed any tamper, the GUID reference you see in the file lead to a non recursive importer.
Comment #4
netmachina commentedYes, in 7.x-2.2 there is infinite import issue (random xlsx file, unfortunately - I cannot share it :( ). It is not happening in version before - 7.x-2.1.
I have downgraded, and it works fine.
Comment #5
netmachina commentedLittle fix, the getTotal() count returns wrong value (count of all cells, not only rows)
Comment #7
mrromios commentedHi all!
Thanks for activity)
@netmachina, yep you are totally right! It was issue with total counter (cells instead of rows (doh))
Fixed and pushed into 7.x-2.x.
Please, try to use 7.x-2.x-dev version and if all is OK I will make release with fix.
Comment #8
mrromios commentedComment #10
daveX99 commentedI see that the last message in this thread indicates a fix for the bug discovered by @netmachina was added to the 7.x-2.x-dev version by @darth romios back in December of 2016.
There wasn't any feedback and the issue was closed 2 weeks later.
After experiencing this problem, I noticed that the last update to the DEV version is more recent than that of the 'official' versions. I switched from 'official' to 'dev' version of the module in my project and it solved my problem.
The fix added to the DEV module back in 2016 should be pushed to the 'official' version.
Thanks.
-dave.