- Issue created by @dtrdewaele
- 🇮🇱Israel jsacksick
Could it be due to this change? 🐛 Fix wrong config schema definitions for @AdvancedQueueBackend plugins Fixed . Can you see if reverting the change makes a difference?
Did you define a custom backend plugin?
- 🇧🇪Belgium dtrdewaele
Reverting that change fixes the issue indeed.
I have not developed the project myself, but as far as I can see, there is no custom backend plugin. All our queues use Database as backend as well. - 🇪🇸Spain qtarant
I have exactly the same problem. Now I fixed temporarily reverting changes. Is there a more "definitive" fix?
- 🇪🇸Spain qtarant
I have checked that in the last version 1.2 changes are reverted, but when I do a clear caches operation I continue getting the same error.
- 🇪🇸Spain qtarant
Ignore my comment #5 because I thought the changes were reverted but no.
- First commit to issue fork.
- 🇸🇬Singapore vhin0210
vhin0210 → changed the visibility of the branch 8.x-1.x to hidden.
- Merge request !22Issue #3469869: Issue with configuration schema "advancedqueue.backend.[id]" → (Open) created by vhin0210
- 🇸🇬Singapore vhin0210
Deleting
advancedqueue.plugin_type.yml: plugin_configuration_schema_idworks for me.
- First commit to issue fork.
- 🇬🇧United Kingdom alexpott 🇪🇺🌍
alexpott → changed the visibility of the branch 3469869-issue-with-configuration to hidden.
- 🇬🇧United Kingdom alexpott 🇪🇺🌍
@vhin0210 that removes the config schema from the plugin making it hard to have a plugin with correctly typed properties. I've create a new MR which fixes and tests the Plugin module integration. As the old MR is a workaround rather than a fix I've hidden it.
- 🇬🇧United Kingdom alexpott 🇪🇺🌍
The test-only run proves the test catches the error - https://git.drupalcode.org/issue/advancedqueue-3469869/-/jobs/2990860 and the fix, therefore, fixes it.
-
jsacksick →
committed a8864851 on 8.x-1.x authored by
alexpott →
Issue #3469869 by alexpott: Issue with configuration schema "...
-
jsacksick →
committed a8864851 on 8.x-1.x authored by
alexpott →
Automatically closed - issue fixed for 2 weeks with no activity.