Don't know why, but I kind of get the feeling that the concept of open source *community* is not fully understood...
The error messages/problems won't fix themselves and probably will go undiscussed/undiscovered for quite a while if 1) everyone follows suit with dumping the "garbage" and 2) not providing the log files to potentially allow correction of the issue(s). Sure the issue could still be on either side (the code or the server), but one will never know if the information is not shared. I had thought that my previous description of the origin of this code section would encourage discussion rather than just ignoring what is going on.
All that aside, the query suggested won't do what is desired or thought unless that "simple" line is to get intrepretted correctly based on what is provided.
The status of a category is in the categories table. The status of a product is in the products table. A category's status condition is or can be independent of the product. Adjusting the product's condition based on the category being modified potentially has some nuances as a product can have a category as its master category or it can be linked to the category with some other category being the master. In either case, changing the status of the product changes it in all locations. If the desire is to "hide" a product from a specific category but not everywhere, then the products_to_categories table may need adjustment to remove the link from the product to that category or to change the master category as part of that.
Just understand that the overall desire is always to resolve issues and not ignore them. The easiest thing to do on your side is to provide back logs (with the admin directory obscured) so that at least if there is something amiss with the code it can be corrected whether you adopt the changes or not.



Reply With Quote
