fbpx
  Sunday, 10 May 2020
  23 Replies
  4.2K Visits
  Subscribe
Hi,

After installing, set rules for building a marketplace and enter all categories, it seems Sellacious is not the best component to build a marketplace with all product universes.

Indeed, after filled in 5.000 categories (Agriculture, food, furniture, ...), now Sellacious slow down.

If Sellacious slow down, this is because for each category you have to set % commission and for loading and made some setting in seller profile page, the page is slowing down.

Another problem, I don't know why I can create a product in the first level category.

In my case to explain this, I have:

Agriculture---->Beans----->Broad Beans
Agriculture---->Beans----->Butter Beans
Agriculture---->Beans----->Cacao Beans
...
...
etc...
etc...

There is no need to create a product in Agriculture Category and Beans category. I only have to create a product in Broad Beans category, Butter Beans category and Cacao Beans category.

I think we have to get a setting when we create a new category and set if this category will be only use as container or not. If I set my new category as container, it will mean I could not create a product inside this category. Maybe this functionality could fix the slow down problem when there is a lot of categories.

Is it possible to set some limits category when a seller post a new product. For example, a new seller make a registration on my sellacious marketplace, set his interest to 1 or 2 or 3 categories because its own company selling greenhouses. This new user don't have need to post a product in food or bathroom, etc... Maybe this could also fix the slow down problem.

If I missing something about categories and settings could you give me some advices for working with all my categories perfectly.

If all works perfectly, I will subscribe to get B2B settings in addition for my needs.
3 years ago
·
#4921
However, I would like to point out a problem: when I search for the categories to be matched on the product page, it only works by looking for the main language. It would be right that if I am looking at the backend in Italian, it would make me search in Italian (as the preview of the results shows me)
3 years ago
·
#4922
I get the following error when attempting to upgrade Sellacious. I am currently on 2.0 Beta 1

Thanks
3 years ago
·
#4923
Hi all-sizes,

I had to delete completely Sellacious and make a complete reinstallation after a lot of trouble with table "doesn't exist".

After that, table #__sellacious_seller_timings was missing with this error in sellacious backend edit profile and I posted a bug report here: https://www.sellacious.com/community-support/4909-sellacious-beta3-warning-__sellacious_seller_timings-doesn-t-exist

In phpmyadmin I had to write a command sql: (replace "#_ " with your "prefix table"Emoticon Wink

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;

and all works.

Hope this help.
  • Page :
  • 1
  • 2
There are no replies made for this post yet.
Be one of the first to reply to this post!
  • +1 (408) 821-8283
  • Email hello@sellacious.com