Description

The error "Oops! An Error Occurred" appears in the storefront.

Oops! An Error Occurred

The server returned a "500 Internal Server Error".

Something is broken. Please let us know what you were doing when this error occurred. We will fix it as soon as possible. Sorry for any inconvenience caused.

Causes

The error "Oops! An Error Occurred" is a common error that is displayed when a technical problem occurs and a certain feature or page cannot be loaded properly. There are several possible causes for the error "Oops! An Error Occurred" error in Shopware.

• Incompatible extensions or themes: Extensions that are not compatible with the current Shopware version can cause the error.

• Missing, outdated or faulty files: Corrupted, outdated, or missing files can cause the error.

• Incorrect settings: Incorrect settings can cause the error.

• Database issues: Corrupted or missing entries in the database can cause the error.

• Server issues: Insufficient resources, incorrect configurations, or network problems on the server can cause the error.

To resolve the error effectively, you should proceed systematically. The following steps will help you identify potential causes and fix the issue.

• Check extensions and themes: Ensure all extensions are compatible with the current Shopware version. Update all extensions and temporarily disable any incompatible ones.

• Clear cache: Clear the entire Shopware cache (possibly via FTP).

• Check files and configurations: Ensure all required files are present and the Shopware configuration is correct.

• Update Shopware:

The "Oops! An Error Occurred" error in Shopware can be resolved through a systematic check of extensions, themes, the database, and the server environment.

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

Description

The branding ("Theme by ThemeWare®") is displayed in the Storefront even though you have entered a Licence Key in the theme configuration.

Basic information

If you want to remove the ThemeWare® branding, you can purchase a license from us. If you are interested, the fastest way to contact us is here.

Solution

1. Check once again that you have selected the correct ThemeWare® version for your licence key.

2. Check whether you have entered the licence key correctly. (Sometimes, for example, spaces are entered before or after the Licence Key.)

3. Recompile the theme once.

4. Clear the Shopware and your Browser cache completely.

5. Check whether you have installed the plugin "" and delete it completely from your shop. The plugin is explicitly intended only for the default Shopware theme.

One or more configuration fields are missing in the theme configuration although they are listed in the ThemeWare® Config Finder or the ThemeWare® Documentation.

If one or more configuration fields are missing in the theme configuration, there are two possible causes:

1. Most likely you are not using the latest version of ThemeWare®.

2. There was a problem with a Shopware or ThemeWare® update.

Both the ThemeWare® Documentation and the are based on the latest version of ThemeWare®. If you find a feature or configuration there that is missing in your shop, you are probably not using the latest version of ThemeWare®.

• Branding is shown despite Licence Key

• CMS blocks are not displayed in Shopping Experience

• Gallery sliders have a wrong height on mobile devices

Unfortunately, the ThemeWare® CMS block "Listing subcategories" does not display any subcategories.

As the name suggests, the CMS extension "Listing subcategories" only works on CMS pages of the type "Listing page". In addition, subcategories in Shopware 6 are only displayed for the main category.

Create a CMS layout of the type "Listing page", add the CMS block "Listing subcategorie" and assign the layout to the desired category. Also make sure that the corresponding category page is in a main category.

Description

One or more pop-ups or modals remain empty and do not display any content. This can affect, for example, the "Privacy" and/or "Terms and Conditions" modal from the footer and/or the "Shipping Costs" modal on the product page.

Cause

This is not a theme "problem" or "bug" but a missing or incomplete Shopware configuration.

In order for shop pages to be displayed in modals (pop-ups), they must be created as Shopping Experience layouts and assigned in the Shopware settings.

Solution

1. Create the corresponding shop page as a Shopping Experience layout ("Contents" => "Shopping Experience" => "Shop pages")

2. Assign this shop page layout via the Shopware settings to your storefront zu ("Settings" => "Shop" => "Basic information" => "Shop pages")

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

Description

-

Cause

Most representation errors in the storefront result from an outdated browser or Shopware cache.

