At work I use Linux, but at home I prefer Windows due to gaming. In this short Tutorial I would like to share my Windows setup with you. My recommended setup includes: WSL 2 Docker Desktop for Windows Ubuntu / Debian GWSL (X-Server for Windows) PhpStorm Development Docker setup or my own Docker setup. (We will use my own in this tutorial) At first we need to install WSL 2 and Docker Desktop. Please follow the tutorials below. ...
Normally every project needs custom values saved on products or another entities. Shopware does offer by default Custom fields. It looks nice, but it can produce very fast issues. Before we start: This is my opinion Let’s start with a simple Pro Contra list. Pro Can be easily created in the Administration / Code. Can define field types, labels etc and Shopware does the rendering in Administration for me Loaded by default on the entities Custom Fields are schema less. You can save anything in it Contra Custom Fields are schema less. You can save anything in it They are saved as JSON Hard to modify using SQL Cannot have associations Slow on SQL Filtering, Aggregation Loaded by default on the entities Support between MySQL and MariaDB differs and Performance Cannot have Flags. All fields are public using Sales-Channel / Store-API Cause it does not have a Schema they will be indexed as dynamic in Elasticsearch. This brings lot of other problems You don’t have a control is it translatable or not Fields values cannot be easy deleted on all entities. You need to modify each entry. The most problems are introduced cause of the usage of an JSON field. In SQL the accessed fields needs to be extracted. This takes some time of course. On a bigger shop using many products this could leak to performance issues in the listing when it’s used inside a product filter. ...
This blog post describes a small example how to automaticly deploy plugin updates to the Store. I will use the FroshPerformance plugin as example. Preparation You will need a Plugin which based on the 5.2 Pluginsystem or Shopware 6 Plugin a Continuous Integration (i will use Travis as example) Credentials for the Shopware Account FroshPluginUploader Prepare the Plugin itself You will need a plugin.xml with filled title, version, description, compability and changelog for the languages en and de. All these informations will be picked up automaticly and updated in the Account. ...