- Issue created by @Shane Birley
- 🇵🇱Poland mahyarss
Thank you @shane-birley for reporting this issue and taking the time to provide clear reproduction steps. Your detailed report made it easy to identify and resolve the problem.
I've investigated the issue and created a patch that addresses the block configuration save problem. The attached patch resolves the issue where countdown block settings were not persisting after saving.
Could you please apply the attached patch and test it in your environment?
Applying a patch
Download the patch to your working directory. Apply the patch with the following command:
git apply -v [patchname.patch]Here's how to test:
- Apply the patch to the module
- Clear your site's cache (drush cr)
- Edit an existing countdown block or create a new one
- Make some configuration changes
- Save the block
- Edit the block again to verify your changes were saved
Please let me know if this resolves the issue for you or if you encounter any other problems. Your feedback is valuable to ensure this fix works properly across different use cases.
Thank you again for your contribution to improving the Countdown module!
-
mahyarsbt →
committed e4fc213d on 2.0.x
Issue #3545014 by shane-birley, mahyarsbt: Fix block configuration not...
-
mahyarsbt →
committed e4fc213d on 2.0.x
- 🇵🇱Poland mahyarss
I've tested the patch and confirmed it resolves the block save issue. The fix is minimal and only uncomments the essential parent::blockSubmit() call.
- 🇵🇱Poland mahyarss
Committed to 2.0.x-dev. Thanks @shane-birley for reporting this issue!
This will be included in the next release.
- 🇵🇱Poland mahyarss
Committed and pushed to 2.0.x-dev.
Thanks @shane-birley for reporting this issue!
Now that this issue is closed, please review the contribution record.
As a contributor, attribute any organization helped you, or if you volunteered your own time.
Maintainers, please credit people who helped resolve this issue.