Bug #103483
closed
EXT:seo requires DB column 'sorting'
0%
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'
Updated by Christian Rieke 8 months ago
- Subject changed from EXT:seo requires DB colum 'sorting' to EXT:seo requires DB column 'sorting'
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)
Updated by Chris Müller 8 months ago
Which table are you referring to? Can you give an example?
Updated by Christian Rieke 8 months ago
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.
Updated by Oliver Bartsch 8 months ago
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.
Updated by Oliver Bartsch 8 months ago
- Status changed from Needs Feedback to Closed