Composer configuration changes are not reflected
I am having trouble understanding how Composer works. After modifying the configuration YAML files and running run.sh and generate.sh, I do not see the changes reflected in the generated files. Could someone explain the correct workflow for applying these configuration changes and provide some guidance on how Composer is intended to be used?
Replies (1)
Hi Olivier,
Understanding
After modifying the YAML configuration files and running both run.sh and generate.sh, you're not seeing your changes reflected in the generated output.
Solution
This typically happens for one of these reasons:
1. Restart the preview server after YAML changes
The Flask preview server (./run.sh --debug) caches configuration when it starts. If you edit YAML files while the server is running, the changes won't appear until you stop and restart the server. Press Ctrl+C to stop it, then run ./run.sh --debug again.
2. Regenerate after view changes
If you modified Jinja template files (in views/), you need to run ./generate.sh again after the preview server is restarted. The generation script reads the current state of your configs and views at the time it runs.
3. Check the correct config file
- Global settings go in
config/app.yaml - Menu structure goes in
config/menu.yaml - Make sure you're editing the right file for the change you want
4. Verify the generated output location
After running generate.sh, check the export directory for the generated HTML files. The output path is typically listed when the script completes.
Typical workflow:
1. Stop server: Ctrl+C
2. Edit YAML config files
3. Restart: ./run.sh --debug
4. Verify in browser preview
5. Generate: ./generate.sh
Sources
- Metronic Composer Docs — configuration and generation reference
Next Steps
If the issue persists after restarting, share the specific YAML change you made and which file you edited. That will help pinpoint the problem.
This reply was generated by AI. A human will follow up if needed.