Hello. I'm getting the following error after save the item:

23000 SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '0-536' for key 'PRIMARY'

I'm not sure if this began after made the update to Joomla 3.5 or k2 7.

Hello. I'm still having the this issue. Any help?

Thanks.

Hi,

I am not sure if this is caused by K2. I guess it is caused by a third-party extension. So try to disable some content or K2 plugins that might get triggered when the item is saved.

An other thing you could try it to disable the smart search indexing.

Solved. The problem was caused by Smart Search - K2 plugin.

Thanks.

You 're welcome.

My issue was not the Smart Search (which was slowing things down), but more with the Search Tags. The search may have been working but you would have to wait 10 minutes to see anything. I turned that off and now it's fast. There has to be a way to fix this. Tags need to be searchable on the site otherwise what's the point? Something for the development team to work on.

Which search are you using?
Joomla!'s mod_search or K2 Tools?

That probably would have been helpful to know up front. (Sorry, I've been working with other developers on this site and just lost track of what I said to whom).

It's not the search that is breaking, but an Ajax search. I'm using RokAjax (which I know slows things even more). The main problem is that they have over 1200 articles on their site. So to search through all of the text as well as tags bogs things down as they are.

But while searching on the default Joomla page (mod_search), and enabling the tag search, things are still very slow.

I should also say that I can't upgrade to K2 2.7 just yet. I tried that and it killed the site. Had to retro back to 2.6.9. So maybe this is fixed in 2.7 but I'll have to wait until another release of K2 to try it out. We are getting ready to launch the site and I can't have anything else delay it like a non-working K2 component. It's working great right now with the exception of not being able to search the tags.

RokAjax is an extension which we have no control over.
This is a 3rd party extension so you need to address this issue to the extension's developers.

Finally tag search will always slow your site down (hence the notice, and it being disabled by default), 1200 articles can mean queries searching through thousands of tags. One way to speed things up would be to possibly cache some queries.

I mentioned in the last post that the problem was not just RokAjax, it's the searching the tags that is the main issue. I know that it has the warning that it will slow things down, but large sites need to have the ability to search tags - that's just a necessity. There are a lot of queries that are cached in the search plugin, but it's still slow to respond. I was merely just asking if you guys were looking to improve on this or if you are just satisfied with telling people that it's going to be slow if you select that option.

I'm not seeing a response to that, so I have to assume that it is not in your plans. That's fine - I just needed to know that.
Thanks for your responses.

Even if we cache queries, even if we simplify and optimize each and every one query by hand, it would still be very intensive. We are using caching and the search is optimized but looking through thousands of tags will always be intensive. Since you have a large site and you want all of the item's content to be searchable you should looking to a GSE (Google Search Engine) integration.

That's the direction we're looking into now. Thank you for your help and advice.

Now you will get a double answer:
I have implemented this method in a K2 site containing 500k+ items with each item containing 4 - 7 tags at least.

You can understand the impact of such a query and the solution that Google Provides.