Hello,
I'm building a new site with K2 2.6.6 and Joomla 3.0. I am trying to setup a site that users can contribute to. Users can open and edit an article form with no problem, but on trying save the article, the site throws this error:

---

You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND trash = 0' at line 1 SQL=SELECT MAX(ordering) FROM joom_k2_items WHERE catid = AND trash = 0

---

I am using sh404sef, but the error occurs whether the component is enabled or not. Any ideas?

Thanks,
Nelson

PS - Everything works fine from the backend.

Ah, getting closer to a resolution. It appears to be something I changed in the form style. When I set the form style to "-default-" instead of my custom style, that fixes the problem.

In case anyone else ever makes the same mistake, I'll update here when I figure out exactly what I changed that caused the issue.

:woohoo: finally..
please kindly inform me, how did you resolve this? puhleeeeease :side:
i've got stressed out because i couldn't save or create new k2 items from front submission :pinch:

Which version of Joomla! and K2 are you using?
Are you using any overrides for the itemform.php file?

Hi...
I am currently on Joomla 3.2.2 and K2 version of 2.6.7 ( now upgraded to 2.6.8 but nothing change)

Sys Info :

System information
Check Result

Web Server Apache
PHP version 5.3.28
MySQL version 5.5.32-cll
GD image library bundled (2.1.0 compatible)
Multibyte string support Enabled
Upload limit 50M
Memory limit 64M
Open remote files (allow url fopen) Yes

attached the screenshot of the error

@chomz

Hi. Are you using any third party K2 or content plugins ? I just tested under Joomla! 3.2.2/K2 2.6.8 and had no issues.

hi... I really dont understand what was wrong .. already tried to put on/off several plugins and modules, switching templates, etc.. no good result at all
finally i decided to re-create the site from zero.. thankfully it's a new site so i only have to rewrite tens k2 articles or so :(

In order to identify such issues in the future you can enable debugging under Joomla! configuration while you are building the site. This should give you more details regarding the error.