I seem to only get this error on my home/index page. all other templates, sub directories and the control panel seem to work without issue.

edit:

if i remove all exp:channel:entries tags on that page, the error goes away

does anyone know what this “m.url” column missing error is all about?

well embarrassingly, I was doing this locally to test/debug and think what happened was I accidentally imported the wrong DB file, so of course EE was confused by the wrong database.

I thought I’d figured this out and ironed out any bugs locally, but I tried to replicate my steps in production and received the same error.

attempted this again on my production server and am getting the same error

would there be any value in attempting to upgrade from 3 > 4 and then 4 > 5 instead of 3 > 5?

I’ve tried the EE 3 > EE 4 upgrade and get the exact same error.

Boy- you’ve almost worked all the way through!

> does anyone know what this “m.url” column missing error is all about?

Used to be, there was a ‘url’ field in exp_members. But that was removed and anyone that had records in it had a custom member field created to hold it. Because really, it didn’t need to be there by default.

So something you have on that homepage is still looking for that field in the old location.

Weirdly, it looks like it’s the channel module doing it, but that doesn’t really make sense.

You’ve got it on v5 now, right? Does it happen if you disable extensions?

If it’s still happening, try simplifying. Build that template up a section at a time until you can zero in on the smallest, simplest bit that causes the error.

Thanks Robin. I’ve done what you said and rebuilt the ee tags element by element.

it looks like including disable=”member_data” is triggering the error.

oddly enough, it only does that in the home/index template. other templates that also use a channel entries tag with disable=”member_data” specified still work?

does anyone have an ideas? i’m officially stuck and am unsure what to do

I have a similar problem on a site I’m currently trying to upgrade from EE2 (was originally on EE1).

Upgrade to EE 3 was fine, but on upgrading to 5, I get the following error on the User add-on’s page. (I made sure to upgrade add-ons as I went along with appropriate versions).

Any suggestions gratefully received!

Exception Caught

SQLSTATE[42S22]: Column not found: 1054 Unknown column ‘user_m_Preference_exp_user_preferences.site_id’ in ‘field list’: SELECT user_m_Preference_exp_user_preferences.preference_id as user_m_Preference__preference_id, user_m_Preference_exp_user_preferences.preference_name as user_m_Preference__preference_name, user_m_Preference_exp_user_preferences.preference_value as user_m_Preference__preference_value, user_m_Preference_exp_user_preferences.site_id as user_m_Preference__site_id FROM (exp_user_preferences as user_m_Preference_exp_user_preferences) WHERE ( user_m_Preference_exp_user_preferences.site_id = 1 ) LIMIT 18446744073709551615

ee/legacy/database/drivers/mysqli/mysqli_connection.php:117

Stack Trace: Please include when reporting this error

0 ee/legacy/database/drivers/mysqli/mysqli_driver.php(112): CI_DB_mysqli_connection->query(‘SELECT user_m_P…’)

1 ee/legacy/database/DB_driver.php(270): CI_DB_mysqli_driver->_execute(‘SELECT user_m_P…’)

2 ee/legacy/database/DB_driver.php(180): CI_DB_driver->simple_query(‘SELECT user_m_P…’)

3 ee/legacy/database/DB_active_rec.php(1138): CI_DB_driver->query(‘SELECT user_m_P…’)

4 ee/EllisLab/ExpressionEngine/Service/Model/Query/Select.php(49): CI_DB_active_record->get()

5 ee/EllisLab/ExpressionEngine/Service/Model/DataStore.php(282): EllisLab\ExpressionEngine\Service\Model\Query\Select->run()

6 ee/EllisLab/ExpressionEngine/Service/Model/DataStore.php(228): EllisLab\ExpressionEngine\Service\Model\DataStore->runQuery(‘Select’, Object(EllisLab\ExpressionEngine\Service\Model\Query\Builder))

7 ee/EllisLab/ExpressionEngine/Service/Model/Query/Builder.php(144): EllisLab\ExpressionEngine\Service\Model\DataStore->selectQuery(Object(EllisLab\ExpressionEngine\Service\Model\Query\Builder))

8 ee/EllisLab/ExpressionEngine/Service/Model/Query/Builder.php(63): EllisLab\ExpressionEngine\Service\Model\Query\Builder->fetch()

9 user/addons/user/mcp.user.php(1862): EllisLab\ExpressionEngine\Service\Model\Query\Builder->all()

10 user/addons/user/mcp.user.php(140): User_mcp->preferences(”)

11 [internal function]: User_mcp->index()

12 ee/EllisLab/ExpressionEngine/Controller/Addons/Addons.php(1662): call_user_func_array(Array, Array)

13 ee/EllisLab/ExpressionEngine/Controller/Addons/Addons.php(946): EllisLab\ExpressionEngine\Controller\Addons\Addons->getModuleSettings(‘user’, ‘index’, Array)

14 [internal function]: EllisLab\ExpressionEngine\Controller\Addons\Addons->settings(‘user’)

15 ee/EllisLab/ExpressionEngine/Core/Core.php(241): call_user_func_array(Array, Array)

16 ee/EllisLab/ExpressionEngine/Core/Core.php(110): EllisLab\ExpressionEngine\Core\Core->runController(Array)

17 ee/EllisLab/ExpressionEngine/Boot/boot.php(151): EllisLab\ExpressionEngine\Core\Core->run(Object(EllisLab\ExpressionEngine\Core\Request))

18 admin.php(153): require_once(‘…’)

18 admin.php(153): require_once(‘…’)

I wanted to circle back around as support was able to dig in and it turned out to be related to caching. For some reason, with memcache in use, it kept using an old query for one of the tags.

Clearing all caches cleared out the problem. But it was a weird one!

MID you’re running into something else- that looks related to the User third party add-on.

Do you have the latest version and have you run the update for it in the Add-ons section? If that doesn’t help resolve it, it might be better to start a new topic, just because this one is already a bit long and involved.

Thanks Robin. Sorry to butt in! I thought it might be worth joining this thread as the error messages seemed similar, and related to member fields being moved around during the upgrade from 3 to 5.

Upgrading User hadn’t helped but I was able to fix it by uninstalling and reinstalling.

No worries, it could have been related. It’s more likely than the weird caching issue it ended up being!

But yours is definitely something to do with User.