Solution

You can easily solve most of the representation errors in Shopware 6 yourself without having to wait for us.

In our article How can I fix representation errors? we show you two simple steps to fix representation errors and what is the best way to proceed if these steps do not help.

Issue not solved?

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

Your administration is not accessible after a Shopware update (or shows a white page).

You probably have an incompatible extension active in your system.

In rare cases, an extension may not be compatible with the old and the new Shopware version at the same time. If you activate an incompatible extension or do not deactivate it before the Shopware update, the administration may no longer be accessible.

Deactivate the corresponding extension (or all extensions) via the database. The administration should then be accessible again.

Update all extensions and only activate them once you have ensured that they are installed in a compatible version.

In the following instructions, we show you how to deactivate an extension via the database using ThemeWare® as an example:

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

Here you can find solutions to the most common issues and errors in the Shopware 6 storefront.

Caused by our experiences with more than 3,000 customers, we have already seen and solved almost every issue. It is therefore very likely that the problem is already known and that there is already a solution.

You may find configuration fields (usually titled "twt-...") in the "General" tab of the ThemeWare® configuration that have no effect.

These are "orphaned configuration fields". These occur when a configuration field has been edited by the user at some point and this configuration field is deleted with a theme update.

Unfortunately, the Shopware update routine currently does not automatically remove those configuration fields.

In response to our issue (NEXT-14571), Shopware has extended the "Save" button in the theme configuration in Shopware 6.4.8.0 and added a "Clean" option. This allows you to delete "orphaned configuration fields".

You can find out how to remove "orphaned configuration fields" in the article .

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

If you are missing one or more features or configurations that you can find in the ThemeWare® Documentation or in the ThemeWare® Config Finder, take a look at the following article:

Description

The error "Unfortunately, something went wrong." appears on the product page if you use our "ThemeWare® Customizing Plugin".

Cause

In this case, the cause is an outdated version of the extension or an outdated customisation.

Solution

1. Please remove the content in the following files:

   1. File "main.scss":

      • Delete everything

      • File location: custom/plugins/TcinnCustomizing/src/Resources/app/storefront/src/scss/

   2. File "headline.html.twig":

      • Delete everything from line 2

      • File location: custom/plugins/TcinnCustomizing/src/Resources/views/storefront/page/product-detail/

2. Then refresh the storefront once to transfer the changes to the storefront:

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

You get the error message Unable to compile the theme "TcinnThemeWare...". $color2: 0 is not a color.

Crucial is the part directly after the message Unable to compile the theme "TcinnThemeWare...". It says $color2: 0 is not a color.

This error message is due to the new validation of the theme configuration as of Shopware 6.6.9.

Check whether you are using empty colour configuration fields. Empty colour fields are usually not valid and lead to this error message. Fill empty colour fields to be able to compile your theme again.

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

When assigning the theme to a sales channel, the error message "Theme could not be assigned to Sales Channel." appears.

Unfortunately, the error message is not very significant. A more detailed error message is needed to solve the problem.

How to get a detailed error message please find in the article .

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

The Shopping Experience layout has been assigned but the CMS blocks are not displayed in the storefront.

ThemeWare® provides "CMS animations". With this feature, CMS blocks are hidden and displayed with a CSS animation when the CMS page is scrolled as soon as the corresponding CMS block comes into the viewable area of the browser window.

This animation is managed by JavaScript.

If the CMS blocks are not displayed as intended, there is a 99.9% chance that you will find one or more error messages in the browser DevTools that refer to JavaScript errors.

JavaScript errors caused by third-party extensions can affect ThemeWare® JavaScript features. In this case the scroll animation is obviously affected.

You get the error message Unable to compile the theme "TcinnThemeWare...". $color: 0 is not a color.

Crucial is the part directly after the message Unable to compile the theme "TcinnThemeWare...". It says $color: 0 is not a color.

This error message is due to the new validation of the theme configuration as of Shopware 6.6.9.

