Shopware Troubleshooting logo

Shopware Troubleshooting

Community
alpham8
shopware-troubleshooting

Use when a Shopware 6 change does not take effect or behaves unexpectedly — Twig overrides that do nothing, JS plugins that fail to initialise, admin assets not rebuilding, cache and performance problems, installation and upgrade failures, plus cross-cutting gotchas and the dev tools and bin/console commands used to diagnose them. Triggers on any "why isn't this working" Shopware question, unexplained cache behaviour, or .env.local and console command lookups.

Overview

Publisheralpham8
Repositoryagentic-webdev
Skill nameshopware-troubleshooting
Stars
4
Forks
0
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by alpham8 on GitHub. Read the source before you install it.

Installation

Install the Shopware Troubleshooting AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/alpham8/agentic-webdev/tree/master/skills/shopware-troubleshooting
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/alpham8/agentic-webdev.git /tmp/agentic-webdev
mkdir -p .claude/skills
cp -r /tmp/agentic-webdev/skills/shopware-troubleshooting .claude/skills/shopware-troubleshooting
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Shopware Troubleshooting in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Shopware Troubleshooting on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Shopware Troubleshooting is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Shopware 6 — Troubleshooting and Gotchas

See the shopware skill for the map of Shopware skills.

Common Gotchas

  1. SW6 DAL — never use raw SQL for entity data. Use repositories. Direct DBAL only for reporting/aggregations.
  2. SW6 context — always pass Context or SalesChannelContext down; never instantiate Context::createDefaultContext() in production code (bypasses ACL).
  3. SW5 cache — call $context->scheduleClearCache() in install/update/activate or changes won't appear.
  4. SW6 Twig — use {% sw_extends %} not {% extends %} for storefront templates.
  5. SW6 JS — PluginBaseClass comes from window, not from an import path.
  6. Don't call .first() on aggregation results — you need the EntitySearchResult object.
  7. Upsert requires an ID — without an ID, every upsert() call creates a new record.
  8. ManyToMany updates — update through the owning entity, not through the mapping repository.
  9. Custom entity tag — shopware.entity.definition entity attribute must match ENTITY_NAME constant.
  10. CMS initElementConfig() — must be called in both component AND config; skipping causes undefined config values.
  11. Store API abstract pattern — always create Abstract → Concrete → optional Decorators; inject AbstractXRoute in consumers.
  12. ArrayStruct + Twig .count — ArrayStruct implements \Countable. In Twig, .count resolves to the count() method (returns number of keys), not to a key named count. Use a different key name like total to avoid collision: new ArrayStruct(['total' => $value]).
  13. CMS slot getData() types — $slot->getData() for a category-navigation CMS element returns a Tree object, not a generic Struct. Use $data->getTree() (returns TreeItem[]), not $data->get('tree').
  14. Sidebar filter styles must scope to desktop — Custom SCSS for .is--sidebar and .cms-element-sidebar-filter .filter-panel-wrapper must be wrapped in @include media-breakpoint-up(lg). Without this, the mobile offcanvas filter panel breaks because display: block overrides the offcanvas hidden state.
  15. .nav-main is a sibling of .header-main — The main navigation bar is outside the header element in the DOM. It can be made position: sticky independently without affecting the header (logo, search, cart).

Common Problems & Solutions (SW6)

Plugin / Service Issues

SymptomCauseFix
Plugin not visible in admin after uploadplugin:refresh not runbin/console plugin:refresh
"Service X does not exist"Service not registered or container not rebuiltbin/console cache:clear, check services.xml
Entity definition not foundMissing service tagAdd <tag name="shopware.entity.definition"/>
Subscriber not firingMissing kernel.event_subscriber tagAdd tag in services.xml
foreach() argument must be of type array on plugin:refreshmanufacturerLink / supportLink set as plain stringUse locale-keyed object: {"de-DE": "...", "en-GB": "..."}
Custom field not in adminPlugin not updated after adding fieldbin/console plugin:update PluginName
Migration not executedNot run after installbin/console database:migrate --all

Template / Frontend Issues

SymptomCauseFix
Twig override has no effectWrong path, or using {% extends %} instead of {% sw_extends %}Mirror path from vendor/shopware/storefront/Resources/views/, use {% sw_extends %}
JS plugin not initialisingSelector not matching, or assets not rebuiltCheck data-* attribute; run bin/console theme:compile
Admin changes not visibleAdmin assets not rebuiltbin/console bundle:dump then npm run build (see shopware-ddev skill)
{{ myData }} undefined in templateData not passed via PageLoadedEvent subscriberSubscribe to correct *PageLoadedEvent, call $event->getPage()->assign()

Cache & Performance Issues

SymptomCauseFix
Stale data in storefrontHTTP cache not purgedbin/console cache:pool:clear cache.http
Config changes not activeCache not clearedbin/console cache:clear
Scheduled tasks not runningMessenger queue not consumedbin/console messenger:consume (or configure a worker)

Installation / Upgrade Issues

SymptomCauseFix
JSON_OVERLAPS SQL error on SW 6.6MariaDB below 10.11Upgrade MariaDB to 10.11+ (snapshot first!)
APP_SECRET missing error.env not set upCopy .env.dist → .env; bin/console system:generate-app-secret
White page / 500 after updatePlugin incompatible with new SW versionDeactivate plugins one by one; check var/log/
Build fails: paths[0] must be of type stringbundle:dump not run before admin buildRun bin/console bundle:dump first

Frequently Used Dev Tools & Plugins (SW6)

ToolPurpose
FroshDevelopmentHelperDebug bar, Twig block name overlay, DAL query log
FroshToolsAdmin UI for cache, queue, feature flags, log viewer
Symfony ProfilerHTTP request profiler (/_profiler), available in APP_ENV=dev
SwagPlatformDemoDataDemo products, categories, customers for fresh installs

.env.local for Development

dotenv
APP_ENV=dev
APP_DEBUG=1
APP_SECRET=your-generated-secret
DATABASE_URL="mysql://root:root@db:3306/shopware"
SHOPWARE_HTTP_CACHE_ENABLED=0
SHOPWARE_HTTP_DEFAULT_TTL=0

Useful bin/console Commands

bash
bin/console debug:container | grep product          # Find services by keyword
bin/console debug:event-dispatcher | grep cart      # Find events by keyword
bin/console debug:router                             # All registered routes
bin/console feature:config                           # Show feature flags
bin/console system:config:get SwagExample.config.myKey
bin/console system:config:set SwagExample.config.myKey value
bin/console sales-channel:list
bin/console user:change-password admin

Frequently asked questions

What does the Shopware Troubleshooting AI skill do?

Use when a Shopware 6 change does not take effect or behaves unexpectedly — Twig overrides that do nothing, JS plugins that fail to initialise, admin assets not rebuilding, cache and performance problems, installation and upgrade failures, plus cross-cutting gotchas and the dev tools and bin/console commands used to diagnose them. Triggers on any "why isn't this working" Shopware question, unexplained cache behaviour, or .env.local and console command lookups.

Why use Shopware Troubleshooting on TypingMind?

Because you install it once and use it with any model. Shopware Troubleshooting is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Shopware Troubleshooting in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/alpham8/agentic-webdev/tree/master/skills/shopware-troubleshooting. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Shopware Troubleshooting?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Shopware Troubleshooting?

As many as you like. As long as a model supports skills, you can use Shopware Troubleshooting with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Shopware Troubleshooting AI skill free?

It is published on GitHub by alpham8. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