The PHP USERGROUP DRESDEN e.V. turns 6 years old and celebrates this special occasion with its members, friends, and partners on the 25th of August 2022.
While deploying an upgrade for one of our Magento projects, I run into a problem with Elasticsuite.
After almost 3 years, the Magento Stammtisch Rhein-Main finally meets again in person. YEAH! I am really looking forward to seeing all attendees again!
While migrating a Magento module to make use of the declarative db schema, I ran into the following MySQL error:
MySQL error code 121: Duplicate key on write or update
Meet Magento UK went virtual for the past two years as most conferences did, but in 2022 they are back with an in-person, all-day conference again. YEAH!
A few weeks ago, whilst applying the latest security patches for Magento, I ran into a problem in our build pipeline. The patches could be applied locally without any issues, but in our build pipeline applying the patches failed.
A while ago a merchant notified us that it was not possible anymore to edit categories in Magento. In the Magento logs, I found several similar error messages:
A while ago we took over a Magento 1 shop that was migrated over to Magento 2. Some products and categories has a “.html.html” url postfix and the merchant wanted to have this fixed. When data was migrated from Magento 1 shop, the url keys came with ".html" suffix. On Magento 2, you have url_key and url_path attributes that help creating the urls for products and categories. Since the url_key attribute contained the “.html” postfix and url_path appended an additional “.html” postfix, the source of the problem was found.