- 🇳🇱Netherlands megachriz
Closed ✨ Import Progress Bar - for All items Closed: duplicate as a duplicate.
In there, I commented:
The reason is that each stage of the import happens in its own batch. So you get a serie of batches.
This is the import workflow, each step has its own batch:
- Fetch data
- Parse data
- Process a number of items
- If there's more to parse, repeat step 2 and 3.
- If there's more to fetch, repeat step 1 till 4.
An other issue is that Feeds cannot predict accurately how many items will be processed in the end. But I think this is mostly an issue when multiple fetches happen. Because in a second fetched file there could be 10 items, but there could also be 2000 items. In Feeds itself, only the directory fetcher does multiple fetches.
I would like to see this issue fixed, but because I have enough other Feeds tasks to do that I consider to be a higher priority I think I won't pick this one up myself in the nearby future.
- 🇬🇧United Kingdom adstokoe
Any updates on this issue? I've setup a custom fetcher to run on a paged API. The batch process does complete, however, the bouncing bar makes the process appear broken in the UI.
- 🇳🇱Netherlands megachriz
@adstokoe
It's bad UX, but it doesn't break functionality. And I think it's a hard one to fix. But because it doesn't break functionality, this issue is quite low on my priority list. My priority right now is first review and commit things that others have worked on recently. Then finish 🐛 in_progress filesystem grows indefinitely Active and create a new release and then get Feeds and related modules Drupal 11 compatible. And after that hopefully I'm able to resolve the remaining stable release blockers to finally create an official stable release. And after all that, then there might be room for me to address this issue. Though there also enough other issues that I think would have higher priority than this one. These are listed on 🌱 [meta] Feeds 8.x roadmap Active .So in other words, I don't see this issue getting addressed in the nearby future and probably not in the next two years. At least not by me.