FAQ
Are placeholders case-sensitive?
Section titled “Are placeholders case-sensitive?”Yes. {promoText} and {promotext} are two different keys.
Can a variable contain HTML?
Section titled “Can a variable contain HTML?”Yes. The Value field is a rich-text editor — bold, links, lists, images, raw HTML blocks all work. Be careful with HTML inside contexts that escape it (e.g. some product fields render < instead of <); test in the editor preview.
Can I use variables in email templates?
Section titled “Can I use variables in email templates?”The variable picker appears in the email template editor, but the storefront replacement runs as part of CMS / product / category rendering. Whether the resulting email actually uses the replacement depends on which mailer template path you are on. Test with a real send before relying on it for production emails.
Can I use variables inside Twig templates I wrote myself?
Section titled “Can I use variables inside Twig templates I wrote myself?”The plugin’s replacer is a public service (P2Lab\DynamicVariables\Service\DynamicVariableReplacer). Inject it into your Twig extension or controller and call it on the string you want to resolve. This is an advanced integration — not part of the default install.
Are variables synced between staging and production?
Section titled “Are variables synced between staging and production?”The plugin stores variables in the standard Shopware database tables. Use whatever you already use to move data between environments (DB export, migration scripts, deployment tooling). There is no built-in export / import.
Will an inactive variable still be listed in the picker?
Section titled “Will an inactive variable still be listed in the picker?”No. The picker shows only active variables that are allowed in the current scope.
What happens if I delete a variable that is used on a CMS page?
Section titled “What happens if I delete a variable that is used on a CMS page?”The CMS page keeps the literal {key} text. It renders as raw text on the storefront. There is no automatic cleanup of references — deleting a widely-used variable is high-impact, so don’t.
If you want to retire a variable, prefer:
- Toggle Active off — placeholders render as literal text but the data is preserved.
- Or: keep the variable but switch its value to the new copy you want everywhere.
Does the plugin store anything outside the database?
Section titled “Does the plugin store anything outside the database?”No. All variable data lives in the plugin’s tables. The per-variable CSS / JS is stored as a string field, not as a separate asset file.
Can two variables share a value?
Section titled “Can two variables share a value?”Not directly — each value belongs to one variable. To share content, define the shared content in one variable (e.g. {shopName}) and reference it from other variables via nesting: {tagline} = Powered by {shopName}.