http://www.magentocommerce.com/bug-tracking/ en MagentoCommerce Copyright {gmt_date format="%Y"} {gmt_date format="%Y-%m-%dT%H:%i:%s%Q"} http://www.magentocommerce.com/bug-tracking/issue?issue=4727 Posted: 2009-01-07 06:21:01
Category: Categories
Version: 1.2.0.1
Priority: urgent
Status: closed
Reported By: andreladocruz

Sirs,

When you remove on product from a category the date is deleted from catalog_category_product but not from catalog_category_product_index.

with that products are still showing in front end.

regards,

---

]]> #1 / Comment by mphillips

I am also experiencing this issue.]]> #2 / Comment by tbertz

+1 for that, this is pretty serious, you cant manage any products in any categories. This isn't something I would expect to escape testing for a stable release. Poor.]]> #3 / Comment by vinai-kung

As a workaround: removing products from the manage categories page works.]]> #4 / Comment by ddeppner

I've got the same problem.

The problem is in app/code/core/Mage/Catalog/Model/Resource/Eav/Mysql4/Product.php.

Function refreshIndex() has the correct code to remove values from the catalog_category_product_index table and re-add only the correct values. However, this code is commented out:

// $this->_getWriteAdapter()->delete(
// $this->getTable('catalog/category_product_index'),
// 'product_id='.$product->getId()
// );

Uncommenting that code seems to fix the problem--when products are saved from that point on, old values are removed before adding valid values to the index.

However, there is still the problem of there being hundreds of incorrect entries in that table.

The quickest way to sanitize the existing database without needing to write custom code (but you must do this after uncommenting the code listed above) is to export your product database and then reimport it. I just created an export profile for sku and category_ids and then reimported it, resulting in the refreshIndex() function being called on every SKU.]]> #5 / Comment by turbo1

Thanks for screwing up yet another upgrade Varien. I said it before, and I'll say it again. 1.2.0.x is a steaming pile of ****]]> #6 / Comment by magicker

thanks ddeppner

you saved my life]]> #7 / Comment by sumityadav

Yes, I also faced this problem today. Took a lot of time to debug:

What i was doing:
1) Moving the code from one category to another.
1.1) From the product edit mode.
1.2) From the category edit mode and unchecking the "Category Products"

Then Tried to disable the product and the product will still show up in frontend.

2) Added log to debug which query was the problem. Found the query below:
[code]
SELECT *
FROM `catalog_product_entity` AS `e`
INNER JOIN `catalog_category_product_index` AS `cat_index` ON cat_index.product_id = e.entity_id
AND cat_index.store_id = '1'
AND cat_index.category_id = '5'
AND cat_index.is_parent =1
LEFT JOIN `catalogrule_product_price` AS `_price_rule` ON _price_rule.product_id = e.entity_id
AND _price_rule.rule_date = '2009-01-21'
AND _price_rule.website_id = '1'
AND _price_rule.customer_group_id = '0'
WHERE (
cat_index.visibility
IN ( 2, 4 )
)
LIMIT 9
[/code]

Manually cleared the `catalog_category_product_index` table. Everything worked fine after that. I will test this further.

QUESTION:
Is there any RULE that checks for the ACTIVE/ENABLED products ?]]> #8 / Comment by elfling

blargle, what a pain in the arse]]> #9 / Comment by Magento Team

Hello andreladocruz,

This issue was fixed. The changes will be available in the next bugfix release.

Thank you.]]> #10 / Comment by keithabt

I have tried all of these solutions with no success. Im using version 1.1.6.

exporting the product db and then importing it seems to fix the problem until I re-save my FIRST category in the 'Manage Category' section in the Admin. If I have any other category selected, then click save, everything is fine. Its ONLY the first category re-save that adds products to this first category in error.

To fix that, I have to go to Manage Products and select the products category and re-save. It then removes the product from the incorrect category (In my case the first category, which is the only category that my products seem to be added to in error).

Im puzzled and a very disappointed that something this major has not been fixed!

Any help? Do I have to upgrade to fix this?

thanks]]> #11 / Comment by gunnar

I have fixed my Problem with the following SQL Statement:

DELETE c FROM catalog_category_product_index c LEFT OUTER JOIN catalog_category_product c1 ON c1.category_id=c.category_id AND
c1.product_id=c.product_id WHERE c1.product_id IS NULL

This Statement looks for entries in the catalog_category_product_index table, which aren't linked to an entry in the catalog_category_product Table. Thoes entries are the bad guys, which are destroying the order in your layered navigation.

works fine in my production environment.
bye, gunter]]> #12 / Comment by hank57

gunnar, you made my day!
Works perfectly, thanks a lot!]]> #13 / Comment by maheshfarswan

I've got the same problem with ver 1.2.0
so i Uprate to the newer version ver 1.2.0.3.
and still facing same problem..]]> #14 / Comment by logosol

THANK YOU GUNNAR AND DDEPPNER! Worked for me on 1.2.0.2]]> #15 / Comment by Joel Green

These PROBLEMS STILL exist...If I change anything on a product in the back end the front end DOES NOT reflect those changes...yeah and I should spend 8k on an enterprise version...LMAO]]> #16 / Comment by henriv

Do we know which version this was fixed? I have 1.2.1.2 and still has this issue.]]> #17 / Comment by Andy Morrill

I had this issue in magento 1.3.2.4 -- gunnar's fix seems to have fixed the problem -- varien -- please please fix problems like this when they are presented -- this is a HUGE problem.]]>