Timeline for Batch API timeout during initialization
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 6, 2018 at 13:33 | comment | added | Sardis |
Remember this line of code? $context['finished'] = $context['sandbox']['progress'] / $context['sandbox']['max']; The bar will be shown based on it. E.g. the bigger the value, the closer progress bar to the end. Yet you are right,the message below progress bar "Performing 1 out of 1" will make no sense. However, $context['message'] = "Processing: {$po_entry->s_name}"; will appear above the progress bar. That's how you will be able to determine the current progress, along with percentages.
|
|
| Apr 6, 2018 at 10:26 | comment | added | NoRandom | First of all, thanks for your very detailed answer. I wasn't aware that the batch tasks were stored in the DB and that adds delay to the process. After posting the question I took a workaround, dividing the long list of tasks into smaller chunks of ~20-40 elements. It's working fine but of course the progress bar just shows each of those chunks of tasks. I imagine that the situation with your approach would be similar and having just one big action would make the progress bar totally meaningless. Am I right? Regards and thanks again. | |
| Mar 29, 2018 at 17:43 | review | Late answers | |||
| Mar 29, 2018 at 17:44 | |||||
| Mar 29, 2018 at 17:24 | history | answered | Sardis | CC BY-SA 3.0 |