Suddenly i am facing with this issue. When i am trying to save a new article i see the below msg and nothing is getting save.

You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '' at line 6 SQL=UPDATE jos_k2_items SET video_caption = '', video_credits = '', extra_fields = '[]', extra_fields_search = '' , published = '1' WHERE id =

This is on joomla 1.5.22

Hi,

First of all, it is highly recommended to upgrade to the latest Joomla 3 version.
Then, which K2 version have this issue?
Do you have any K2 plugins installed?
Do you find any javascript issues/errors?

The k2 is 2.5.5. for now i will stick with joomla 1.5 and when i find time i will upgrade it. I can't find any other problems and the front works just fine. The back-end as well. The only issue i find is when i am trying to save articles. Yes i have k2 plugins install but it is just to show the articles in the front. It was working fine few days ago.

I disabled the plugins but the same issue exist.

Well, maybe it is helpful to enable debugging and set error reporting to maximum or development to find out in which file the problem happened.
Make sure to disable debugging and set error reporting to its previous value after testing.

Hello. This is the error:

jDatabaseMySQL::query: 1064 - You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ')}' at line 1 SQL=DELETE FROM jos_k2_tags_xref WHERE itemID={intval()}

2.5.5 and Joomla! 1.5.22 are not supported.
I would urge you to backup and update to Joomla! 1.5.26 and K2 2.7.1.

I did the update to joomla 1.5.26 and to k2 2.6 but i dont want to try 2.7.1 cause there are issues. I already did that update and the back end was messed up and didn't fix the error. So can you help me? The website was working fine the one day ad the other had this issue. By the way this is happening only to k2 component. From joomla article component i can save articles

You can try repairing your db's tables.
Where you always using MariaDB?

Yes this is the same db server

Did you try repairing the tables?