Closed (fixed)
Project:
Feeds Excel
Version:
7.x-2.1
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 Mar 2016 at 16:04 UTC
Updated:
10 Jan 2017 at 12:28 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
aolaze commentedI have same problem,but i set to 200 rows on Settings for Excel parser.
Comment #3
sosyuki commentedBut if sheet more than 200 rows.Set to 200 rows also don't import 200+ data.
Comment #4
mrromios commentedCan you send screenshot of you settings?
Comment #5
jaredcampbell commentedI didn't include the author user name or the mapping settings. Would prefer not to post user and database information. If that's required, then I'd be willing to share directly via email.
Comment #6
mrromios commentedAnd with this settings ExcelParser parses only 200 rows?
Comment #7
sosyuki commentedMy settings and node data.
Comment #8
jaredcampbell commentedWith my settings, only 19 rows are parsed. XLS files with fewer than 19 rows are processed without a problem. More than 19 rows, nothing is processed beyond row 19.
Comment #9
sosyuki commentedThis bug patch.
Comment #10
jerry commentedThe patch in #9 works for me. Thanks!
Comment #11
jaredcampbell commentedSorry for the delay in testing this...
Patch #9 worked in our testing environment. Moving over to production and will test again next week.
Comment #12
jaredcampbell commentedWe've had Patch #9 in production for a few weeks now and everything seems to be working.
Have imported upwards of 35 rows at a time without problem.
Thanks for the fix!
Comment #13
Alexandre360 commentedHello,
I had a excel with more than 20k rows and, before this patch, the import stopped after 3000 rows. Applied the patch and it works.
Seems critical to me as it's a bug that can have a big impact on business if you don't notice that your import stopped...
Comment #14
sinasalek commentedFix #9 works, however the patch does not apply due to formatting issue. also it contains some unused codes and comments as well
Here is the cleaned up version.
Comment #15
sinasalek commentedLine ending and path correction
Comment #16
mrromios commentedHi guys!
Sorry that didn't have a time to check it.
This patch works, but it is not very good solution for performance - you just run looping of all rows to find total.
I will check it right now and push fixes.
Thanks
Comment #18
mrromios commentedAs expected, it was issue with pointers. So, fixed now. Welcome to test new release!!!
Comment #19
mrromios commentedComment #21
sinasalek commented