Here’s a fun pestle command I forgot about.

This command accepts a file path as a single argument, searches through the specified folder for anything that looks like a Magento controller file, and then displays that controller file’s execute method along with its relative file path.

Pipe the resulting output to a file or text editor, and you can quickly search through all Magento’s controller files. For example, today I forgot the syntax for adding a custom handle to a layout update XML file – but with magento2:search:search_controllers the syntax was and a “Ctrl-F handle” away.

Für die SCHRAMM Werkstätten GmbH hat netz98 ein E-Commerce-Projekt auf Magento-Basis realisiert, bei dem der Content die zentrale Rolle spielt. Denn bei SCHRAMM, einem Hersteller von Luxusbetten mit extrem hochwertigen Taschenfederkern-Matratzen, ist der Content auf www.schrammwerkstaetten.de letztlich wichtiger als der Onlineshop: Marketing vor Direktvertrieb. Darum hat netz98 die Magento 2 Community Edition kurzerhand zum richtigen

The post netz98 verwandelt Magento für SCHRAMM Werkstätten in ein CMS appeared first on Regalsprecher.

Magento uses notification messages to improve user experience. You can simply add any message using the Message Manager to notify users whether the result of an action is successful or not.

In this blog post we will cover one type of the notifications – Admin System Messages. This type of notifications will be shown in a pop-up block and will be present in the admin panel as a reminder for an admin user until a special condition is met. These notifications can vary from messages about invalidated indexes to vulnerability issues. Adding custom system messages can be helpful and we are going to show you how to do it in few simple steps.

To add a custom system message you need to:

1. Register a new message in the message list;
2. Create a model class for the new message, which implements few necessary methods for further message handling.

The "\Magento\Framework\Notification\MessageList" class is responsible for…

I finally got an answer out of Magento engineering on those nodes and their best guess is as good as ours. i.e., they’re redundant/not-used.

There’s a few interesting points to make here for folks just learning to program, and just getting settled into the industry.

The first is software projects often grown beyond what any individual can understand, even (or especially) if that person works at the company responsible for that software. This is why programmers clammer for best-practices and consistency in their framework code. The ability to quickly trace out why something works a particular way is more important than any particular implementation, and inconsistent or over complex systems make that impossible.

The second is, when you find something that doesn’t work right, you’ll…

Although there’s no documentation stating this, based on system behavior it seems like the

class files are sort of required by a Magento module.

I say sort of required because you can run a module without them. You can use that module to add features to Magento. However, a version number for that module will not be added to the setup_module table unless the InstallSchema class is present.

I discovered this when I tried adding an UpgradeSchema class to a module that didn’t have an InstallSchema. The UpgradeSchema still ran, but calling $context->getVersion()

returned an empty string, as…

While PHP production environments have long made use of extra systems like memcache, varnish, and redis, most successful PHP projects also let developers and technically savvy folks drop an archive of files on a server, point the web server at those files, configure the application to point to a traditional RDMS/database, and have a working application.

After a year or so of life with the Magento 2 non-beta-beta, it’s becoming clearer that this isn’t a priority for Magento’s engineering team. The first run experience remains dismal, and the company’s efforts seem focused on tools for Silicon Vally professionals, such as Docker.

For my on work, I’m still installing Magento directly on my OS X/macOS workstation. With out of the box performance of the file based cache being what it is, I’ve started using redis as Magento’s…

This week it did not work out for me, I did the kata only once in PHP and that was not enough to get any particular insights. I’ll have to repeat it again some time soon! But on to the next one:

The task: build a function pipe() that takes any number of callables as arguments and returns a new callable.
The returned callable passes any arguments to the first callable, then the result of that to the next callable, and so on, and will return the final result.
So the processing order is left to right.

Example:

Optional follow up exercise:

implement a function compose(), which behaves just like pipe()…

In etwa zwei Wochen ist es wieder Zeit für einen der Höhepunkte in unserem Veranstaltungskalender. Nein, damit ist nicht Karneval gemeint, auch wenn wir dafür nach Köln fahren. Stattdessen geht es um die MageUnconference. Wir unterstützen das Event auch in diesem Jahr wieder als Hauptsponsor und werden mit dem gesamten Team vor Ort sein.

Wie schon in den letzten beiden Jahren treffen sich ein Wochenende lang Magento-Interessierte. Anders als bei einem Hackathon wird nicht programmiert. Anders als bei einer Konferenz gibt es auch keinen vorab geplanten Vortragsplan. Stattdessen werden an beiden Veranstaltungstagen morgens Themen vorgeschlagen, passende Vortragende aus den Teilnehmern erkoren und dann von allen darüber abgestimmt, welche Themen sie am meisten interessieren. Daraus ergibt sich dann der Plan des jeweiligen Tages.