Check whether you are using empty colour configuration fields. Empty colour fields are usually not valid and lead to this error message. Fill empty colour fields to be able to compile your theme again.

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

The pop-up or modal for "Terms and Conditions" (e.g. in the footer) opens, but remains empty.

This is not a theme "problem" or "bug" but a missing or incomplete Shopware configuration.

More information and instructions on how to solve this "issue" can be found in the following article .

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

When saving your Shopping Experience, you receive the error message "Some blocks were not configured sufficiently." or "Errors occurred. Please check the error list in the editor.".

Shopware usually indicates that you have not completely filled in all mandatory fields of a CMS element.

Fill in all mandatory fields of your newly added CMS elements. These are often image fields or missing products in product sliders.

You can find more information in the following article:

Description

When saving the theme, you will receive the error message Invalid configuration – The configuration is faulty. The theme cannot be saved.

Cause

The message suggests that an error has occurred during the compilation of the storefront (Shopware Core + theme + customisations + extensions).

This error usually occurs when saving the theme, as this triggers the compilation process.

We are currently aware of two source texts:

1. Usually, the issue is simply down to a configuration field that has been filled in incorrectly, for example, containing the wrong value.

2. However, as described above, it can also occur due to an error in a customisation or third-party extension.

However, as described above, it can also occur due to an error in a customisation or third-party extension.

Why hasn't this error been noticed before?

You may not have noticed this error in Shopware 6.6. However, with Shopware 6.7, the validation of the theme configuration has been significantly improved so that even minor typos are now reliably detected.

There are two ways to resolve this error:

1. You have entered an incorrect value:

   • As the configuration could not be saved, the incorrect value was not applied. Reload the configuration and you can continue as normal.

2. The value was already incorrect before the update from Shopware 6.6 to 6.7.

   • Try the theme configuration validation to get more info. For example:

You can find more information about validation in the following article:

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

Description

If you find the message "Allowed memory size of ... bytes exhausted" in the PHP error log or in the Shopware log files, the issue is caused by the PHP memory_limit.

Cause

The error message "Allowed memory size exhausted" is one of the most common issues in shop or content management systems, especially if you are using a shared hosting service.

This means that the web server limits the amount of memory used by Shopware and the memory provided is not sufficient.

Solution

The decisive factor in this error is the PHP memory_limit of your web server.

Shopware recommends a memory_limit of "512 MB or higher". Please increase the memory_limit of your web server to the value recommended by Shopware (or higher).

In case you do not know how to change the value, your hoster will certainly be happy to help you.

Issue not solved?

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

You get the error message No default folder for entity "cms_page" found if you want to import the Shopping Experience into your ThemeWare® theme.

Internal Server Error No default folder for entity "cms_page" found, please make sure that basic data is available by running the migrations.

The sample images of our Shopping Experiences are installed in the standard folder ‘CMS Media’ during import. This folder is usually already available in Shopware. If the folder has not been created or has been removed for any reason, the images cannot be imported.

All you need to do is create the appropriate standard folder. Please refer to our instructions below:

Once you have created the folder, you can easily install/activate the plugin.

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

You get the error message Unable to compile the theme "TcinnThemeWare...". $color: 0 is not a color.

Crucial is the part directly after the message Unable to compile the theme "TcinnThemeWare...". It says $color: 0 is not a color.

This error message is due to the new validation of the theme configuration as of Shopware 6.6.9.

Check whether you are using empty colour configuration fields. Empty colour fields are usually not valid and lead to this error message. Fill empty colour fields to be able to compile your theme again.

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

Variants of the error with the title "Bad request":

Description

In Shopware 6.3.2.1 the gallery slider on the product page has an incorrect height in the smartphone viewport. This creates an unnecessary blank space between the slider and the price.

Solution

Issue not solved?

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

No ThemeWare® update is available in your administration, although a new version of ThemeWare® is already listed in the Shopware Store or in our Service Portal.

This "issue" can have various causes:

