During the migration of a Shopware 5 system to a containerized environment, an error pattern emerged that initially seemed unusual: The backend loaded, but instead of the usual interface, a Shopware error dialog appeared that completely blocked the user. This error dialog contained:
A technical field report from practical web development – for everyone who programs and maintains websites with Neos CMS.
An online shop is more than just a list of products. It needs to create trust, make purchasing decisions easier, and appeal to customers' emotions. Anyone who neglects these factors is giving away revenue and valuable customer loyalty. In this article, you will learn which elements should not be missing from any successful shop and how to implement them optimally.
Does this sound familiar? You have built an online shop with the Magento CMS to sell your products online. To improve customer loyalty, your customers can send you messages via forms. But your inbox is full of spam messages in Cyrillic, Arabic, or Chinese, and you don't know how to effectively protect yourself against them?
If you use Shopware as an e-commerce platform for your company, you certainly know that operating and scaling it optimally requires a great deal of time, effort, and resources. To ensure that your Shopware shop grows quickly and that you are successful in the e-commerce business, you need expert knowledge. In this blog post, we provide you with a guide on how to scale your Shopware shop quickly and efficiently. We will explain helpful tips and techniques so that you can maximize your e-commerce success. Let's get started and discover which steps you need to take to achieve the perfect scaling of your Shopware shop.
Our agency's goal was to use a hash in the URL to target an anchor on an online shop based on Shopware 5. In other words, we wanted to automatically scroll down to an anchor (to an element with the ID "someanchor") after entering, for example, https://irgendeinonlineshop.de#irgendeinesprungmarke in the browser. In principle, this mechanism is application-independent; it works just as well in a Magento 2 online shop as it does on a static HTML website. However, this is not the case in Shopware 5 if the anchor is embedded in a shopping world, regardless of whether it is loaded via AJAX or not.
Question from our agency regarding a webshop built with Shopware 5: How can you add the EANs of the variant products of a main product to the variant selection? The goal here was to add the EAN as an additional identifier to the respective option, which could then be controlled via an automated size selection. In other words: If I select a specific size using a size calculator, this size is selected via the corresponding EAN (jQuery), and the associated variant product is then loaded. This can also be applied to the more general question: How can I add properties of main or variant products or any additional information to the product detail page of my Shopware 5 online shop?
At our web agency, we use the Google Tag Manager plugin by codiverse for a Shopware 5 customer. The plugin prepares a dataLayer that can then be conveniently read via Google Tag Manager. However, we were missing the current shopping cart value, which in the basic configuration of the online shop / plugin was only provided during checkout.
At our agency, we use a Smartfit size calculator for a project that can calculate the size of the desired item based on several parameters. The problem here is that the part of the product detail page that contains the calculator is re-rendered via AJAX after a variant is selected, and the size calculator is then not re-populated and no longer works.
Today's problem at our web agency: We want to add a text block above a selected payment method on a website / online shop (implemented with Shopware 5) that we can freely modify. In this particular case, we want to display a note above various leasing models indicating that additional information is required in a text field. Our Shopware 5 online shop also uses PayPal Plus, meaning that payment methods other than PayPal are rendered through the PayPal Plus module. Therefore, we cannot modify the standard Bare theme directly, but instead need to make changes to the PayPal plugin in our theme.
If you want to change the specified financing example of the Shopware plugin "Consors Finanz" by the plugin developer "MILLEMEDIA" on the product detail page, this cannot be done via the backend. Instead, you can intervene directly in the function that selects the respective example. For example, we do not want to display the lowest installment, but rather the lowest installment with 0% financing.
When we create an online shop with Shopware, a customer may request that Google Tag Manager be integrated as a supporting tool for online marketing. There are extensions available for this, but for technicians, doing it manually is basically easier and faster and generally does not result in compatibility issues or the need to make adjustments after updates. In principle, changes in just 2 places in Shopware are enough to make the online shop ready for Google Tag Manager.
If you encounter an AJAX error (Error 500) in the Shopware backend in the order overview (Customers->Orders) and cannot view all customer orders, it is advisable to check the Shopware error logs (directly in the backend or via var/log/). In our case, the error indicated that there were problems with the payment status. The exact error message in the log file was:
Problem statement at our web agency: If the current PayPal plugin ("SwagPaymentPayPalUnified", see https://store.shopware.com/swag828732772311f/paypal.html, which replaces the old "PayPal Express" plugin) is used to enable PayPal Express Checkout in a Shopware online shop, but the PayPal Express Checkout is not displayed, this may be due to the localization of the Shopware shop. In our case, the console reported the JavaScript error "Error: Expected props.locale to be valid", meaning that the localization was invalid. In our case, it was Kazakh (language code "kk_KZ"), because we use the "Deutsch Du - Shopware 5+ ready" language pack from "Shop Uebersetzungen". However, the code "kk-KZ" is not supported by the PayPal plugin. So what can be done?
Question at our web agency while creating a Shopware online shop: How can you prevent the category menu from being displayed when opening the OffCanvas menu in the mobile views (viewports "s" and "xs") for categories without subcategories, forcing the user to click again to return to the main navigation? This behavior, which is included by Shopware in the standard installation, is implemented using a plugin ("swSubCategoryNav") that relies on the attribute "[data-subcategory-nav="true"]". This behavior is defined in the file
Problem statement at our web agency: In a Shopware-based online shop, we want to set up an accordion for all viewports / screen widths that contains the product description in the product detail view. To do this, we can use the existing swCollapsePanel plugin, which Shopware already uses, for example, to display the cross-selling slider in the "s" and "xs" viewports via the StateManager (using the selector ".tab-menu--cross-selling .tab--header" for the header and ".tab--content" for the content). First, we take a look at the file
Today’s problem at our web agency: How do I change the breakpoints in a child theme based on the Responsive theme in a Shopware-based online shop? Ideally, we would simply move the file in which the breakpoints are defined into the child theme and then change the breakpoints there. Unfortunately, it does not work that way. We have to use the StateManager, which allows us in Shopware to execute JavaScript plugins depending on different screen widths (see also https://developers.shopware.com/designers-guide/javascript-statemanager-and-pluginbase/).
Even without a plugin, it is relatively straightforward to add an add-to-cart button to the wishlist in an online shop implemented with Shopware 5. Based on the buy button used in the product listing (/themes/Frontend/Bare/frontend/listing/product-box/button-buy.tpl), we need to find the appropriate template file for displaying the items in the wishlist. We find this in /themes/Frontend/Bare/frontend/note/item.tpl. More specifically, the relevant block here is {block name="frontend_note_item_actions_buy"}. Of course, you should not modify the Bare theme directly, but instead extend the block in your own theme. We then populate the block with the shopping cart form, as it is also displayed in the product listing:
If you try to place a banner in Shopware and also want to place shopping worlds on the same page, you will quickly notice that the banner disappears when the shopping world is activated. To display both at the same time, a small change to the theme is necessary.
When installing a Shopware shop locally with XAMPP, it can happen that the shopping worlds on the homepage have extremely long loading times. In the worst case, the shopping world may not load at all. I will now show you how to fix this problem.
By default, the language switcher in Shopware (which manages the different shop languages) is displayed as a dropdown and is located at the very top of the header inside a <div> element with the class "top-bar". According to our design template, however, it needs to be placed in the main navigation and should look something like EN | DE.
The Shopware error message "core.ERROR: exception 'Doctrine\DBAL\Types\ConversionException' with message 'Could not convert database value "s:0:""" to Doctrine Type object'" or a similar error message may indicate invalid values in the "s_core_config_elements" table. If a terminating semicolon is missing after an entry in the "value" column, Shopware (under Linux) cannot process it (whereas Windows can).
Shopware and older browsers — here is another chapter: On our Samsung Galaxy Tab 3 10.1 (GT-P5200) tablet using the native Android browser, our online shop displays the message "Invalid form token" on the contact page and on some other pages after attempting to submit a form.
Online shops built with Shopware can be set up professionally and offer good usability for both shop operators and users. However, Shopware has a difficult relationship with older browsers — unfortunately, there is no other way to put it. Here is an example of how Shopware can cost an online shop developer several hours of work: In the standard Shopware template, the service dropdown menu in the top right cannot be opened because it immediately disappears again after briefly opening. This problem occurred on a Samsung Galaxy Tab 3 10.1 (GT-P5200) using the native Android browser. The reason is the simultaneous assignment of "click" and "touchstart" listeners, which in
The speed of a shop, alongside user guidance and styling, is a decisive factor for many customers when deciding whether or not to place an order with you. A shop where customers have to wait 20–30 seconds before they can see the next page will have a hard time being successful. Many customers will abandon their purchase in frustration before completing their order because they are (rightly) unwilling to wait minutes for the product details or checkout to load. That is why it is important to keep waiting times as short as possible. Today, I will show you how to achieve this.
By default, Shopware does not use HTML formatting in the product listing. This is inconvenient when you have different, independent pieces of information in the product description that you naturally want to display in a structured way.
For example: the product name, the manufacturer, a product description, and the place of origin. Without HTML formatting, all of this is displayed in the listing without formatting or line breaks, one item after another. We will now show you how to enable HTML formatting in the listing.
For some inexplicable reason, the “WooCommerce” plugin does not have the option to display only the free shipping method when a certain order value is reached. Normally, the standard shipping method is displayed alongside the free shipping option. This can often be confusing for customers and should therefore be changed for usability reasons.
In January 2016, a change to the information requirements for online merchants comes into effect (Art. 14 of the ODR Regulation / Regulation on Online Dispute Resolution for consumer disputes No. 524/2013). The new information requirement concerning online dispute resolution will take effect on 09.01.2016.
If errors occur when saving product attributes in Modified Shop (xtcmodified) after the online shop creation, this may be related to the number of attributes if the so-called Suhosin component is installed on the underlying server.
Integrating various payment methods into osCommerce online shops via Skrill / Moneybookers can be difficult when using version 2.3.
Hier ein Vorschlag zur Erstellung eines ausklappbaren Kategorien-Menüs in osCommerce
The variables $languages_id, $languages_name, and $languages_code provide us with the current language
To extend or completely disable the automatic logoff of an (inactive) admin within an osCommerce installation (e.g. osC 2.3.2),
If "auto" is set as the value for "image width" or "image height" to automatically calculate the product image width or height in osC (this applies to preview images / thumbnail images / thumbnails)
Eine kurze Anleitung zum Hinzufügen eigener Inhalte im osCommerce-System (osC 2.3.2) am Beispiel einer Impressumsseite:
If problems occur after installing the WYSIWYG editor (WYSIWYG = What You See Is What You Get) "ckeditor" (latest update of the osC contribution at the time of this article: 21.03.2011)
Select your language
