core-sessiongiftmessagemagento-1
Can any one help me why am not able to set a magento session variable with the following code.
Mage::getSingleton('core/session')->setGiftMessage("<script type='text/javascript'>jQuery('#gift_message').val();</script>");
If the above implementation is wrong then please tell me how can i get a value of a text area
<textarea id="gift_message" rows="2" cols="75" name="gift-message"></textarea>
and set that value in a magento session variable to use it later.
Many thanks in advance .
So, user can create as many key ==> value pair matching as they want.
For this I would recommend the "Array" frontend and backend models, which work similar to the tier price definition in products. You would create a matrix with 2 columns that can easily be transformed to a key=>value map if needed. With a little extension to the frontend model you can use dropdowns for the shipping method as well.
It is explained in detail here: http://www.integer-net.com/2015/03/17/how-to-create-tables-in-magento-system-configuration/
Preview
What you need
<backend_model>adminhtml/system_config_backend_serialized_array</backend_model>Mage_Adminhtml_Block_System_Config_Form_Field_Array_Abstract and overrides _prepareToRender() to define the columns.Mage_Core_Block_Html_Select to create a custom dropdown.Well, I found my problem:
Early Session Instantiation
Magento doesn’t know which area it’s handling until the preDispatch method. Therefore, Magento can’t instantiate its session object until the preDispatch method. However, there are Magento system events that fire before pre-dispatch. If a Magento client programmer attempts to use a session in one of these events, some weird stuff can happen.
http://alanstorm.com/magento_sessions_early
I changed it to observe controller_action_predispatch instead, dispatched after Magento instantiates the core/session singleton with the named area, and it is working fine now.
Best Answer
I assume that the value is sent through post as some controller.
Just add this in the controller that handles the request:
Later you should be able to get it like this:
or if you want to retrieve it and remove it from session use this