- Issue created by @aballa
- 🇺🇸United States flashwebcenter Austin TX
Thank you for your detailed report and for using the Solo theme.
After reviewing your description, I want to clarify that the “Save configuration” functionality is part of Drupal core and is handled by the form system itself. The Solo theme does not override or customize this form submission behavior in any way.
Based on what you’ve shared, the issue is not caused by the Solo theme. The settings form and save button are provided by Drupal, and the theme only provides additional fields or defaults (e.g., color settings, layout options) via the theme hook.
A few things you might try next:
- Confirm that the Solo theme settings form has not been altered in a custom module or by the sub-theme.
- Temporarily disable your sub-theme and try saving with Solo as the default theme to rule out custom overrides.
- Check if the Solo config is being blocked from saving by a contributed module (like Config Ignore or similar).
- Enable error reporting or check logs again after saving, to see if PHP or form validation errors are being hidden silently.
Again, thank you for bringing this up. At this time, there are no known issues in Solo version 1.0.19 related to saving theme settings. Please feel free to share any further findings.
Best wishes,
Alaa I have the same exact issue, this is a issue with the recent update Solo theme version: 1.0.19 I cannot save settings, and also it kicks the primary menu to the left and not centered, it react the same in the solo sub theme and the solo theme, if you disable the welcome message then you can save the setting how ever the primary menu is still kicked to the left, I never respond to the sites because the first thing is
QUOTE Again, thank you for bringing this up. At this time, there are no known issues in Solo version 1.0.19 related to saving theme settings. Please feel free to share any further findings. so I am sharing further findings I have reinstalled from backups to find just where this is and how i have come to the conclusion that upgrade Solo version 1.0.19 has issues that i cannot solve i easily duplicate it but I will be stuck on Solo 1.0.18 until it is fixed or a security threat. thank you for your time best wishes to all
- 🇺🇸United States flashwebcenter Austin TX
Hello,
Thank you for sharing these detailed findings.
I have tested Solo 1.0.21 locally and am not encountering these issues, which suggests the cause may be site-specific. Please try the following troubleshooting steps to help isolate the problem:
- Clear caches and rebuild CSS/JS aggregation (drush cr).
- Check logs under Admin > Reports > Recent log messages (/admin/reports/dblog) for any errors when saving theme settings.
- Temporarily disable contrib modules that may alter admin forms or configuration.
- Switch to the default theme (Olivero), then re-enable Solo and test again.
- Verify any custom CSS overrides in your sub-theme or custom module that could affect the primary menu’s alignment.
- Ensure there are no duplicate copies of older Solo versions present in your themes directory.
- I am also attaching a video demonstrating → my test with Solo 1.0.21 for your reference.
Please let me know what you find after these steps, and I will continue to assist you in resolving this.
Best regards,
Alaa Hi, thank you for the reply and the instruction to help fix the issue, I have found the issue, it is in the Fixed Search Block, removing the search from the Fixed Search Block area to another location fixed the menu hanging to the left side and now i can save settings in the admin section to modify my website, you cannot just disable the Search Block in the Fixed Search Block area, you have to remove it completely and place your search some place else in the webpage.
CLICK ON Structure, Click on Block Layout, Scroll down to Fixed Search Block, make sure there is No blocks in this region
Thank you and best wishes to all fweclan.com/drupal- 🇺🇸United States flashwebcenter Austin TX
Hi,
Thank you for sharing your findings, and I’m glad you resolved the issue.
I did test this as well: I removed the block from the Fixed Search Block region and also removed all blocks from all regions except the menu and content to test thoroughly. It is working fine on my end with these changes.
Best wishes,
Alaa