The lack of an update option for extensions or themes may simply be due to time constraints. It can take a while until an update is available in your system.

Or the subscription for your theme – in the case of a purchased version of ThemeWare® – has expired.

However, it can also be due to an outdated Shopware version. If an extension or theme is not compatible with your Shopware version, you will not receive further updates until you have updated Shopware.

In addition, there are cases where the Shopware account is not or no longer connected to the shop. In this case, the shop no longer receives information about available updates.

Due to the options mentioned above, there is no definite solution but several possible solutions.

When saving your Shopping Experience, you receive the error message "Configuration required. Please fill in data in all elements.".

This is Shopware's way of indicating that you have not completely filled in all the mandatory fields of a CMS element.

Fill all mandatory fields of your newly added CMS elements. These are often image fields.

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

You get the error message Unable to compile the theme "TcinnThemeWare...". parse error: failed at $...

Crucial here is the note "parse error: failed at $...". This means that a wrong value was entered in a configuration field and in which configuration field this is the case respectively the technical name of the field: $...

If the error message says Unable to compile the theme "TcinnThemeWareBath". parse error: failed at $sw-font-family-base: ‚Open Sans', sans-serif; (stdin) on line 11, at column 1, for example, the theme cannot be compiled or even saved due to an error in the $sw-font-family-base configuration field.

Just change the corresponding configuration field.

If you don't know which configuration field you are dealing with, just visit the ThemeWare® Config Finder and search there for the technical name

When saving your Shopping Experience, you receive the error message "Some blocks were not configured sufficiently." or "Errors occurred. Please check the error list in the editor.".

This is Shopware's way of indicating that you have not completely filled in all the mandatory fields of a CMS element.

Fill all mandatory fields of your newly added CMS elements. These are often image fields or missing products in product sliders.

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

You get the error message Unable to compile the theme "TcinnThemeWare..." in the theme configuration.

Please take a look at the following article:

Description

You will receive the following error message when validating the theme configuration SCSS Value "..." is not valid for type "color".

Examples:

• SCSS Value "#9fa5ab;" is not valid for type "color"

• SCSS Value "none" is not valid for type "color"

• SCSS Value 'color' cannot be 'none'

This error message is caused by improved validation of the theme configuration in Shopware 6.7 and indicates that you have filled in a colour configuration field incorrectly.

There are two possibilities for this error:

1. You filled a field incorrectly before saving.

   • The incorrect value will not be applied. Reload the configuration and everything will be fine again.

2. You filled in a field incorrectly before updating to Shopware 6.7.

   • You must now find the value and correct it.

Why hasn't this error been noticed before?

You may not have noticed this error in Shopware 6.6. However, with Shopware 6.7, the validation of the theme configuration has been significantly improved so that even minor typos are now reliably detected.

You can find out how to correct invalid configuration fields in the following article:

You can find more information about this validation error in the following article:

Description

The theme cannot be saved – for example, after a Shopware update – so your changes will not be applied.

The cause is stated in the accompanying error message. Usually, you have configured a configuration field incorrectly.

Potential error messages:

You get the following error message during a Shopware update or when deactivating or uninstalling a theme:

Unable to deactivate or uninstall theme "{themeName}". Please remove the following theme assignments: {assignments}.

As the error message says, a theme must no longer be assigned to a sales channel so that it can be deactivated or uninstalled.

With this message, Shopware asks you to remove the assignment of a theme (see {themeName}) from the sales channel (see {assignments}).

In this case, simply assign the Shopware Standard Theme to the corresponding sales channel.

Description

The header overlays the Shopping Experience on the home page / the Shopping Experience is overlaid by the header.

Cause

The fact that the header overlays the Shopping Experience on the home page is not a representation error but a configurable effect of ThemeWare® in order to enable a certain look in different themes such as ThemeWare® Outdoor, ThemeWare® Exquisite or ThemeWare® Lights.

You are probably using one of these themes, because the ThemeWare® Shopping Experience Header is already configured in them.

