I haven't had time to look at it yet but in ArticlesModel, we have two ordering fields in the query without using Alias, and it could cause wrong ordering value returned, thus causes error with Drag and Drop ordering in Articles management
https://github.com/joomla/joomla-cms/blob/4.0-dev/administrator/components/com_content/src/Model/ArticlesModel.php#L255
https://github.com/joomla/joomla-cms/blob/4.0-dev/administrator/components/com_content/src/Model/ArticlesModel.php#L276
If someone could figure out why we need that ordering data (especially from #__content_frontpage table), that would be great.
Labels |
Added:
?
|
Isn't this the messy featured items?
I haven't had a chance to read the code myself carefully yet. However, because of this bug, the wrong ordering value for each article will be used on articles view, mean re-ordering articles in article management won't work properly. (I found this issue why trying to test the PR #33937 )
If someone could figure out why we need that ordering data (especially from #__content_frontpage table)
Isn't this the messy
featured items
?
@dgrammatiko Yes, #__content_frontpage
is the table for that messy thing .. the table of which I wish it never had been created. The columns could have been added to the content table. This would maybe waste a few kilobytes space on a big table where the columns would be used only for a few % of all data, but it would have saved us from so much trouble. Well, all I can say is .. it wasn't me
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2021-05-20 05:32:40 |
Closed_By | ⇒ | joomdonation |
Isn't this the messy
featured items
?