The problem is probably related to your MySQL (or MariaDB) configuration. To be exact and as described here dev.mysql.com/doc/refman/5.7/en/innodb-limits.html if "innodb_large_prefix" is set to false, this limit is imposed to databases with utf8mb4_unicode_ci collation.

Your hosting company may have set this option explicitly for backwards compatibility reasons (the default is enabled).

The other option is to download and extract the K2 zip file and edit the file /administrator/components/com_k2/install.mysql.sql replacing all instances of "CHARSET=utf8mb4 DEFAULT COLLATE=utf8mb4_unicode_ci" with "CHARSET=utf8 DEFAULT COLLATE=utf8_general_ci". Then repackage the contents you extracted into a new zip file and finally install that file in Joomla.

Hi there
I cant install K2 extension in my joomla website
Joomla 3.9.15
PHP version 7.3.14
Database Type mysql
Database Version 5.6.47-cll-lve

Error message
Warning
JInstaller: :Install: Error SQL Index column size too large. The maximum column size is 767 bytes.
Extension Install: SQL error processing query: DB function failed with error number 1709
Index column size too large. The maximum column size is 767 bytes.
SQL =

CREATE TABLE IF NOT EXISTS `#__k2_tags` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`name` varchar(255) NOT NULL,
`published` smallint(6) NOT NULL DEFAULT '0',
PRIMARY KEY (`id`),
KEY `idx_name` (`name`),
KEY `idx_published` (`published`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 DEFAULT COLLATE=utf8mb4_unicode_ci;

Error
Error installing component
Any idea ?
Thank you

Joomla non installa a causa del seguente errore ( vedi sotto).
Cosa suggerite ?

Grazie
________________________________________________________________

Warning
JInstaller: :Install: Error SQL Index column size too large. The maximum column size is 767 bytes.
Extension Install: SQL error processing query: DB function failed with error number 1709
Index column size too large. The maximum column size is 767 bytes.
SQL =
CREATE TABLE IF NOT EXISTS `#__k2_tags` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`name` varchar(255) NOT NULL,
`published` smallint(6) NOT NULL DEFAULT '0',
PRIMARY KEY (`id`),
KEY `idx_name` (`name`),
KEY `idx_published` (`published`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 DEFAULT COLLATE=utf8mb4_unicode_ci;
×
Error
Error installing component

Hi ,

I already tried to install the new version, but unfortunately there is an error message ...

SQLSTATE[42S02]: Base table or view not found: 1146 Table 'd030e732.qeqo4_k2_items' doesn't exist

It's a fresh joomla installation ...

best regards

Amine

Hello!
I have installed Joomla with latest version and K2 v2.9.0. When I try to update K2 to v2.10.2, I receive an error: Unknown character set: 'utf8mb4'.
Default charset of MySQL server ir UTF8, DB default charset is UTF8, also tables default charset is utf8.
What is the problem?

Please let us know if you solve your issues. It may help others as well in the future.

I'm sorry but I can't possibly know what's wrong with your site. You're the first to report such an issue. If it's not a corrupt Joomla/K2 installation, it may be some system plugin causing issues. Start disabling your 3rd party "system" or "k2" type plugins one by one to see which one affects your category save action.

Re-install Joomla from the Joomla Update component and then re-install K2 as well.

I try "maximum reporting" - no more info =(
I get this error when i save the category settings (K2 -> Categories - > "My category" and press [Save & Close]

Set error reporting to maximum in Joomla's Global Configuration and check again if more information is reported while installing K2.

Where can I find it?

I can't tell much about this. The error should probably indicate more. Can you paste the full error redacting the path up to Joomla's root folder?

When I try to save the K2 category settings I get this error: [1064] 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 '' at line 3.

K2 v2.10.1

I'm confused. How did you save a category when there's no category editing in the frontend?

The SQL error may be caused by an outdated 3rd party K2 or system plugin.

As for the error on your console tab, perhaps another JS script is attaching click events to K2's frontend editing controls.

If you want me to have a thorough look, use the contact form on this site and send me temporary super-user access.

Fotis wrote: Works just fine on my test sites and no error in the browser console. Which K2 version are you using and on what browser? Is your browser up to date?

Hi Fotis,

Apologies for the delay in responding:

Using K2 v2.10.0
[Dev Build 20190522]

Have been using Chrome and just tested again. Opened an item in the front end, saved and got the "item saved" message, clicked CLOSE and the page just closed the tab completely.

Just tried FireFox and when CLOSE is clicked, the age refreshed but did not close back to the normal page, remained in the Edit mode.

Not sure if this is relevant but when saving a Category I get the following error:

1064 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 '' at line 3

My server still runs MySQL 5.7 but I can upgrade to MariaDB 17 if you think this may resolve both problems.

Thanks

Chas

Hello everybody,

I am new here and new to Joomla CMS also. I have a client that have a website builded through Joomla but now he is having an problem when click to store an item through K2 Items. He received an error message :

DateTime:::__construct(): Failed to parse time string (-1-11-30 00:00:00) at position 5 (-): Double timezone specification.

The website is builded by another webmaster and now is maintaned by our company but we arent finding an solution for this problem.

He is using Joomla 3.7.3 and K2 2.7.0

Web Server Apache/2.4.10 (Debian)
PHP version 5.6.17-0+deb8u1
MySQL version 5.5.47-0+deb8u1
GD image library 2.1.1-dev

Can you help me with any solution please ?

Thank you,
Enea.

Ok, originally my problem was rooted—I thought—in moving a site to a new hosting service. I tried various things. But before I posted this, I decided I would try it with a brand-new fresh install, and I get the same error message. So it can't be due to my old files which is what I thought was the problem.
When I try to install K2 I get
JInstaller: :Install: File does not exist /home/mxxx/public_html/xxx/tmp/install_5d59d98726f2e/components/com_k2/k2.php

[This was what I was first going to post.]
Originally, I moved all the folders and files and imported the database I exported from the old site.

There is an error message in the display area where K2 would appear on the main administrator page (An error has occurred.
0 Class 'K2HelperHTML' not found). I tried reinstalling K2, uninstalling, reinstalling. I tried fresh files and folders of Joomla and installing K2.
When I try to install I get
JInstaller: :Install: File does not exist /home/xx/public_html/xxx/tmp/install_5d59d98726f2e/components/com_k2/k2.php
Component Install: Failed to copy site files.

here is the system information:
PHP Built On Linux alabama.shnw.net 3.10.0-962.3.2.lve1.5.25.10.el7.x86_64 #1 SMP Wed May 29 04:37:40 EDT 2019 x86_64
Database Type mysql
Database Version 5.5.5-10.1.41-MariaDB-cll-lve
Database Collation utf8_general_ci
Database Connection Collation utf8mb4_general_ci
PHP Version 7.2.21
Web Server Apache
WebServer to PHP Interface litespeed
Joomla! Version Joomla! 3.9.11 Stable [ Amani ] 13-August-2019 15:00 GMT
Joomla! Platform Version Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT
User Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.100 Safari/537.36

Fotis

Hello!
Thanks for your response

As I read that several people when updating the apartment had problems I was afraid.

It happens to be a Daily News site and I'm worried about updating and giving some trouble.

Until yesterday before the update of Joomla 3.94 to 3.95 I did not have any kind of problem, everything worked perfect.

That's why I have not updated yet.

It happens that the Mysql database is very large and I intend to only make a backup of the news, if I have problems I have one more chance to recover besides the daily Backups that I do. More than 150 thousand news

As I read that several people when updating the apartment had problems I was afraid.

So I'm trying to find out if there's anyone who has ever had this to try to solve without risking it.

I await your comments
abs
Success
Carlos Tegs

This is not related to K2. It looks like a DB error occurring after MySQL or MariaDB was switched to recovery (after a corrupt InnoDB data file).

See this as well: stackoverflow.com/questions/9595852/mysql-got-error-1-from-storage-engine-error

Fotis, I got this from Nicholas K. Dionysopoulos this morning:

First of all, it's normal to have a mix of collations when you try to convert a site. Some older software may have not updated its database structure for UTF8MB4 requirements. For instance, MySQL only allows database keys with entries up to 767 bytes long. If you have a VARCHAR(192) column it takes up 3 x 192 = 576 bytes under UTF8 but 4 x 192 = 768 bytes under UTF8MB4. This makes it an invalid key size. If there's an INDEX / KEY on that column the conversion to UTF8MB4 will fail, therefore it needs to remain plain old UTF8.

That said, this has absolutely nothing to do with your problem! If you look at the error message, it tells you that trying to write to the Joomla menu table, and that failed because something tried to store the value -1 on a column which is supposed to only accept unsigned long integers. "Unsigned" means "without a sign", i.e. only positive values. Clearly, -1 is negative, not positive, hence it's out of range.

The column level where this happens is what is used internally by Joomla! to figure out the hierarchy of menu items. Therefore the error message tells us that your Joomla! menu structure is, not to put too fine a point on it, cocked up. The first thing you should try is going to the backend of your site, Menus, Manage and click the Rebuild button in the toolbar. It tries to fix exactly this kind of issues.

If that didn't make any difference then you should probably rebuild your site, as painful as it may be, because that'd mean you have a far more complicated issue.

PS: You may wonder why this happened when you tried to install an update. It's probably because Joomla is trying to regenerate the backend Components menu during the update of any component. Since the menus table, shared by the front- and backend, is screwed up this triggered an invalid data write which raised the database error.

So I rebuilt all the menus, but K2 2.9.1-dev still threw the same database value out of range range exception when trying to store and unsigned varchar of -1.

So I thought, OK, I'm done, I will just have to start from scratch and then begin migrating everything over.

But I decided to try one more thing. I downloaded the most recent version of K2 2.9.0 and tried to install that over the existing installation of K2 2.9.1, and to my surprise, it installed without throwing any exception.

Since that was successful, I decided to try re-installing the latest dev build of K2 2.9.1, and again to my surprise, everything installed without exception.

I think something must have gone wrong because of installing several different dev builds of K2 2.9.1.