Solution

You can find out how to use or deactivate the header in the article Configuring the Shopping Experiences Header.

Issue not solved?

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

Description

Either the error massage "Error 500" occurs in the Theme Management and/or the theme cannot be saved.

Cause

Typically, this error means that the server is not providing enough resources. This does not mean that the server is generally too weak, it is more of a configuration issue.

In most cases, you will find the specific cause in the PHP error log on your server. This does not mean the log within Shopware. If you do not know how to check the PHP error log, your hoster will certainly be happy to help you.

In the PHP error log you will probably find references to the PHP settings memory_limit or max_execution_time.

Solution

Increase the memory_limit and/or the max_execution_time to the recommended values (or higher):

• memory_limit: min. 512 MB

• max_execution_time: min. 60 seconds

In case you do not know how to change the value, your hoster will certainly be happy to help you.

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

Description

You get the error message Unable to compile the theme "TcinnThemeWare..." in the theme configuration.

Cause

There are several possibilities here, because this error can be caused by an unknown variable in a configuration field or by an incorrectly filled configuration field.

• Unable to compile the theme "TcinnThemeWare...". Undefined variable $...

• Unable to compile the theme "TcinnThemeWare...". parse error: failed at $...

In addition, there are new error messages due to the new validation of the theme configuration from Shopware 6.6.9:

• Unable to compile the theme "TcinnThemeWare...". Error: argument `$color` of `red($color)` must be a color

• Unable to compile the theme "TcinnThemeWare...". $color: 0 is not a color

• Unable to compile the theme "TcinnThemeWare...". $color2: 0 is not a color

The part directly after the message Unable to compile the theme "..." is decisive. It says Undefined variable $... or parse error: failed at $... or a reference to the variable $color or $color2.

Description

You get the error message Error compiling theme in the theme configuration.

Solution

If you click on "Show full error" it says "Unable to compile the theme...". Please have a look at the following article:

After a theme update, representation errors soccasionally occurred in the storefront in a theme duplicate.

If representation errors only occurred in a theme duplicate, a bug in Shopware was usually the cause.

You can find more information in the article .

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

Description

In some rare cases it might happen that an update is available in the extension administration, but it cannot be executed.

Cause

Unfortunately, there is no definite solution so far, as the problem can have various causes.

Solutions

There are currently several possible workarounds:

1) Check the PHP memory limit

In our experience, an insufficient PHP memory_limit is often the cause of problems with updates of extensions (plugins, apps or themes).

Check and if necessary increase the PHP memory_limit to the value recommended by Shopware of "512 MB or higher".

If you do not know how to change the value, your hoster will certainly be happy to help you.

2) Deactivate theme

It is always a good idea to deactivate (not uninstall!) an extension (plugin or app) or theme before updating. This often helps with update problems.

1. Instructions:

2. Instructions:

3. Instructions:

In some rare cases, the update with step 1 and 2 still does not work. There might be e.g. a problem with file permissions. In most of such cases the only thing that helps is a reinstallation.

1. Instructions:

2. Instructions:

3. Instructions:

In addition to the above options, a manual theme update via the Shopware 6 Extension Management would also be an option.

• Instructions:

You can also upload the ThemeWare® zip file to your server manually via FTP instead of using the Extension Management. Take particular care that the file permissions of the source files do not get messed up.

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

Description

The improved presentation of the theme configuration does not appear in a duplicate theme.

Cause

To ensure that the improved presentation of the theme configuration and the useful links of ThemeWare® do not affect other themes, it is necessary for us to restrict them to ThemeWare®. This is currently only possible by referring to the theme name.

If your theme duplicate does not contain the word "ThemeWare" in its name, the improved presentation of the theme configuration will not be applied.

Solution

Rename your theme duplicate and add the word "ThemeWare" to benefit from the improved presentation of the theme configuration.

Screenshots

Issue not solved?

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

Description

