WordPress database error: [Expression #1 of ORDER BY clause is not in SELECT list...

Hi, We’re using DO managed database for two of our Wordpress sites, one of them shows the following error with debug=true in wp-config.php

WordPress database error: [Expression #1 of ORDER BY clause is not in SELECT list, references column ‘wordpress-programs.wp_posts.post_date’ which is not in SELECT list; this is incompatible with DISTINCT]
SELECT DISTINCT YEAR( post_date ) AS year, MONTH( post_date ) AS month FROM wp_posts WHERE post_type = ‘attachment’ ORDER BY post_date DESC

Wordpress 5.2.3. PHP, MySQL 8.0.16 - Linux

The other site is just fine, see config below and the content is identical i.e we have similar posts on both

Wordpress 5.2.3 PHP 7.2.19-0ubuntu0.18.04.2, MySQL 8.0.16 - Linux

We’ve tried the fixes for Disable ONLY_FULL_GROUP_BY from the following link but didn’t help. Can you please review and help?

Thanks James

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hi Bobby,

Thanks, that was quick!

I did see this post before posting but please note that I’m not privy to what the DO support guys instructed this user to do, and also just guessing it was similar to - SET SESSION sql_mode=(SELECT REPLACE(@@sql_mode,‘ONLY_FULL_GROUP_BY’,‘’));

Which I tried with no luck



I think recently another person had the same issue. You can have a look at this question here:

They were able to fix the problem by setting the sql_mode on session as instructed by the DO support team.

Hope that this helps! Regards, bobby