- 🇺🇸United States bluegeek9
re-saving the view from UI will actually fix the schema for given view.
RC2 did not deliver upgrade paths for views, which it should.
I believe upgrade paths are only available for stable releases.
Note, workaround is to save both the name fields and the views that use these.
Originally reported by Dropa
RC2 did not deliver upgrade paths for views, which it should.
Say you have few submodules, each providing views that does use name field, now after RC2, tests for those modules will break due to schema errors like following:
Drupal\Core\Config\Schema\SchemaIncompleteException: Schema errors for
views.view.my_view:display with the following errors:
views.view.my_view:display.default.display_options.fields.name__given.settings.markup
variable type is boolean but applied schema class is
Drupal\Core\TypedData\Plugin\DataType\StringData,
views.view.my_view:display.default.display_options.fields.name__given.settings.output
missing schema,
views.view.my_view:display.default.display_options.fields.name__given.settings.multiple
missing schema,
views.view.my_view:display.default.display_options.fields.name__given.settings.multiple_delimiter
missing schema,
views.view.my_view:display.default.display_options.fields.name__given.settings.multiple_and
missing schema,
views.view.my_view:display.default.display_options.fields.name__given.settings.multiple_delimiter_precedes_last
missing schema,
views.view.my_view:display.default.display_options.fields.name__given.settings.multiple_el_al_min
missing schema,
views.view.my_view:display.default.display_options.fields.name__given.settings.multiple_el_al_first
missing schema,
views.view.my_view:display.default.display_options.fields.name__family.settings.markup
Now in order to fix that, the view that is being provided by the module itself of course needs to be updated, but for each module to also provide update for existing view is not supposed to be required. Instead name module should provide that update.
Edit: the update itself should be quite easy, since re-saving the view from UI will actually fix the schema for given view.
Edit 2: It seems that just saving the view itself does not actually change everything that is necessary, saving the corresponding fields individually will also change things.
Closed: works as designed
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
re-saving the view from UI will actually fix the schema for given view.
RC2 did not deliver upgrade paths for views, which it should.
I believe upgrade paths are only available for stable releases.