When saving the theme configuration, the error message "Error 400" or "Error: Request failed with status code 400" is displayed and the theme has not been saved.

Clicking on the button "Show full error" opens a pop-up with the message "Unable to compile the theme "TcinnThemeWare...". Undefined variable $...".

Cause

The message "Undefined variable $..." refers to a theme variable that is used in a configuration field. This is basically possible, but is unfortunately subject to a restriction.

Variables must be initialised before they can be used in another configuration field. This is only the case if the variable has already been defined before the intended configuration field.

The problem affects all configuration fields, but mainly occurs in Shopware standard configuration fields and theme duplicates. (Problematic configuration fields are indicated with corresponding information in their help texts).

If you currently entered a variable in a configuration field, reload the theme configuration and change the corresponding configuration field back to an appropriate HEX or RGB value.

If you do not know which configuration field this is, just visit the ThemeWare® Config Finder and search there for the technical name from the error message (e.g. $twt-color-brand-primary-light) without the dollar sign "$".

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

Instead of the selected images, the placeholder images are displayed. Unfortunately, this affects all CMS elements, including those from ThemeWare®. The correct images are nevertheless displayed in the Storefront.

Unfortunately, there was a bug in Shopware 6.4.14 in the Shopping Experience editor regarding the preview images of CMS elements. This was reported to Shopware and fixed with version 6.4.15.

Just update Shopware to version 6.4.15.

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

For a while, new configuration fields of themes were not applied to theme duplicates (child themes) during a theme update.

Please update Shopware and ThemeWare® to the latest version.

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

The Shopping Experience layout has been assigned but the CMS blocks are not displayed in the storefront.

The sticky top navigation and the Shopping Experience Header from ThemeWare® are displayed and positioned using JavaScript.

If the sticky top navigation is not displayed, there is a 99.9% chance that you will find one or more error messages in the browser DevTools relating to JavaScript errors.

JavaScript errors caused by third-party extensions can affect ThemeWare® JavaScript features. In this case, the sticky top navigation is obviously affected.

Deactivate (not uninstall!) all extensions used. If the problem no longer exists after deactivating all extensions, the issue is probably due to an extension.

You can find more information in the article .

The pop-up or modal for "Shipping Costs" (e.g. on the product page) opens but remains empty.

This is not a theme "problem" or "bug" but a missing or incomplete Shopware configuration.

More information and instructions on how to solve this "issue" can be found in the following article .

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

Description

You get the error message Unable to compile the theme "...". Undefined variable $....

Cause

Crucial here is the note "Undefined variable $...". This means that an unknown variable was entered in a configuration field and in which configuration field this is the case respectively what the technical name of the field is: $...

Example:

If the error message says Unable to compile the theme "TcinnThemeWareModern". Undefined variable $twt-color-brand-primary-light: line: 12, column 1, for example, the theme cannot be compiled or even saved due to an error in the $twt-color-brand-primary-light configuration field.

Solution

Just change the corresponding configuration field.

If you don't know which configuration field you are dealing with, just visit the ThemeWare® Config Finder and search there for the technical name twt-color-brand-primary-light (without the "$").

After you have adjusted the field, the theme or the duplicate can be saved and compiled again.

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

The pop-up or modal for " Privacy" (e.g. in the footer newsletter) opens but remains empty.

This is not a theme "problem" or "bug" but a missing or incomplete Shopware configuration.

More information and instructions on how to solve this "issue" can be found in the following article .

If you could not solve the problem, simply start the ThemeWare® Debugging. You can open a support ticket in case you are not able to solve the problem yourself:

Saving the theme configuration takes several minutes.

When saving the theme configuration, the entire storefront is being compiled in the background. This means that the entire JS and CSS code of Shopware and all extensions (plugins, apps and themes) will be rebuilt.

This can take 1-2 minutes depending on the theme, especially if a theme offers many settings, such as ThemeWare®.

This process is mostly RAM and CPU dependent. Check if your server has sufficient resources and PHP is allocated these resources.