Bug #103483
closed
EXT:seo requires DB column 'sorting'
Added by Christian Rieke 8 months ago.
Updated 8 months ago.
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'
- 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)
Which table are you referring to? Can you give an example?
- Status changed from New to Needs Feedback
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.
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.
- Status changed from Needs Feedback to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by