Home › Forums › Template Support › Unable to install jbelieve church Joomla on Site5 hosting platform
-
Sherdon ForbesSubscriberI have been trying to install the joomla jbelieve church template on Site5 my hosting platform but I am unable to pass the Database Restoration stage after putting in the correct requested information. I have since contacted Site5 but they are also unable to get pass this stage and has inform me to contact the developer of the Joomla jbelieve church tmeplate to get this issue resolved. Please see below the Site5 support staff response to my ticket on Wednesday, October 16, 2019 at 08:59 CDT:
“Hello,
Thank you for contacting support,
We have tried to replicate the issue by installing your Joomla application your domain pentabja.com/pentabjoomla and we could see that the akeeba backup is trying to restore the database and while restoring the database we are getting the error saying that Specified key was too long and it’s Max length has to be 767 bytes as per the Error we are facing here is the error message we are receiving :
========================
Database server error reply:ErrNo #1071
Specified key was too long; max key length is 767 bytes
SQL=CREATE TABLEb8qje_akeeba_common
(key
varchar(192) COLLATE utf8mb4_unicode_ci NOT NULL,value
longtext COLLATE utf8mb4_unicode_ci NOT NULL, PRIMARY KEY (key
) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci
Raw query text:CREATE TABLE
#__akeeba_common
(key
varchar(192) COLLATE utf8mb4_unicode_ci NOT NULL,value
longtext COLLATE utf8mb4_unicode_ci NOT NULL, PRIMARY KEY (key
) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci
========================We request you to contact your developer and ask them to check on this Error and update the key size accordingly.
If you have any further queries please feel free to contact us. We are available 24X7.
Sincerely,
Tushar Rokad
Web Advisor
Site5 Web Hosting
https://www.site5.com/”
TonyModeratorHi Tushare,
It seems your server does not support the modern UTF8MB4 encoding. For this case, please check two options “Force UTF8” while restoring the package, like this https://imgur.com/a/dRURofp
You must be logged in to reply to this topic.