Den genannten Ordner mal umbenennen und schauen was passiert. Cache leeren und Theme kompilieren zuvor hat nichts gebracht?
Rafael
24. Juni 2025 um 09:05
22
leider kein Erfolg mit dem Theme kompilieren. Bei dem Verzeichnis ändern muss ich warten bis eine Freund der die Zugänge hat es mal probiert.
R4M
25. Juni 2025 um 13:48
23
Im Zusammenhang mit dem Plugin „Shopware Commercial“ haben wir in einer Testversion einen seltsamen Effekt - im Backend kann man keinen Cache mehr löschen. Ist das Plugin deaktiviert, geht alles wieder. Den Cache leeren über Konsole geht auch, aber eben nicht im Backend.
Update:
offen 02:04PM - 18 Jun 25 UTC
component/core
extension/Commercial
priority/critical
domain/framework
### Shopware Version
7.0.0
### Affected area / extension
Extension:Commercial…
### Actual behaviour
With Commercial 7.0.0 (Shopware 6.7.0.0) installed and active, it is not possible to install other extensions. It will throw the following error message:
`Failed opening required '/var/www/clients/client13354/web18686/web/var/cache/prod_h7e50101cc0fc5807342ae54e068de98f/Container3xPUF6Y/removed-ids.php' (include_path='.:/opt/php-8.4/lib/php')`
The weird thing is, that this error message is not necessarily thrown all the time and even if it is thrown, it is not always necessarily preventing the action of the user.
### Expected behaviour
Extensions can still be installed, although commercial is active
### How to reproduce
1. Install Shopware 6.7.0.0
2. Install Commercial 7.0.0
3. Install any other extension (tested with Custom Products, CMS Extension and PayPal)
It's worth mentioning, that this error message does not seem to occur in all cases. However, this seems to be the most reliable way. It seems to be important, that the extension you want to install at step 3 has never been installed yet.
For example, I did not get this error message, when I have installed Custom products first, installed Commercial afterwards, and then uninstalled and reinstalled Custom products
### Definition of Done
- [ ] An automated test covers the fix.
- [ ] Integration/E2E testing in staging is done.
- [ ] Changelog markdown file created or updated in /changelog/_unreleased directory.
- [ ] Developer documentation written/updated.
- [ ] End user and/or developer documentation written or updated with clarification.
- [ ] Regression test created to ensure bug does not reappear, and automated regression tests pass.
- [ ] Code changes resolve the reported bug without introducing new issues.
