Skip to content

Administration is broken due to a critical error with removed theme config values #9988

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
7 tasks
timo-haas-gh opened this issue May 30, 2025 · 1 comment
Open
7 tasks
Labels
needs-triage A newly created issue or PR that needs team assignment and/or prioritization. Platform(Default)

Comments

@timo-haas-gh
Copy link
Contributor

Shopware Version

6.7Rc5

Affected area / extension

Platform(Default)

Actual behaviour

If a theme config value is changed (and then stored in 'config_values') a critical error occured when the value is removed from the base_config (via. update for e.g.)
This is very critical because it denies the removal of outdated config values.

Thats because of a missing null check in the THemeService.php an the 'type'-key

Expected behaviour

A null check should be implemented.

How to reproduce

  1. create a theme with a configuration (theme.json)
  2. change the value in the administration (it changes the config_values)
  3. remove the value from your theme.json
  4. update your theme
  5. try to compile the configuration

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.
@timo-haas-gh
Copy link
Contributor Author

@marcelbrode i have seen that you have refactored the ThemeService.php and other stuff. So in the trunk the null check is implemented. Can you verify that the explained issue is solved and if the fix is implemented into the actual 6.7 release?
The issue can lead to serious problems when someone has old values from older theme versions stored in the database.

Thanks in advance :)

@github-actions github-actions bot added the needs-triage A newly created issue or PR that needs team assignment and/or prioritization. label May 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage A newly created issue or PR that needs team assignment and/or prioritization. Platform(Default)
Projects
None yet
Development

No branches or pull requests

1 participant