#103483EXT:seo requires DB column 'sorting'
Description
A DB column ‘sorting’ is generated by the core if a TCA ctrl entry ‘sortby’ => ‘sorting’ is present. Neither the existence of a sortby nor the usage of this fieldname is mandatory. However, if the database column ‘sorting’ is missing, EXT:seo does throw a fatal error
An exception occurred while executing 'SELECT * FROM […] ORDER BY `sorting` ASC': Unknown column 'sorting' in 'order clause'
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
History 6
-
Christian Rieke commented and changed subject
EXT:seo requires DB colum 'sorting'EXT:seo requires DB column 'sorting' 03/25/24, 16:07 -
Chris Müller commented 03/25/24, 18:35
Which table are you referring to? Can you give an example?
-
Chris Müller changed status
NewNeeds Feedback 03/25/24, 18:35 -
Christian Rieke commented 03/25/24, 21:22
Sorry, just a misconfiguration. In the EXT:seo data provider TypoScript, I should have changed the line “sortField = sorting” to “sortField = uid”, as clearly stated in the documentation, instead of just deleting the line.
Please close the issue, thanks.
-
Oliver Bartsch commented 03/26/24, 07:36
Thanks for the feedback. I’m closing the issue now. In case you encounter similar issue again, feel free to open a new issue with reference to this one.
Best, Oli.
-
Oliver Bartsch changed status
Needs FeedbackClosed 03/26/24, 07:36
A DB column ‘sorting’ is generated by the core if a TCA ctrl entry ‘sortby’ => ‘sorting’ is present. Neither the existence of a sortby nor the usage of this fieldname is mandatory. However, if the database column ‘sorting’ is missing, EXT:seo does throw a fatal error
An exception occurred while executing ‘SELECT * FROM […] ORDER BY `sorting` ASC’: Unknown column ‘sorting’ in ‘order clause’
(Corrected typo in title)