ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #shopware
Goal Establish a reliable method to verify that a restored Shopware 6 database and file system from a point-in-time backup contain complete and untampered data. Constraints Shopware 6 core provides no built-in backup/restore module; recovery relies on manual database dumps and file copies. Mixing backups from different timestamps causes media references to m
Theme color picker contrast validation missing WCAG AA enforcement Shopware 6 allows sales channel editors to save theme color configurations that produce contrast ratios below WCAG AA thresholds for header, button, and text elements. The color picker in Settings > Theme accepts any hex or RGB value without blocking the save action, leaving low-vision rea
Context The Shopware 6 upgrade wizard performs incremental schema migrations but provides no automated rollback mechanism. If a migration fails partway through, the database may contain a mix of old and new schema elements, and obsolete tables from prior versions are not purged automatically. Goal Determine the practical boundaries of recovery after a failed
Shopware 6.x Pagination Performance with Large Datasets Shopware 6.x uses a Criteria pattern for entity queries with offset-based pagination via Criteria::limit($size, $offset). When retrieving paginated results, the framework executes a separate COUNT query to calculate the total number of records, which can become expensive for large datasets, especially w
When bounding a query and paginating a large dataset in Shopware 6, the goal is to control the number of results returned per page to avoid performance issues. The repository layer’s paginate() method accepts a Page and Limit but does not expose a global default maximum. Developers must enforce limits manually. The Admin API applies a hard‑coded 1000‑item ca
Goal: Ensure that Shopware’s HTTP cache is fully populated before production traffic arrives, regardless of whether the filesystem or Redis adapter is used. Constraint: The default warm‑up mechanism only populates the filesystem cache; when the Redis adapter is enabled the cache remains cold until the first request, which can cause latency spikes. Additional
Context Shopware 6 stores all date-time values in UTC and relies on the Data Abstraction Layer (DAL) to convert timestamps to the configured system timezone during entity retrieval. This conversion is applied transparently when using repository methods or the storefront API. Problem Custom reporting queries that bypass the DAL and read directly from tables s
Integration boundary We are designing a headless integration against Shopware 6 that uses the two supported HTTP components: the sales-channel-scoped Store API (authenticated with the sw-access-key header) for storefront browsing and cart operations, and the Admin API (OAuth2 over /api/oauth/token ) for a backend service that needs to inspect and adjust orde
Our team is setting up a shared Shopware 6 development environment and needs one repeatable stack that every developer can spin up identically. Two documented options are on the table: dockware, which ships prebuilt Docker images bundling Shopware with its PHP, database, and web server runtime, and the newer devenv-based setup, which uses Nix to declarativel
doctrine
redis
docker