- Issue created by @DamienMcKenna
- πΊπΈUnited States DamienMcKenna NH, USA
This seems to only happen when Queue Order is installed.
- πΊπΈUnited States DamienMcKenna NH, USA
After the form is submitted, this is what Table::validateTable() is trying to process:
This is the data from $complete_form['queues']['values'] in Table::validateTable():
This is the data from $complete_form['weight']['values']:
Clearly the problem is that the item weight is taking precedence over the item processing.
- π¦πΊAustralia jnlar Sydney, Australia
Not exactly the same issue as yours @DamienMckenna but I also get the error when I try to batch process just a single queue that has cron disabled, as I was testing a use case where I wanted to manually batch process the queue.
As
$form['cron']
is a table it's also being validated againstTable::validateTable()
and failing due to 'Cron time' not being set: - Status changed to Needs work
3 months ago 8:34am 3 October 2024 - πΊπ¦Ukraine voleger Ukraine, Rivne
Trying to reproduce the issue by functional test
- Merge request !53Issue #3390467: "No items selected" when submitting the overview page when Queue Order is installed β (Merged) created by voleger
- πΊπ¦Ukraine voleger Ukraine, Rivne
It looks like it is fixed in 3.2.x. Anyway, I added an update for the submit handler. If the test and changes look good, I'll going to merge MR and close the issue. I have a plan to release 3.2.0 within a week.
-
voleger β
committed 150bb67f on 3.2.x
Issue #3390467: "No items selected" when submitting the overview page...
-
voleger β
committed 150bb67f on 3.2.x
- πΊπ¦Ukraine voleger Ukraine, Rivne
I have a related issue in π Better support for Derivative queue workers Active , so I'm merging that. Also, I'll keep this issue open for feedback.
- Merge request !55Issue #3390467 by voleger, damienmckenna, jnlar, ivnish: "No items selected" when submitting the overview page when Queue Order is installed β (Merged) created by voleger
-
voleger β
committed 783ab9f8 on 3.2.x
Issue #3390467 by voleger, damienmckenna, jnlar, ivnish: "No items...
-
voleger β
committed 783ab9f8 on 3.2.x
- πΊπ¦Ukraine voleger Ukraine, Rivne
I see no need to change the cron time limit in bulk. I refactored, changing the cron limit for specific queues in a separate edit form. Also, it allows us to avoid changing the limit by accident by submitting order changes.
Merged changes into 3.2.x
Automatically closed - issue fixed for 2 weeks with no activity.