MageGyverIf you have Xdebug installed on your local development machine, you might experience the following error when running Magento:
Fatal error: Maximum function nesting level of ‘256’ reached, aborting!
(instead of 256, the reported nesting level might be different)
So you’ve got an idea for an amazing new Magento 2 module and want to start coding right away. But before you can start you have to set up a Magento installation. And when you’re done, you probably want to test your module in other Magento installations with different versions.
m2devbox can help you with two things:
Today Magento has released the new Magento 2.4.2 version along with security updates for the 2.4.1 and 2.3.6 branches. The newly released versions affect both the Open Source and Commerce editions and have the version numbers:
When installing a fresh instance of Magento 2 you may get one of the following error messages:
Code language: plaintext (plaintext)[PDOException] SQLSTATE[42S02]: Base table or view not found: 1146 Table 'magento.store_website' doesn't exist
That’s weird, you say? Of course the table store_website doesn’t exist yet, because you were just trying to install Magento. So, where does that exception come from?
An overview of the latest Magento 2 versions, complete with release notes and security bulletins. As soon as there is a new version released by Magento, we will review and update this list accordingly.
When you’re running Magento 2 inside a Docker container (for example for local development) and you’re using a non-standard TLS port (or SSL port) like 44333, then your back-end adminhtml route will trigger a 404 error.
To save a few bits of data you don’t have to create a specialized entity each time. Magento 2, just like its predecessor Magento 1, offers Flag models. Flag models implement a small key-value store inside the Magento database.
In Magento 1 you could use the Flag model directly. For Magento 2, we have to create a class that extends the framework Flag class so we are able to set the correct FlagCode.