{"id":2696,"date":"2024-12-31T20:26:01","date_gmt":"2024-12-31T20:26:01","guid":{"rendered":"https:\/\/meetanshi.com\/blog\/solved-fatal-error-uncaught-error-call-to-a-member-function-getsectionnames-after-upgrading-magento-2\/"},"modified":"2025-09-01T10:55:57","modified_gmt":"2025-09-01T05:25:57","slug":"uncaught-error-call-to-a-member-function-getsectionnames","status":"publish","type":"post","link":"https:\/\/meetanshi.com\/blog\/uncaught-error-call-to-a-member-function-getsectionnames\/","title":{"rendered":"Solved: Fatal Error: Uncaught Error: Call to a Member Function getSectionNames() After Upgrading Magento 2"},"content":{"rendered":"\n

Facing a\u00a0\u201cFatal error: Uncaught Error: Call to a member function getSectionNames()\u201d<\/strong><\/em>\u00a0after\u00a0Magento 2 upgrade<\/a>? Read this blog post to find the complete solution.<\/p>\n\n\n\n

Adobe<\/a> releases several upgrades throughout the year, fixing various issues and adding new features to the Magento platform. Major upgrades are released every six-twelve months, with minor upgrades and patches in between. These updates introduce new features and functionalities, known bug fixes, and security improvements.<\/p>\n\n\n\n

Sometimes, these new feature introductions may conflict with the existing customizations in the store and produce errors. One such error after upgrading Magento version is the \u201cFatal error: Uncaught Error: Call to a member function getSectionNames()\u201d<\/p>\n\n\n\n

I recently faced the same issue while upgrading a client\u2019s store from Magento 2.3.3 to the 2.4.5 version. On further investigation, I found the root cause of the problem.<\/p>\n\n\n\n

Let\u2019s understand the cause & the method to solve the issue.<\/p>\n\n\n\n

Where is the Problem?<\/h2>\n\n\n\n

Magento 2.3.4 release<\/a> has introduced a new argument named sectionNamesProvider<\/code>tag for the frontend blocks. This means Magento assumes a sectionNamesProvider argument for every instance of the block. If you use a custom theme or have overridden the default.xml, you may encounter the \u2018Fatal error: Uncaught Error: Call to a member function getSectionNames()\u2019 error.<\/p>\n\n\n\n

The solution to \u2018Fatal error: Uncaught Error: Call to a member function getSectionNames()\u2019<\/h2>\n\n\n\n

The solution to getting rid of the error in Magento 2 is to find the XML file that is being called by the custom PHTML file and add the argument tag.<\/p>\n\n\n\n

For example, in my case, the error read:<\/p>\n\n\n\n

Fatal error: Uncaught Error: Call to a member function getSectionNames() on \/vendor\/magento\/module-customer\/view\/frontend\/templates\/js\/section-config.phtml:20<\/code><\/pre>\n\n\n\n
Therefore, the section-config.phml<\/code> file was causing the error here.<\/p>\n\n\n\n
Here, we need to find the XML file where this PHTML file is called and add the argument tag as per the default.xml<\/code> file<\/p>\n\n\n\n
<block name=\"customer.section.config\" class=\"Magento\\Customer\\Block\\SectionConfig\"\n               template=\"Magento_Customer::js\/section-config.phtml\">\n            <arguments>\n                <argument name=\"sectionNamesProvider\" xsi:type=\"object\">Magento\\Customer\\Block\\SectionNamesProvider<\/argument>\n            <\/arguments>\n        <\/block><\/pre>\n\n\n\n
and the problem will be solved!
Solution to a similar error:<\/strong><\/p>\n\n\n\n