Hello and good day to all the members of this great community. I'm still new in PHP and especially in Magento.
I'm not posting, waiting for answers, and leaving without replying back. This is a learning process. I hope to get a great support from all of you.
I have a product. I did create custom option for the product, that is an attribute named "a_size". The attribute has value of S, M and L. Each of the value has quantity.
In the single product view, I would like to call all the available size. That is the size (S, M, or L) that has quantity more than 0. I just want to show the available size, not how much the size left.
Can anybody guide me? I'm using Magento 1.7.x and as far for this 2 weeks, I did try pretty many of suggested answers from the community thru the search function.
The replies will be much appreciated. Thank you.
There are a few things to try.
Firstly check that when you set up your new attribute in the Magento Admin (Catalog->Attributes->Manage Attribute) that in the Frontend Properties box you have set Visible on Product View Page on Front-end to yes.
To get size values I use this code:
$cabac_sizeAttribute = $_product->getAttributeText("a_size");
but I have other code for getting attribute values that goes like this:
$_product_helper = Mage::helper('catalog/output');
$temp = $_product_helper->productAttribute($_product, $_product->getASize(), 'a_size');
I think it is related to the type of attribute: text, dropdown, multiselect etc so try both and see how you get on. But really the function productAttribute() is just applying formatting. You can read the function in the file app/core/Mage/Catalog/Helper/Output.php
Also, I wonder, if you have set up a configurable product and you are on the product view page then you will be viewing the configurable product. That product won't have an a_size value: you are trying to access the a_size attribute of the simple products that make up the configurable product, yes? Everything I wrote above is (I think) correct but to get the attribute of the simple products that are part of a configured product you should study the code in the function getJsonConfig() of the file app/core/Mage/Catalog/Block/Product/View/Type/Configurable.php
And in particular to these lines:
//file: file app/core/Mage/Catalog/Block/Product/View/Type/Configurable.php
//class: Mage_Catalog_Block_Product_View_Type_Configurable
//function: getJsonConfig()
foreach ($this->getAllowProducts() as $product) {
$productId = $product->getId();
foreach ($this->getAllowAttributes() as $attribute) {
$productAttribute = $attribute->getProductAttribute();
$productAttributeId = $productAttribute->getId();
$attributeValue = $product->getData($productAttribute->getAttributeCode());
Being careful about variable naming: $product is local here, I suggest changing it, and about $this - but if you are in a .phtml of the product view for configurables then I think your $this is already Mage_Catalog_Block_Product_View_Type_Configurable
Welcome to Magento coding. You are doing well; it is a long but rewarding path. (hints: local.xml is your vital friend and so is Alan Storm if you haven't come across his content yet.)
[Additionally, (welcome to Magento) I think you are trying to say eg S and L are out of stock and M is in stock but actually the function getAllowProducts() will disallow a product with zero stock and exclude it from the returned object. You will need to use
$allProducts = $this->getProduct()->getTypeInstance(true)
->getUsedProducts(null, $this->getProduct());
(taken from function getAllowProducts() in file app/core/Mage/Catalog/Block/Product/View/Type/Configurable.php)
and then, if needed, check that each product is allowed to be shown eg status=ENABLED, and then check its stock level...
]
Malachy.
If you want to get the values of your drop down attribute use the following code
$_product->getASize();
and initially load the product object
Related
I'm developing a script (external to Magento, not a module) which aims to output a text list of all available products, their prices and some other attributes. However, catalog price rules don't seem to be applied to product prices. If I use any of the following:
$_product->getPrice()
$_product->getFinalPrice()
I get the normal price (without rules being applied).
If I use:
$_product->getSpecialPrice()
I get null unless the product actually has a special price inserted in the product itself (i.e. if special price is not related with catalog rules).
I also tried
Mage::getModel('catalogrule/rule')->calcProductPriceRule($product,$product->getPrice())
as suggested in the answer given by Fabian Blechschmidt, but interestingly it returns the normal price only if the product is affected by any catalog rule, returning null otherwise.
There was a similar question in StackOverflow and Magento Forums some time ago, but the provided answer (which is to insert the code bellow) doesn't work for me (returned prices remain the same).
Mage::app()->loadAreaPart(Mage_Core_Model_App_Area::AREA_FRONTEND,Mage_Core_Model_App_Area::PART_EVENTS);
Does anybody have an idea of how to achieve this?
I'm using Magento 1.6.2.0.
Thanks in advance.
Thanks to you, I found a new site:
http://www.catgento.com/magento-useful-functions-cheatsheet/
And they mentioned:
Mage::getModel('catalogrule/rule')->calcProductPriceRule($product,$product->getPrice())
HTH
As catalog price rules heavily depend on time, store and visiting customer, you need to set those parameters when you want to retrieve the product final price with it's price rules applied.
So, in your case, make sure that provided product is passed with the desired store and customer group id, which can be set as:
Mage::getModel('catalogrule/rule')->calcProductPriceRule($product->setStoreId('STORE_ID')->setCustomerGroupId('CUSTOMER_GROUP_ID'),$product->getPrice())
I discovered the problem. The discounted prices display Ok in the store frontend. The problem was that I was developing a script "external" to Magento (thus not a Magento module), something like:
<?php
set_time_limit(0);
ignore_user_abort();
error_reporting(E_ALL^E_NOTICE);
header("Content-Type: text/plain; charset=utf-8");
require_once "app/Mage.php";
// Get default store code
$default_store = Mage::app()->getStore();
...
For everything to work properly it seems that one must follow the proper Magento bootstrap, and develop everything as a module. My script was so simple that I thought it wouldn't be necessary to code a complete module. In other words, everything in Magento should really be a module.
Concluding, using the module approach, all the methods work as expected:
$_product->getPrice()
$_product->getFinalPrice()
$_product->getSpecialPrice()
Thank you all for your input.
This helped me in this issue: http://www.magentocommerce.com/boards/viewthread/176883/
. Jernej's solution seems plausible, but it does not handle rules that Overwrite other rules by using 'stop processing' and therefore can apply more than one rule.
$original_price = $_product->getPrice();
$store_id = 1; // Use the default store
$discounted_price = Mage::getResourceModel('catalogrule/rule')->getRulePrice(
Mage::app()->getLocale()->storeTimeStamp($store_id),
Mage::app()->getStore($store_id)->getWebsiteId(),
Mage::getSingleton('customer/session')->getCustomerGroupId(),
$_product->getId());
// if the product isn't discounted then default back to the original price
if ($discounted_price===false) {
$discounted_price=$original_price;
}
today I'm fighting with Magento again :) and I found a difference between
$product = Mage::getModel('catalog/product')->loadByAttribute('sku', $product_sku);
and
$product = Mage::getModel('catalog/product')->load($product_id);
Can anyone exaplain me a difference between these two approaches? I found that when I'm loading a product by sku then when I 'try to re-save it with changed data then I get error exception 'Varien_Exception' with message 'Invalid method Varien_Object::save in app\code\core\Mage\CatalogInventory\Model\Observer.php(153): Varien_Object->__call('save', Array) that's true because once you try to load by sku then another observer sets product's stock item as Varien_Object, that looks like pitfall or I just dont understand it enough, but
I do daily Magento development from its beginnig so I know a lot about system and this is new for me. Thanks in advance, Jaro.
Interesting. While both methods will net you a single product model instance with fully loaded EAV data (provided the third parameter of loadByAttribute() is not passed or is *), the observers which add stock-related data are different for products vs. product collections, yet both stock information objects are added to the product data key "stock_item". It's debatable, but this feels like a bug. I would think that Mage_CatalogInventory_Model_Observer::saveInventoryData() or Mage_CatalogInventory_Model_Observer::_prepareItemForSave() would handle this.
You could resolve this issue by setting the product stock item fully on your product instance using the stock_item object.
loadByAttribute is a serious misnomer in my opinion because it doesn't actually trigger a load(); rather it uses getResourceCollection():
public function loadByAttribute($attribute, $value, $additionalAttributes = '*')
{
$collection = $this->getResourceCollection()
->addAttributeToSelect($additionalAttributes)
->addAttributeToFilter($attribute, $value)
->setPage(1,1);
Because it doesn't trigger the observer events associated with load() it means the resulting product object doesn't include the full set of product data you might want. In my case I needed the "description" attribute and it wasn't included.
There are several ways to resolve this:
Use a different method to load by SKU:
$product = Mage::getModel("catalog/product");
$product->load($product->getIdBySku("whatever"));
Force the desired attribute data to be included in the default product resource data by visiting Magento Admin > Catalog > Attributes > Edit attribute > "Used in Product Listing" = "Yes" and then reindexing. You should then be able to use the attribute data (in the frontend, at least) using loadByAttribute().
See also https://magento.stackexchange.com/a/197286/18855
We have added a "yes/no" product attribute labelled: "Allow this product to have coupons applied?" with a default value of "yes".
The reason for this is, that we never want the sales team to give discounts on certain core products out of the thousands available.
We could add these products as SKU's to every one of the thousand coupons created, but that can then be changed by accident, or improperly listed by the sales team creating the coupons.
We therefore have asked them to add this rule to their new coupons, to exclude these products. We also updated all the other coupons via code, to include this rule.
When I test the rule on Magento 1.5, Community edition, it does exactly the opposite of what the condition says.
When I test the same rule on our other Enterprise solution (magento 1.9), it actually does what it is supposed to.
When I have one product in the shopping cart, being a product that has this attribute set to "No", and I apply a coupon code, it accepts the coupon code. On the other system (Enterprise) it rejects it, as it should.
Has anyone else came across this?
UPDATE:
Ok, this just got more interesting.
When I stepped through the Rule classes, the product was passed, but the product attribute did not come through. The scope is set to website, and I did check that is it saved under that scope in the back end.
This is really weird...
On the enterprise system, the product attribute, with the same configuration and data is coming through.
I even tried to not have double negatives, with another new attribute, to make sure.
Running against the following rule, the coupon gets refused: "Coupon code is not valid."
This is correct, as the product is set as "Can use coupon? = No".
But the problem is that I do not want to do a check against all the other products, but rather against, the few that has been marked as "No".
This is not going to work for us anyway, as we don't want to apply a coupon if there is any product in the cart that has a value of "No" for the attribute "Can use coupon?".
This is a double negative rule, no matter which way you look at it.
I stepped through /app/code/core/Mage/SalesRule/Model/Rule/Condition/Product.php through the validate() function, when adding the product a second time, and the data shows up in the attributes, but when I go and re-apply the coupon, and step through this function again, those values are gone. this is weird.
When adding new product to shopping cart:
When Re-applying Coupon Code:
Where the heck did description and some of the other attributes disappear to?
UPDATE NOTE I am getting a bit closer.
When I change the following validate() function in "/app/code/core/Mage/SalesRule/Model/Rule/Condition/Product.php" from the following:
public function validate(Varien_Object $object)
{
$product = false;
if ($object->getProduct() instanceof Mage_Catalog_Model_Product) {
$product = $object->getProduct();
} else {
$product = Mage::getModel('catalog/product')
->load($object->getProductId());
}
$product
->setQuoteItemQty($object->getQty())
->setQuoteItemPrice($object->getPrice())
->setQuoteItemRowTotal($object->getBaseRowTotal());
return parent::validate($product);
}
To This:
public function validate(Varien_Object $object)
{
$product = false;
$product = Mage::getModel('catalog/product')
->load($object->getProductId());
$product
->setQuoteItemQty($object->getQty())
->setQuoteItemPrice($object->getPrice())
->setQuoteItemRowTotal($object->getBaseRowTotal());
return parent::validate($product);
}
It then works fine!
Found out the actual problem, and here is what I did for the solution:
The following bit gets the product data for the Shopping Cart Price Rules:
if ($object->getProduct() instanceof Mage_Catalog_Model_Product) {
$product = $object->getProduct();
} else {
$product = Mage::getModel('catalog/product')
->load($object->getProductId());
}
The culprit is this line: $product = $object->getProduct();
That calls a line from the "Quote/Item/Abstract.php" being: $product = $this->_getData('product');
It will simply get the cached data from the system, and that consists of a selection like this:
$productCollection = Mage::getModel('catalog/product')->getCollection()
->setStoreId($this->getStoreId())
->addIdFilter($this->_productIds)
->addAttributeToSelect(Mage::getSingleton('sales/quote_config')->getProductAttributes())
->addOptionsToResult()
->addStoreFilter()
->addUrlRewrite()
->addTierPriceData();
The problem with this is, the following line:
->addAttributeToSelect(Mage::getSingleton('sales/quote_config')->getProductAttributes())
That will get only the attributes defined in the Config.xml for quote items being:
<quote>
<item>
<product_attributes>
<sku/>
<type_id/>
<name/>
<status/>
<visibility/>
<price/>
<weight/>
<url_path/>
<url_key/>
<thumbnail/>
<small_image/>
<tax_class_id/>
<special_from_date/>
<special_to_date/>
<special_price/>
<cost/>
<is_recurring/><!-- for totals calculation, placing and processing order -->
<recurring_profile/><!-- for placing order -->
<gift_message_available/>
</product_attributes>
</item>
</quote>
This will not get the new custom attribute that I want, and the rule will never be able to compare the data with the expected value properly.
Adding the following xml to my custom sales module config.xml, which have some observers in it for other stuff, fixes the problem.
<sales>
<quote>
<item>
<product_attributes>
<exclude_from_coupon/>
</product_attributes>
</item>
</quote>
</sales>
Then it all works!
Why did it work in the enterprise version of magento
Don't really know. I think Enterprise is maybe looking for settings on the actual Attribute definition, and includes it to the list of Attributes to collect, and then return the data for it, my guess. I will research that, and update it here to the post.
At least I now know what the real issue is, and why the Shopping Cart Rule Condition (coupon) failed.
Thanks to all those who helped me with some good questions and suggestions.
Another day wiser with magento...
I tested this with Magento CE 1.5.1.0 and cannot reproduce your problem. For me, it works.
Please recheck the following for your CE installation:
You set the default attribute value to "yes"
You did reindex the indexes as required.
You edited one test product and explicitly set the attribute value to "no".
(Just to be sure) You updated the caches.
You set the shopping cart price rule exactly as described above (apply if conditions are FALSE and allow is set to NO).
If you don't have any custom code interfering, this should work. It does in the default installation.
If it still doesn't work:
What happens if you rephrase the condition to only apply if all conditions are TRUE and allow is set to TRUE (does remove the double negative which is more complicated)?
Please post screenshots of the backend forms for shopping cart price rule, product attribute and the product.
Let's ask the question clearly before entering into the details:
Is there a way of hard deleting an attribute value from a product?
By hard I mean, removing the row from the database and not only setting the value to null or empty.
Now, the details:
I'm currently confronted to a problem on Magento.
Many product in my store have user defined attributes that are not related to the product. For example, let's say we have a bag product, among other products like t-shirts,dresses,pants,etc.:
Our bag product has only configurable 1 attribute: color.
Our T-Shirt product has 2 configurable attributes: color and tshirt_size.
Our Dress product has 2 configurable attributes: color and dress_size
My current problem is that when I retrieve my Bag product from the database, the attributes stored in my product are: color, tshirt_size and dress_size.
I suspect that it is because on our store you can change the attribute set of a product (thanks to the FlagBit ChangeAttributeSet community extension).
I think that the bag product has been created with a specific attribute set, then someone changed the attribute set to another, and another again. That would have lead the product to get ALL the attributes from ALL the attribute sets it has been changed to. But that's just a though, and it could be another reason. I'm actually currently not looking for the specific reason that led my product to have unrelated attributes.
I today want to reset my products. By reset I mean removing the attributes unrelated to my product. In the case of my bag, that means removing the tshirt_size and dress_size attributes. And by removing I mean deleting forever these attributes from the object.
My problem is that, I can't find how to do it. I tried setting the attributes to NULL and saving the product, but when I query again the product, I still get the attribute in the datas, with a null value. I don't want the attribute value to be null, I want the attribute to not exist.
Here is a sample of code that explains a bit what I tried:
$product = Mage::getModel('catalog/product')->load(1234); //Let's assume that my bag product ID is 1234
Mage::log($product->getData());
/* This last line dump all my products datas and contains among other things:
[...]=>...
[color]=>3
[tshirt_size]=>34
[dress_size]=>45
[...]=>...
*/
If I do a:
$product->setData('tshirt_size',null);
$product->setData('dress_size',null);
$product->save();
then again:
$product = Mage::getModel('catalog/product')->load(1234);
Mage::log($product->getData());
/* I get:
[...]=>...
[color]=>3
[tshirt_size]=>null
[dress_size]=>null
[...]=>...
*/
I don't want that. I want:
/*
[...]=>...
[color]=>3
[...]=>...
*/
The fact that I still have the entries in my array mean that the actual rows in the database are not deleted. I want the rows to be deleted.
Even more frustrating, when I do a:
$product->getAttributes();
It returns me all the attributes that can be set to my product without the unrelated attributes -which makes sense because the unrelated attributes are not in the attribute set of my product.
So, again, the question is:
Is there a way of hard deleting an attribute value from a product?
By hard I mean, removing the row from the database and not only setting the value to null or empty.
Thanks for your help!
Hugues.
FYI: I'm using Magento 1.6.1.0 (but it does not really change anything)
I finally had to tackle this, and although #vBuck was close, I always was able to query the old data after the switch in the attribute set and if I switched back I would see the old data when it shouldn't have been there. Today, I have the same need to ensure the random data is removed. Here is how I approached this topic.
In order to programmatically delete attributes when you switch from one set to another you must first look at all the entries for the new set, then get a list of all attributes, check against that list and (this is the important part) remove it from the correct entity table. For example, I want to get rid of a value of 500 GB that is in the sample Magento data when I switch Western Digital 500GB HD - 7200RPM from Hard Drive to Shoes. In order to do that I must remove the entry in the catalog_product_entity_text table it's stored at. This means that I must find that entry where it's equal to the product id and then delete it from it's entity type table.
I was able to do this, and was not able to find the stray data after. This was confirmed by both a DB search and switching back to the old attribute set and looking for the data. you can find it all here
https://gist.github.com/jeremyBass/6581038#file-attribute-clean-switch-md
TESTED in CE 1.7.0.2, 1.8.0.0
So I too would love to have the programmatic answer, but I don't have the time to do it. But this is what I can provide to this chain. You see the desired resulting action happening when you try to remove an attribute by its self from the admin.
Steps:
make sure the attr set has the attr in it's set.
update all products with that attr set to have the attr needing deletion as null.
remove the the attr from the set
Seems when I don't clear all attrs before removal of attr from the set, the result is for the app to leave the rows there. Maybe for safety, I don't know as I have not dived in. What I can tell with as little as I have looked in this it’s that if you don't clear the values before attr removal from the set, when you set the attr to null, the attr remains.
So, then the programmatic solutions will need to follow that pattern. If I get time I'll write it, but I have like 15 other tasks in the queue right now.
Ok, I found it finally, 15 minutes after asking the question (and spending few hours trying to solve it)
Here is the answer:
$product = Mage::getModel('catalog/product')->load(1234); //Let's assume that my bag product ID is 1234
$product->setData('unwanted_attribute',null);
$resource = $product->getResource();
$resource->saveAttribute($product,'unwanted_attribute');
Edit: This doesn't work. If you re-save the product later by doing a $product->save(), all the attributes reappear.
Looks like this is an old post, but I too was looking for an answer here, and I think I'm onto a solution.
To solve this, I had to work directly with the product resource's write adapter:
$product->getResource()->getWriteConnection()
to delete the attribute values from the table.
I got clues on how to do this after digging through some code. See Mage_Catalog_Model_Resource_Eav_Mysql4_Abstract::_saveAttributeValue:
$write = $this->_getWriteAdapter();
$storeId = Mage::app()->getStore($object->getStoreId())->getId();
$table = $attribute->getBackend()->getTable();
/**
* If we work in single store mode all values should be saved just
* for default store id
* In this case we clear all not default values
*/
if (Mage::app()->isSingleStoreMode()) {
$storeId = $this->getDefaultStoreId();
$write->delete($table, join(' AND ', array(
$write->quoteInto('attribute_id=?', $attribute->getAttributeId()),
$write->quoteInto('entity_id=?', $object->getEntityId()),
$write->quoteInto('store_id<>?', $storeId)
)));
}
By using this code in a loop through $product->getAttributes() before changing the attribute set, you are able to "unlink" the values from the attributes of the product without destroying the attributes themselves. Then you can change the attribute set (as done in Flagbit's extension) safely, not leaving behind dead data.
Using the above code, here's a demonstration that I've written to prove my theory:
$product=Mage::getModel('catalog/product')->load(MY_TARGET_PRODUCT_ID);
$write=$product->getResource()->getWriteConnection();
foreach($product->getAttributes() as $attribute) {
if($attribute->getId()==MY_TARGET_ATTRIBUTE_ID) {
$write->delete(
$attribute->getBackend()->getTable(),
join(' AND ', array(
$write->quoteInto('attribute_id=?',$attribute->getAttributeId()),
$write->quoteInto('entity_id=?',$product->getId())
))
);
}
}
In this example, I'm looking for a specific attribute to clear from the product, but you can remove the IF conditional to delete every attached value.
I haven't fully tested this, but so far it seems alright. I'm running Magento 1.4, by the way. Hope it helps someone!
UPDATE:
Looks like the above is only half correct. You'll still have to be careful not to clear certain attributes that might render the product dead (such as the name, mode, status, and others). So in my case, it looks like I'll have to compare with the default attribute set before removing.
ANOTHER UPDATE:
With the help of this SO post: https://stackoverflow.com/a/8500506/1442685
I was able to compare all attributes linked to a product and delete only the non-default values. This way, when changing sets, I can ensure that basic information about the product is not lost. Check out my Gist for the two classes which make it all happen:
https://gist.github.com/vbuck/5911170
You should be able to unset the value like either of these:
$product->unsetData('unwanted_attribute')
->save();
$product->unsUnwantedAttribute()
->save();
you need to go to admin>>catalog>>attributes>>manage attribute sets
if your trying to manage your product catalog you should first think of your attributes (separate to your product), then your sets(again not actually part of your products).
after you have properly established your attributes and sets (of attributes) you can apply them to products with values for each attribute.
or maybe you prefer this kinda thing?
class Mage_catalog_Model_Product_Attribute_Set_Api extends Mage_Api_Model_Resource_Abstract
{
{
/**
* Retrieve attribute set list
*
* #return array
*/
public function items()
{
$entityType = Mage::getModel('catalog/product')->getResource()->getEntityType();
$collection = Mage::getResourceModel('eav/entity_attribute_set_collection')
->setEntityTypeFilter($entityType->getId());
$result = array();
foreach ($collection as $attributeSet) {
$result[] = array(
'set_id' => $attributeSet->getId(),
'name' => $attributeSet->getAttributeSetName()
);
}
return $result;
}
} // Class Mage_Catalog_Model_Product_Attribute_Set_Api End
Once you have associated an attribute set to a product there is no way to change attribute set or remove that attribute set.
The way out is to export product and then modify sheet and import.
This link also explains :
https://collaborate.magento.com/magento/topics/how_do_i_change_product_attribute_set
We're building a custom Ajax product search and are returning attribute options, from associated simple products for a configurable product, that are available to purchase.
In this case, the attribute is 'gender', so to illustrate, I'm trying to show, in the search, whether we have 'Guys, Girls, Kids' in stock, or just 'Guys'.
It's the EXACT same logic as product options on a product page, but it's global.
I have it working with this code:
$attributeOptions = false;
$jsonConfig = $this->getLayout()->createBlock('Mage_Catalog_Block_Product_View_Type_Configurable')->setProduct($_product)->getJsonConfig();
$jsonConfigDecode = Mage::helper('core')->jsonDecode($jsonConfig);
$genderAttributes = reset($jsonConfigDecode['attributes']);
$attributeOptions = $genderAttributes['options'];
But it's taking up to 1 second per product result so can't be used in our Ajax implementation, which may have dozens of results.
I'm wondering if there's a better/faster way. Perhaps, I'm bypassing flat catalog, which we're using by doing this?
Thanks for your help!
Wilson
Better way.
$product->getTypeInstance()->getConfigurableAttributesAsArray()