Navigating Shopware 6.7.16 Update Challenges: Plugin Conflicts and Configuration Service Errors
Navigating Shopware 6.7.16 Update Challenges: Plugin Conflicts and Configuration Service Errors
This community insight delves into critical issues encountered during a Shopware 6.7.15.1 to 6.7.16 update, specifically focusing on plugin compatibility and core framework changes. The discussion highlights two primary errors: ConfigReader::getTabDefinitions(): ... DOMComment given and ConfigurationService::$bundles must not be accessed before initialization during theme compilation.
The initial DOMComment given error was identified as a Shopware 6.7.16 core bug (Issue #22418). Shopware 6.7.16 changed how config.xml files are parsed, expecting as the first element. If a comment precedes it, the error occurs. A temporary workaround involved manually removing or relocating comments in affected plugin config.xml files.
However, a more persistent ConfigurationService::$bundles error emerged, preventing theme compilation and further updates. This was diagnosed as a plugin compatibility issue where a plugin extending Shopware's ConfigurationService did not implement new methods introduced in Shopware 6.7.16 (specifically getResolvedSystemConfigDefinition). This led to ConfigurationService::$bundles being accessed before initialization in the original Shopware class.
The affected plugins were identified as "PDF & E-Rechnung automatisch per E-Mail" (AutoInvoice) and "Tickets for Shopware" from GOLLE IT. The developer promptly released updates (AutoInvoice 6.6.19 and Tickets 3.17.2) addressing both issues. The config.xml structure was corrected, and the ConfigurationService extension was updated to cover the new methods.
For users experiencing similar issues, the thread provides valuable diagnostic commands:
- To find plugins with leading comments in
config.xml:grep -lzP '^\s*(<\?xml[^>]*\?>\s*)?2026 Migrate My Store. All rights reserved.