Hello,

After updating, we always get this error when we want to delete an item from the overview page:

Unknown column 'Array' in 'where clause' SQL=SELECT c.id, c.title, c.alias, c.introtext, c.fulltext, c.image_caption, c.image_credits, c.video_caption, c.video_credits, c.extra_fields, c.extra_fields_search, c.metakey, c.metadesc, jfc.id as jfc_id, jfc.value as titleTranslation, jfc.modified as lastchanged, jfc.published as published, jfc.language_id, jfl.title as language, jfc.reference_id as jfc_refid FROM #__k2_items as c LEFT JOIN #__falang_content as jfc ON c.id=jfc.reference_id AND jfc.reference_field='title' AND jfc.reference_table='k2_items' AND jfc.language_id=3 LEFT JOIN #__languages as jfl ON jfc.language_id=jfl.lang_id WHERE c.id=Array ORDER BY c.title

Are you using 2.7 and Falang?

Yes inded, but we've updated Falang to the latest version, released today. Is this because of Falang?

this is ok?
c.id=Array ??? don't be simple value???

Hi,

No, it's still there. As well in Falang 2.2.2 as in latest falang version we have this issue.

Jeroen

Hello,

Can you try the latest DEV version?
github.com/getk2/k2/archive/master.zip

I have same problem.

Using latest master from k2 repository and also latest Falang 2.5 with k2 2.4 content element.

When I try to unpublish the item I get this:

An error has occurred.
1054 Unknown column 'Array' in 'where clause' SQL=SELECT c.id, c.title, c.alias, c.introtext, c.fulltext, c.image_caption, c.image_credits, c.video_caption, c.video_credits, c.extra_fields, c.extra_fields_search, c.metakey, c.metadesc, jfc.id as jfc_id, jfc.value as titleTranslation, jfc.modified as lastchanged, jfc.published as published, jfc.language_id, jfl.title as language, jfc.reference_id as jfc_refid FROM #__k2_items as c LEFT JOIN #__falang_content as jfc ON c.id=jfc.reference_id AND jfc.reference_field='title' AND jfc.reference_table='k2_items' AND jfc.language_id=3 LEFT JOIN #__languages as jfl ON jfc.language_id=jfl.lang_id WHERE c.id=Array ORDER BY c.title

Thank you for reporting this.
I am reporting this on github as well, we will look into it and let you know.

Was this fixed? I'm trying to find a fix but everything I tried its not working. I have the exact same error message.

Hello Gorast,

We are still working on it.