• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

Can't fix Invalid use of NULL value upon upgrade

Affected version
2.0.0

NixFifty

Well-known member
#1
Code:
Running upgrade to 2.0.0 Alpha, step 1... done.
Running upgrade to 2.0.0 Alpha, step 2... done.
Running upgrade to 2.0.0 Alpha, step 3... done.
Running upgrade to 2.0.0 Alpha, step 4... done.
Running upgrade to 2.0.0 Alpha, step 5... done.
Running upgrade to 2.0.0 Alpha, step 6... done.
Running upgrade to 2.0.0 Alpha, step 7... done.
Running upgrade to 2.0.0 Alpha, step 8...
                                                      
  [XF\Db\Exception]                                   
  MySQL query error [1138]: Invalid use of NULL value
 

Chris D

XenForo developer
Staff member
#2
Does your xf_conversation_message table already have a like_users field, perhaps from another add-on?
 

NixFifty

Well-known member
#3
That would explain it. Thought I'd made sure table-wise everything was sound but apparently missed that one. :D

Thanks!
 

Mike

XenForo developer
Staff member
#4
Just to clarify, was this from an add-on, or were you doing some manual table manipulations?
 

NixFifty

Well-known member
#5
Just to clarify, was this from an add-on, or were you doing some manual table manipulations?
From an add-on. I thought I'd checked beforehand to make sure there weren't going to be any column name clashes but i'd missed the xf_conversation_message table so mistakenly thought it was a core issue. :)
 

Floyd R Turbo

Well-known member
#8
So if we have this addon, what has to be done prior to attempting an upgrade? Just removing the addon, or does a table have to be edited / column deleted?
 

Chris D

XenForo developer
Staff member
#9
Looks like it will be a simple case of upgrading it to a soon to be released version before carrying out the upgrade.
 

NixFifty

Well-known member
#10
So if we have this addon, what has to be done prior to attempting an upgrade? Just removing the addon, or does a table have to be edited / column deleted?
There'll probably be an update out for it which will rename the conflicting column name for XF1 users, most likely.
 

Xon

Well-known member
#13
I was using "`like_users` blob DEFAULT NULL," so disabling the add-on doesn't break XF1 conversations. I guess I'll just rename it away, and in the XF2 version drop those columns.