In Sellacious backend: Go to User Profile / select no matter user (Sellers, All, Clients, ...) / and edit this user profile and you will get this warning message with nothing else: Warning #__sellacious_seller_timings' doesn't exist.
Could you reproduce it? Do you have something to fix it?
Hi, we are fixing this issue in next update, for now create these two tables manually.
CREATE TABLE IF NOT EXISTS `#__sellacious_seller_timings` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`seller_uid` int(11) NOT NULL,
`type` varchar(50) COLLATE utf8mb4_unicode_ci NOT NULL,
`week_day` int(11) NOT NULL,
`from_time` time NOT NULL DEFAULT '00:00:00',
`to_time` time NOT NULL DEFAULT '00:00:00',
`full_day` tinyint(1) DEFAULT NULL,
`slot_window` int(11) NOT NULL,
`slot_window_unit` varchar(50) COLLATE utf8mb4_unicode_ci NOT NULL,
`today_availability` time NOT NULL DEFAULT '00:00:00',
`state` tinyint(1) NOT NULL DEFAULT 1,
`created` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
`created_by` int(11) NOT NULL,
`modified` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
`modified_by` int(11) NOT NULL,
`params` text COLLATE utf8mb4_unicode_ci NOT NULL,
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS `#__sellacious_product_seller_slot_limits` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`seller_uid` int(11) NOT NULL,
`product_id` int(11) NOT NULL,
`slot_from_time` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
`slot_to_time` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
`full_day` tinyint(1) NOT NULL,
`slot_limit` int(11) NOT NULL,
`slot_count` int(11) NOT NULL,
`created` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
`modified` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
Hi, we are fixing this issue in next update, for now create these two tables manually.
CREATE TABLE IF NOT EXISTS `#__sellacious_seller_timings` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`seller_uid` int(11) NOT NULL,
`type` varchar(50) COLLATE utf8mb4_unicode_ci NOT NULL,
`week_day` int(11) NOT NULL,
`from_time` time NOT NULL DEFAULT '00:00:00',
`to_time` time NOT NULL DEFAULT '00:00:00',
`full_day` tinyint(1) DEFAULT NULL,
`slot_window` int(11) NOT NULL,
`slot_window_unit` varchar(50) COLLATE utf8mb4_unicode_ci NOT NULL,
`today_availability` time NOT NULL DEFAULT '00:00:00',
`state` tinyint(1) NOT NULL DEFAULT 1,
`created` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
`created_by` int(11) NOT NULL,
`modified` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
`modified_by` int(11) NOT NULL,
`params` text COLLATE utf8mb4_unicode_ci NOT NULL,
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS `#__sellacious_product_seller_slot_limits` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`seller_uid` int(11) NOT NULL,
`product_id` int(11) NOT NULL,
`slot_from_time` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
`slot_to_time` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
`full_day` tinyint(1) NOT NULL,
`slot_limit` int(11) NOT NULL,
`slot_count` int(11) NOT NULL,
`created` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
`modified` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
Hi, we are fixing this issue in next update, for now create these two tables manually.
CREATE TABLE IF NOT EXISTS `#__sellacious_seller_timings` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`seller_uid` int(11) NOT NULL,
`type` varchar(50) COLLATE utf8mb4_unicode_ci NOT NULL,
`week_day` int(11) NOT NULL,
`from_time` time NOT NULL DEFAULT '00:00:00',
`to_time` time NOT NULL DEFAULT '00:00:00',
`full_day` tinyint(1) DEFAULT NULL,
`slot_window` int(11) NOT NULL,
`slot_window_unit` varchar(50) COLLATE utf8mb4_unicode_ci NOT NULL,
`today_availability` time NOT NULL DEFAULT '00:00:00',
`state` tinyint(1) NOT NULL DEFAULT 1,
`created` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
`created_by` int(11) NOT NULL,
`modified` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
`modified_by` int(11) NOT NULL,
`params` text COLLATE utf8mb4_unicode_ci NOT NULL,
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS `#__sellacious_product_seller_slot_limits` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`seller_uid` int(11) NOT NULL,
`product_id` int(11) NOT NULL,
`slot_from_time` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
`slot_to_time` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
`full_day` tinyint(1) NOT NULL,
`slot_limit` int(11) NOT NULL,
`slot_count` int(11) NOT NULL,
`created` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
`modified` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
Hope this helps.
Thanks.
I'm having the same error... how do we "Create the table?"
What version of sellacious you are having in shop now ?
this query works with beta3 version only
if not pls upgrade to beta3 version.
thanks.
I'm using v2.0.0-beta3
PHP Built On Linux joomla 5.4.0-1034-gcp #37-Ubuntu SMP Wed Jan 6 19:44:41 UTC 2021 x86_64
Database Type mysql
Database Version 8.0.22-0ubuntu0.20.04.3
Database Collation utf8mb4_0900_ai_ci
Database Connection Collation utf8mb4_0900_ai_ci
PHP Version 7.4.3
Web Server nginx/1.18.0
WebServer to PHP Interface fpm-fcgi
Joomla! Version Joomla! 3.9.24 Stable [ Amani ] 12-January-2021 15:00 GMT
Joomla! Platform Version Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT
User Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.141 Safari/537.36
Hi,
Kindly check your mysql version. Recommenced version is MySQL v5.5.3+ or MariaDB 10.1.22+ (with InnoDB suppert enabled).
Also joomla version 3.9.16 is officially supported with beta3 version.
Check with these two and let me know if still not working.
Hi,
Kindly check your mysql version. Recommenced version is MySQL v5.5.3+ or MariaDB 10.1.22+ (with InnoDB suppert enabled).
Also joomla version 3.9.16 is officially supported with beta3 version.
Check with these two and let me know if still not working.
Thanks.
MySQL version as noted in my previous response is 8.0.22 and I can confirm InnoDB support is enabled.
So the latest version of Joomla (3.9.24) is NOT supported and it won't work?
Can you check with Mysql version 5.x, seems like it is because of your mysql version.
About your joomla 3.9.24 question- When beta3 version was launched it was was tested with latest joomla at that time which was v3.9.16 but that doesn't mean it will not work with v3.9.24 but it is recommended to have joomla 3.9.16
Hi
Our next update will be compatible with joomla 3 9 24 and php7.4, we will think of joomla4 and php8 in later updates.
Thanks.
Page :
1
There are no replies made for this post yet. Be one of the first to reply to this post!
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here. Register Here »