Forum

Forgot password?
  2. Forum
  3. SCHLIX CMS
  4. General Discussion
  5. Install;ation error

General Discussion

Install;ation error

Alexxx
Alexxx · 2020 Jan 10 @ 05:39

This is what i get when i install...




Every thing in the test is ok by installing but after that no install..






Database schliks exists.


Creating tables...


-- Table structure for table `gk_app_items`

-- Table structure for table `gk_bannedip_items`

-- Table structure for table `gk_block_categories`

-- Table structure for table `gk_block_config`

-- Table structure for table `gk_block_items`

-- Table structure for table `gk_block_menu_association`

-- Table structure for table `gk_blog_categories`

-- Table structure for table `gk_blog_items`

-- Table structure for table `gk_blog_categories_items`

-- Table structure for table `gk_config`

-- Table structure for table `gk_contact_categories`

-- Table structure for table `gk_contact_items`

-- Table structure for table `gk_contact_messages`

-- Table structure for table `gk_cronscheduler_items`

-- Table structure for table `gk_cronscheduler_items`

DB Error - Could not run query: CREATE TABLE IF NOT EXISTS `gk_cronscheduler_items` ( `id` bigint(20) NOT NULL AUTO_INCREMENT, `title` varchar(191) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'untitled', `cron` varchar(512) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `date_created` datetime DEFAULT NULL, `date_modified` datetime DEFAULT NULL, `date_available` datetime DEFAULT NULL, `date_expiry` datetime DEFAULT NULL, `date_lastrun_start` datetime DEFAULT NULL COMMENT 'Last Start', `date_lastrun_end` datetime DEFAULT NULL COMMENT 'Last Run', `date_expected_next_run` datetime DEFAULT NULL, `created_by_id` bigint(20) unsigned NOT NULL DEFAULT '0', `modified_by_id` bigint(20) unsigned NOT NULL DEFAULT '0', `command_type` tinyint(1) DEFAULT NULL, `command_internal` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `command_external_url` varchar(512) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `send_email_to` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `status` int(11) NOT NULL DEFAULT '0', `is_system_cron` tinyint(1) DEFAULT NULL, PRIMARY KEY (`id`), KEY `status` (`status`), KEY `command_internal` (`command_internal`), KEY `date_expected_next_run` (`date_expected_next_run`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; Error:Index column size too large. The maximum column size is 767 bytes.
prana
prana · 2020 Jan 10 @ 13:34
Hi Alex,

A quick solution to this is to upgrade your MySQL server to version > 5.7.6 or MariaDB > 10.2.1.

Regardless, it was an oversight because all our test servers use MySQL 5.7 and 8.0.

Thanks for reporting the bug, expect a fix within 1 - 2 weeks.
Alexxx
Alexxx · 2020 Jan 13 @ 13:58
thank you, i'm on a webhost so i can't change the version of the mysql or maria db. So i will wait for the update! Thank you fot the fast reply.
Alexxx
Alexxx · 2020 Jan 23 @ 07:49
i downloaded 2.2.1 latest and tried again.



I have php 7.4 and 10.1.43-MariaDB-cll-lve - MariaDB Server





Database exists.


Creating tables...



[/i]gk_app_items

[/i]gk_bannedip_items

[/i]gk_block_categories

[/i]gk_block_config

[/i]gk_block_items

[/i]gk_block_menu_association

[/i]gk_blog_categories

[/i]gk_blog_items

[/i]gk_blog_categories_items

[/i]gk_config

[/i]gk_contact_categories

[/i]gk_contact_items

[/i]gk_contact_messages

[/i]gk_cronscheduler_items

[/i]gk_cronscheduler_items

[/i]gk_cronscheduler_log

[/i]gk_stats_dailyhits

[/i]gk_email_queue_items

DB Error - Could not run query: CREATE TABLE IF NOT EXISTS `gk_email_queue_items` ( `id` bigint(20) NOT NULL AUTO_INCREMENT, `queue_marker` varchar(36) DEFAULT NULL, `hourly_marker` varchar(13) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `guid` varchar(36) COLLATE utf8mb4_unicode_ci NOT NULL, `field_subject` TEXT COLLATE utf8mb4_unicode_ci DEFAULT NULL, `field_from_name` varchar(127) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `field_from_email` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `field_to_name` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `field_to_email` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `field_cc_name` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `field_cc_email` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `field_replyto_name` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `field_replyto_email` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `field_bcc` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `field_return_receipt` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `field_priority` tinyint(3) NOT NULL DEFAULT 0, `field_xmailer` varchar(255) NOT NULL DEFAULT '', `store_folder` varchar(255) NOT NULL DEFAULT '', `field_sha1` char(40), `status` tinyint(3) DEFAULT '0', `retry_count` tinyint(3) DEFAULT '0', `date_queued` datetime DEFAULT NULL, `date_sent` datetime DEFAULT NULL, `date_last_retry` datetime DEFAULT NULL, `extra_headers` TEXT COLLATE utf8mb4_unicode_ci DEFAULT NULL, `attachments` text COLLATE utf8mb4_unicode_ci DEFAULT NULL, PRIMARY KEY (`id`), KEY `queue_marker` (`queue_marker`), KEY `field_to_email` (`field_to_email`), KEY `date_sent` (`date_sent`), KEY `status` (`status`), KEY `hourly_marker` (`hourly_marker`), KEY `status_hourly_marker` (`status`, `hourly_marker`), KEY `unsent` (`status`,`retry_count`), KEY `count_period` (`status`,`date_queued`), KEY `date_queued` (`date_queued`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; Error:Index column size too large. The maximum column size is 767 bytes.

prana
prana · 2020 Jan 23 @ 12:18
Hi Alexxx, thanks for the follow up and helpting us test it. Looks like we'll have to retest with that specific version installed on your server.

In addition to MySQL 5.7 and 8.0, we tested it with an older version of Ubuntu 14.04 with MySQL 5.5.62 and didn't give an error and hence we released it.

We'll retest with MariaDB 10.1.43 and will get back to you soon.
prana
prana · 2020 Jan 26 @ 21:17
Hi Alexxx,

Attached is a ZIP file containing the fixed version of /system/apps/sitemanager/sql/install_step1.sql. If you extract it and replace the file, it should install just fine. We're still quite a few weeks away from another release, so I thought I'd post an interim fix for now.

Let me know if this doesn't work.
Attachment(s)
Alexxx
Alexxx · 2020 Jan 30 @ 13:29
no more errors ! thank you!