Bring back websites-column

[kanduvisla]

Why is the websites-column removed? I'm currently running into an issue where I have 3 websites with 12 languages each. There is one website with all products, and 2 websites with a sub-set of products.

I try to use the websites-column, but it does nothing (as expected when a feature is obsolete).

So I try to populate the store-column with a comma-separated list of either 12, 24 or 36 values (12 languages for each website). But still all the products get added to all 3 websites.

So I created a post-magmi-function where my SQL the database to set the correct website ID's. This works, but as soon as magmi runs an update or something, store gets defaulted back to 'admin' and all websites are included again.

So I was wondering, is this a bug or a feature? Because I've been trying for a couple of hours now how to setup my CSV so a product gets imported in website A and B, but not in C.

What was the main reason for obsoleting the websites-column anyway?

[dweeves]

Hi,
Websites column is back in the git version. The doc is not "up to date" , but you may use the websites column & it should be taken into account.

[aingham]

Hi Dweeves,

Is the git version you're referring to here 0.7.19? I'm using 0.7.18 and 'website' column seems to be ignored. I'm finding problems using the store field to control which website a product is linked to: if you specify a store view code on product insertion then that works fine. However, if you then do an update using exactly the same csv record, then the fact that you've specified the store view code in the update will mean that you are now just overriding the product's attributes for that specific store view.

it would be preferable to be able to specify 'admin' as store view code and 'websites' as 'website1', so that you can use the same import file (and Magmi profile) for insertions and updates.

I hope I've explained that ok! Many thanks for this fantastic project.

Andy