An Interesting Challenge for folks Using Magento 1 and PHP 7 Magento 1 doesn’t officially support PHP 7, but the changes needed to Magento’s core code to get this working aren’t too strenuous, and even third party extensions can be patched/modified to make this work. Whatever interesting here is the de-facto standard [...]
astormThis one’s a follow up to my Magento 2: Understanding the Web API Architecture post. In that post I gloss over Magento’s oAuth implementation, and what I did say got several details wrong. This article aims to fix that. To understand Magento’s oAuth features, you need to understand the (related) integrations feature. To [...]
astormMagento 2 Feature Request: Simple, Standard, Seamless, PHP Install Option My thoughts on the state of Magento 2 from a product point of view, with a focus on why Magento needs to to shore up some PHP basics. Related to my open letter.
astormAnother high level first pass at an important topic for Magento 2 developers. Corrections and clarifications are more than welcome. Magento 2, like Magento 1, has a “web” API. This has nothing to do with the @api notation on classes, methods, and interfaces. The Web API is a way for programmers to programmatically interact [...]
astormMagento Travis Build Starter Travis is a popular, hosted system for automatically creating test environments for open source projects hosted on a GitHub. The word automatic can be a little misleading though – Travis hooks up to the GitHub API, handles spawning new virtual machines (presumably at AWS/EC2), and has a simple domain [...]
astormRemoving a Block from Magento 2 Layouts I’ve dug into the Magento 2 layout enough to discover that On the PHP level, there are methods for removing/unsetting a block from the layout That these methods are not exposed via the Layout DSL
astormIf you’ve read previous articles on the subject, you know that every URL in Magento 2 corresponds to a single controller file, and each controller file has a single execute method. This execute method is responsible for returning a “result” object (i.e. an object that implements the [...]
astormThanks to Magento 2’s MVVM approach the traditional responsibilities of a controller object have been pushed into the “view model” layer (i.e. a block’s _prepareLayout method). The main job a controller performs in Magento 2 is to Determine what sort of response is needed (HTML page, JSON, Redirect) Create an [...]
astorm