Magento

Hi all,

I was working with importing some products and to my surprise found that none of them were queried on the search in the front end. A little investigation revealed that no records had been inserted into ’catalog_product_website‘ table.

I tried creating a product manually and observed that there is a records in this table. So exported this record and imported by changing the SKU and product name alone. But found that there are no records created in catalog_product_website table. Is this a known issue? I wonder because this is pretty basic and someone should have faced this by now.

@srinigenie: during the import, which store did you select in the profile wizard?
Did you have “store” column in your import file? If yes, what values did you have in this column?

yes .... I tried with “admin” ..it didnt work, then tried with “default” ...still didnt work and then finally with “base” and no luck either :(

I should have done this earlier. ok… better late than never ...listing import file contents which imports one product...(unable to attach in the forum for some strange reason)…

And know what found someonelse facing the same issue
http://www.magentocommerce.com/boards/viewthread/4837/

I same issue.
partially solve problem…
in file Mage/Catalog/Model/Convert/Adapter/Product.php change in line 266 before: $product->save(); insert

Yes, the current dataflow importer doesn’t save the web site ID properly.  One solution is to create 2 website views, then when you are editing your products you can select which web site the product belongs to.  Strange how the Web site can only be edited if there are multiple store views present.

The heirachy should go

Site -> Store -> View

So even if you specify the “store” correctly, the site doesn’t get saved.

I’ve have the same issue. In order to make a single product visibile in frontend I need to clik on “edit” and save it (even with no really editing the record)

this solve my problem !

in file Mage/Catalog/Model/Convert/Adapter/Product.php change in line 266 before: $product->save(); insert

if (isset($row[’row’][’store’])) {
$storeId = Mage::app()->getStore($row[’row’][’store’])->getId();
} else {
$storeId = Mage::registry(’current_convert_profile’)->getStoreId();
}
if ($storeId) {
$product->setWebsiteIds(array($storeId));
}

PS: You have to delete and re-import all the product, otherwise you have to do those by hand !

It works !

Have logged a bug for this. Please track
http://www.magentocommerce.com/bug-tracking/issue?issue=1502

all my simple product were imported well… I now have this error when I am trying to view my Configurable Product on the frontend:

Error 500 - Internal server error
An internal server error has occured!
Please try again later.

In addition to this, any image paths in my import file are not represented in the database. I manually added records in catalog_product_website, then had to add records to catalog_product_entity_media_gallery and catalog_product_entity_media_gallery_value so that my images showed up in the admin panel for product management on the images tab.

Are there plans to modify this so that image paths are added to the tables mentioned?

Thanks…

Jason
webdevology.com

jeanlucb - 25 March 2008 09:28 AM

It works !

Yes, it works. Thanks for sharing!

cibernoid,

Can you do me a favor and import 25 Simple Products, and try to make a Configurable Product with them with over 20 Associated Products ?

For me, as soon as I add more than 20, on my frontend, this product gives me a 500 Internal Server Error.

I can send you my csv if you don’t want to create one.

Thank you,

Jean-Luc B.

Jean-Luc,
I’ve created a configurable product with 30 associated products without error.

Although I just get “Internal Server Error” when I import an huge csv file with 3000+ items. It only imports first 90 items.

that’s weird then what I am getting…

I am also importing small CSV with only 40 items MAX each…

I don’t know why :@

@jeanlucb --- strange ...didnt you notice that the bug you logged for the issue has been picked up by Magento team for resolution
http://www.magentocommerce.com/bug-tracking/issue?issue=1503