Shopware 5.6.10: Unraveling the Checkout Comment Field Bug with Cookie Rejection

Shopware 5, while a robust platform, occasionally presents developers and merchants with intricate challenges. One such issue, highlighted in a community forum discussion, revolves around the persistent problem of the checkout comment field (sComment) being cleared when users reject cookies and then modify quantities via AJAX requests in Shopware 5.6.10.

The Problem: Ephemeral Comments in Shopware 5.6.10 Checkout

The initial post from Steffffi describes a frustrating scenario: despite attempts with JavaScript workarounds and even using third-party plugins, the comment field consistently loses its content during AJAX-driven quantity changes in the checkout process, specifically when cookie consent is denied. This issue pointed towards a deeper problem with how Shopware 5.6.10 handles session data under strict cookie consent rules.

Uncovering the Root Cause: BlackHoleStorage

The expert insight from MrAle quickly pinpointed the core of the problem: Shopware's BlackHoleStorage mechanism, implemented in /themes/Frontend/Responsive/frontend/_public/src/js/jquery.storage-manager.js. This mechanism is designed to prevent data from being written to or read from localStorage and sessionStorage if cookies are not accepted. The confusion arose because sessionStorage is often considered "technically necessary" and thus exempt from explicit consent, yet it was being blocked.

The Risky Fix: Bypassing Cookie Consent Entirely

Initially, an AI-generated solution proposed by Steffffi, after inputting MrAle's findings into Gemini, involved a drastic modification to the hasCookiesAllowed() function (presumably in jquery.state-manager.js or related context, though the file path was given as jquery.state-manager.js, the discussion implies jquery.storage-manager.js context). The suggested change was to simply return true at the beginning of the function:

function hasCookiesAllowed () {
    return true; // <--- Diesen Befehl einfügen!

    if (window.cookieRemoval === 0) {
        return true;
    }
    // ... der Rest wird nun vom Browser ignoriert

MrAle swiftly warned against this approach, emphasizing its severe implications. By forcing hasCookiesAllowed() to always return true, the system would falsely assume that all cookies were accepted, potentially compromising security features like Captcha and CSRF protection, and violating cookie consent regulations. This highlights the critical need for human oversight when implementing AI-generated code, especially in sensitive areas like user privacy and security.

A More Targeted (But Still Direct) Solution Attempt

Following MrAle's cautionary advice, Steffffi proposed a more specific modification aimed at re-enabling sessionStorage for the comment field without broadly bypassing cookie consent. This involved directly assigning window.sessionStorage to storage.session within the jquery.storage-manager.js file, specifically after enableBlackHoleStorage() is called:

            } else {
                enableBlackHoleStorage();
				//Kommentarfix
				storage.session = window.sessionStorage; 
				//Kommentarfix

This snippet attempts to override the BlackHoleStorage for the session storage specifically, allowing the comment field data to persist. While more targeted, it still represents a direct modification to a core Shopware JavaScript file, which can lead to issues during updates or when integrating other plugins that rely on the default storage manager behavior.

Key Takeaways for Shopware 5 Merchants and Developers

• Understanding Core Mechanisms: Deep dives into files like jquery.storage-manager.js are crucial for diagnosing complex issues related to cookie consent and data persistence in Shopware 5.
• Caution with AI-Generated Code: While AI can provide quick suggestions, always validate them against security, compliance, and best practices, especially when dealing with core system functionalities.
• Impact of Cookie Consent: Strict cookie consent implementations can have cascading effects on seemingly unrelated functionalities, requiring careful attention to how session and local storage are managed.
• Shopware 5 Specifics: This issue is particular to Shopware 5. For long-term stability and compliance, considering a migration to Shopware 6, which has a more modern and robust approach to cookie management, is often advisable.

This forum discussion serves as a valuable case study, illustrating the complexities of maintaining older e-commerce platforms and the importance of expert knowledge in navigating technical challenges while upholding user privacy and store functionality.