Magento – Ajax Request Session Messages

ajaxmessagessession

I have implemented the EasyAjax extension by Vladimir Fishchenko, which is an amazing extension that allows you to make ANY Magento request via Ajax. One problem I am having relates to session messages being stored on Ajax requests.

After executing an Ajax request, like adding a product to the cart for example, session messages that were set during that request appear on subsequent pages that implement the global_messages block. Typically since the page would refresh after adding to the cart, the session messages would be displayed as expected, however because this request is made with Ajax, the session messages are stored but not displayed until the user navigates to another page (by which time the message is a page late).

Is there a way to prevent messages from being stored in the session if the request is Ajax? I can check if a request is Ajax using Mage::getSingleton('easyAjax/core')->isEasyAjax(), but I am unsure of where to implement this.

Best Answer

Magento uses \Mage_Core_Model_Session_Abstract::addMessage to store all the messages.

All messages end up in \Mage_Core_Model_Message_Collection::$_messages.

To clear this container, just call \Mage_Core_Model_Message_Collection::clear. The problem here is, that all the session core/session, customer/session, etc. have their own containers, therefore to delete the messages, you need to clear them all.

But I think it should be enough to get rid of the core/session messages, which are set here: \Mage_Core_Block_Messages::_prepareLayout because these are the messages which are shown in global message block (at least I think so)

Related Solutions

Magento – Session messages not showing

Okay, so after even more digging online and consulting some Magento guides/courses, I've found out the problem myself, namely:

I had to add the messages block to my layout.xml, like so:

<reference name="content">
    <block type="core/messages" name="messages" as="messages"?>
    // rest of code here
</reference>

I had to edit my indexController, so it renders and loads the layout, including the messages (and do this earlier), like so:

public function indexAction()
{
    // rest of code here

    if (!$competitor) {
        $cSession->addError($this->__('The url is not correct, please check the url and try again.'));
        return $this->_redirect('competition/landingpage');
    }

    $this->loadLayout();
    $this->_initLayoutMessages('customer/session');
    $this->renderLayout();

    if ($postData) {
        try {
            Mage::getModel('competition/competitor')->saveCompetitor($postData);

            $competitor = Mage::getModel('competition/competitor')->loadByHash(Mage::helper('competition')->getHash());
            $cSession->addSuccess($this->__('Thanks for participating, your entry has been registered.'));
        } catch (Exception $e) {
            $cSession->addError($e->getMessage());
        }

        $this->_redirectReferer();
    }
}

So if anyone else bumps into a similar problem, hopefully this might help you.

Magento 2.3.2 Redis Session Error – Successfully Broke Lock Fix

Finally able to resolve this issue by changing below configurations for Redis:

break_after_frontend changed from 5 to 30
max_concurrency => changed from 6 to 25

break_after_frontend was the main culprit. Following error log helped to trace the issue.

[2019-11-26 09:51:32] main.INFO: ip-10-0-0-78|28852: Successfully broke lock for ID sess_ebfc12b22fa8c8e1fb81dca122fcdda6 after 5.01422 seconds (10 attempts). Lock: 12
Last request of broken lock: POST pp-www.revivermx.com/rest/default/V1/carts/mine/payment-information /customer/section/load/?sections=messages&force_new_section_timestamp=true&_=1574761818952 [] []
[2019-11-26 09:51:37] main.WARNING: ip-10-0-0-78|28670: Did not write session for ID ebfc12b22fa8c8e1fb81dca122fcdda6: another process took the lock. /rest/default/V1/carts/mine/payment-information [] []

Best Answer

Related Solutions

Magento – Session messages not showing

Magento 2.3.2 Redis Session Error – Successfully Broke Lock Fix

Related Topic