Question 1071 Specified key was too long; max key length is 1000 bytes

I tried to install V6.34 onto a Joomla 4.46 site and see this error:   

An error has occurred.
1071 Specified key was too long; max key length is 1000 bytes

Any ideas what this means?   This install is part of a J3 > J4 Migration.  I uninstalled Kunena 5.x and all other K5 extensions before installing Kunena 6

 

Hello,

It seems that your are using MyISAM as storage type on your tables, so to fix this issue you need to change the storage type to InnoDB : dev.mysql.com/doc/refman/8.0/en/myisam-storage-engine.html

I see.  Thanks.   I'm migrating from a J3 site.

Does this means changing all the table to InnoDB storage type or jus the ones affecting Kunena?    I gather this will means playing inside the MySQL database software?
If so, is there a Query I can do or am I looking at doing thinga maniually?

Lastly,  Does the wrong storage type affect the instal or is this just a warning message?

UPDATE:

Just found this useful article:   www.nexcess.net/help/convert-myisam-to-i...atabase-performance/

I also took a look at my tables and all but the Kunena ones are already using the InnoDB Storage type.   Do all these tables need to be converted?

 


_discuss_priorities
_discuss_optimizer
_discuss_conversations_message
_discuss_points
_kunena_ranks
_discuss_tags
_discuss_favourites
_discuss_badges
_kunena_categories
_discuss_posts_tags
_discuss_conversations
_discuss_packages
_discuss_sync_request
_discuss_oauth_posts
_discuss_external_groups
_discuss_attachments_tmp
_kunena_attachments
_kunena_version
_discuss_posts_references
_discuss_configs
_discuss_subscription
_discuss_oauth
_discuss_download
_discuss_attachments
_kunena_announcement
_discuss_posts
_kunena_users_banned
_discuss_rules
_discuss_notifications
_akeeba_common
_discuss_comments
_discuss_assignment_map
_kunena_aliases
_wf_profiles
_discuss_post_types_category
_kunena_users
_discuss_roles
_discuss_migrators
_discuss_category_acl_map
_discuss_activities
_discuss_customfields_value
_discuss_post_types
_kunena_user_categories
_discuss_views
_kunena_user_topics
_discuss_reports
_discuss_mailq
_discuss_category_acl_item
_kunena_polls_users
_discuss_acl_group
_discuss_customfields_rule
_discuss_post_reject
_kunena_topics
_discuss_users_history
_kunena_user_read
_discuss_votes
_discuss_likes
_kunena_messages_text
_discuss_category
_kunena_polls_options
_discuss_ratings
_discuss_acl
_kunena_thankyou
_discuss_users_banned
_discuss_customfields_acl
_discuss_post_labels
_discuss_languages
_kunena_messages
_discuss_captcha
_kunena_polls
_discuss_ranks_users
_discuss_users
_discuss_customfields
_discuss_polls_users
_kunena_smileys
_kunena_logs
_discuss_honeypot
_discuss_badges_users
_discuss_tnc
_discuss_conversations_participants
_discuss_polls_question
_kunena_sessions
_discuss_holidays
_discuss_badges_rules
_discuss_ranks
_discuss_conversations_message_maps
_discuss_polls
_kunena_rate
_discuss_thread
_discuss_hashkeys
_discuss_badges_history
_kunena_configuration

Not sure, but it might have something to do with all your discuss tables. When I install the plugin in a clean J4 installation I have only one table named xxx_kunenadiscuss. Or those tables belong to another extension.

Hello,

All tables starting by kunena_ should be converted to InnoDB, in your screenshot the kunena tables are still in MyISAM

Thanks,  

Are the ones starting with xxx__discuss are not Kunena?   I thought it was maybe Kunena Discuss extension.

Also not sure what xxx_wf_profiles is.

These look to be leftovers from J3 (This site was recently migrated to J4)

 

xxx_wf_profiles is the profiles table for jce editor

AlexRag wrote:

Thanks,  

Are the ones starting with xxx__discuss are not Kunena?   I thought it was maybe Kunena Discuss extension.

 

If you had installed kunena discuss plugin, you will have a table nammed #__kunenadiscuss so your tables xxx__discuss are belonging to something else