User tests: Successful: Unsuccessful:
Pull Request for Issue #24008 .
Starts the ordering with 1 instead of 0, this allows to use getNextOrder in table store function for new items. This is used in com_modules.
Thx to @bembelimen for helping to find and fixing this issue.
N/A
| Status | New | ⇒ | Pending |
| Category | ⇒ | JavaScript Repository NPM Change |
did you run npm ci ?
Does PR manage the ID of the modules? Do I understand correctly?
No this is about the order of the modules - a different field altogether
I have tested this item
I tested with the administrator modules in the cpanel position, full screen for dragging and narrow responsive screen for checking order. (Glitch on first reload? But...) Seems to work as described.
I have tested this item
| Labels |
Added:
?
|
||
RTC
RTC
| Status | Pending | ⇒ | Ready to Commit |
| Status | Ready to Commit | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-11-28 02:29:49 |
| Closed_By | ⇒ | wilsonge | |
| Labels |
Added:
?
|
||
Thanks!
The ID starts with 1, it's fine but still random.

I don't have 109 modules.
Does PR manage the ID of the modules? Do I understand correctly?