It feels a little thiefy, but from my point of view, is this too easy, brilliant and good to not conserve it from slack. And because he doesn’t want to, here we are. Thanks Melvin for hosting with us ?
Melvin Achterhuis just post this:
{% sw_extends '@Administration/administration/index.html.twig' %}
{% block administration_templates %}
{{ parent() }}
{% if '.test' or '.our-test-domain.com' in app.request.schemeAndHttpHost %}
<style>
body .sw-desktop__content::before {
content: 'Test environment';
background-color: red;
font-weight: bold;
color: white;
display: flex;
padding: 16px 0;
justify-content: center;
}
</style>
{% endif %}
{% endblock %}And added a screenshot, showing the shopware administration with a bold red banner at the top „Test environment“.
You know the admin’s „duplicate“ button on products. Now the ticket says: „We need that, but from code — duplicate a product per sales channel, with adjusted name and its own product number.“ Or: „Campaign landing pages: clone this CMS page 20 times with different headlines.“ I’ve watched this get implemented as: load entity with […]
The requirement sounds harmless every time: „Log when a product price changes, with old and new value.“ Or: „When an order’s email changes, notify the old address.“ Or the audit-trail classic: „Who changed what, from what, to what?“ And every time, the naive implementation is the same sad shape: subscribe to product.written, load the entity […]
A code review scenario. A plugin adds a purchasePrice-style field to a custom entity — internal margin data. The review question: „Can the Store API read this?“ Followed by: „Can the Admin API write that computed field you recalculate in a subscriber?“ The answers, in the plugin at hand, were „yes“ and „yes, and then […]
