Jump to content



Member Since 18 Oct 2018
Online Last Active Today, 05:17 PM

Posts I've Made

In Topic: Variations 2.0 In Cs-Cart & Multi-Vendor 4.10.1

Today, 12:46 PM

It would be much better to have a backend name for the feature, which would be used to import/export and a frontend name for the customer.

It would make managing features much easier.


Let me summarize for you the gist of the above BugTracker issue.


feature_size in Group1 has ID 2345

feature_size in Group 2 has ID 3456


When importing products of the two groups, feature_size of group 2 is imported with the wrong ID because the system finds first that the ID of feature_size is 2345, looks for all instances of feature_size and assigns to them ID 2345.

In Topic: Variations 2.0 In Cs-Cart & Multi-Vendor 4.10.1

Today, 10:44 AM

This seems to be a big issue. If the name of the feature is Size, and there are 10 feature groups containing different features with different ID but one and the same name Size, import will mix them up, as reported here
This is because the feature name taken into account is derived from the name of the feature, i.e., feature_size in English, feature_размер in Russian, feature_größe in German, and so on. We can have 10 different instances of feature_size multiplied by the number of the active languages. Feature-id is not referred to - or is referred only once, to make the things worse and replace the other FIDs, CODE of the feature is also being left without attention. All these variation factors are not taken into account, hence the total mess.

In Topic: Migrating Store With 2Nd Storefront, Addon Domain Cpanel How To

Yesterday, 12:48 PM

No, if you migrate via cpbackup

In Topic: Variations 2.0 In Cs-Cart & Multi-Vendor 4.10.1

Yesterday, 06:23 AM

a merchant may want only 2 methods of providing "Size". ( I.e. 4, 6, 8, 10, 12, 14, 18, etc.and XS, S, M, L, XL, XXL).


Actually, there will be a multiverse of Sizes:


Hats Size

Shirt and Blouse Womens Size

Shirt and Jacket Mens Size

Children Clothes Size

Trousers Size

Socks Size

Mens Shoes Size (EU, US, UK, JA, CH)

Womens Shoes Size 

Children Shoes Size

Bike Size

Ring Size

Wrist Size

Elbow Size

Book Size

etc., etc ad nauseum


Each of these Sizes has its own variation logic and standards/unit measures. Classes of classes within subclasses of the general idea of Size...

In Topic: Mve Plus Some Advices To Cs-Cart

23 March 2019 - 01:31 PM

Common Products for Vendors (CPV) is still in BETA, as is the entire MV Plus. The biggest problem of CPV is that it creates a new product_id for the selected common product but does not inherit its properties, only refers to them. The chosen CP should be entirely cloned and the vendor should be given access to all its tabs, not just to 3 of them. If you want to help vendors sell more products, do not restrict their privileges and permissions.


As for your points, here is how some MVP owners solve the case


1. Allow creating own products. When the product is created, take it from the vendor and turn it into common product, then all vendors can appropriate it. - This in my view is a bad practice, but working if you don't nurture some scruples.


2. Returns are not possible in MVP, esp. if you activate the Separate Checkouts.


3-4. Commission-based plans are risky, no matter how often you suspend the vendor.