[#48492] - [6.2] Order of Modules
- New
- Medium
- Build: 6.2
- # 48492
forum.de users have reported:
... keep noticing that the order of the modules changes on its own as soon as I edit, save, and close one of these modules. This happens with the site modules as well as with the administrator modules.
... clicked the icon with the small triangles pointing up and down (second column).
Now the drag handles become active (three dots stacked vertically).
I reorder the modules as desired → everything works fine.
Days later, I open one of these modules to make a change.
After saving and closing it, the module is in a different position.
Is this because the indexing in the database is incorrect?
Only when you correctly enter the position index consecutively (0..x) for each module in the database does it work with the selection field. Previously, there were multiple positions labeled 0.
Perhaps the index for each position should be fundamentally rebuilt before sorting.
Other users reported:
... that this is indeed how it behaves.
The reason for this is the "Order" field in the module editor—its value is always set to the first module instead of the module's own rank. When you save the module this way, the order changes accordingly
... I’ve experienced this a few times myself, but I can no longer reproduce it on new pages.
Is anyone else familiar with this?
Votes
| Labels |
Removed:
?
|
||
joomla-cms-bot
- | Labels |
Added:
No Code Attached Yet
|
||
I am the person who originally reported this issue on the DE forum. I am posting here so that I am automatically notified of any updates to the issue. Please feel free to contact me if you need any further information!
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48492.
| Labels |
Added:
bug
|
||
I checked the database. In the ordering column there are values between 1 and 14. No «0».
I may not have mentioned this yet:
The bug also occurs when you sort the filtered list view and there are duplicate index entries.
The only explanation maybe is that this happens when you move a module to a different position, and the indexes aren't rebuilt at that point.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48492.
I may not have mentioned this yet:
The bug also occurs when you sort the filtered list view and there are duplicate index entries.
The only explanation maybe is that this happens when you move a module to a different position, and the indexes aren't rebuilt at that point.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48492.
This kind of known issue that hard to catch and reproduce. I think it is since Joomla 3 time to time happen to me.
There already should be an openned issue for this.
If someone will find, please link it. Thanks
I had this sometimes but cannot replicate. Mabe it is something with cache - https://github.com/joomla/joomla-cms/blob/5.4-dev/libraries/src/Form/Field/ModuleorderField.php
I had this sometimes but cannot replicate. Mabe it is something with cache - https://github.com/joomla/joomla-cms/blob/5.4-dev/libraries/src/Form/Field/ModuleorderField.php
When the error occurs, the mouleorderfield input is wrong, it sets the active module on place 1
I had this sometimes but cannot replicate. Maybe it is something with cache - https://github.com/joomla/joomla-cms/blob/5.4-dev/libraries/src/Form/Field/ModuleorderField.php
When the error occurs, the mouleorderfield input is wrong, it sets the active module on place 1
I had this sometimes but cannot replicate. Maybe it is something with cache - https://github.com/joomla/joomla-cms/blob/5.4-dev/libraries/src/Form/Field/ModuleorderField.php
When the error occurs, the moduleorderfield input is wrong, it sets the active module on place 1
@ChristineWk thanks, that they are :)
I am the person who originally reported this issue on the DE forum. I am posting here so that I am automatically notified of any updates to the issue. Please feel free to contact me if you need any further information!
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48492.