Cannot save Views admin settings due to skip_cache error

Did you run updates? That setting was removed in 📌 Get rid of using 'views.settings':skip_cache in ViewsData Fixed

If you mean database updates, admin/reports/status shows them as already up to date and going to /update.php tells me there are no pending updates. Is there some other step I need to take?

I had the same problem on a site created 3 months ago. I think it was on 10.2 and updated to 10.3.

No pending updates. I'm not sure if they ran before or something else happened.

I fixed it with drush cedit. Edit views.settings and remove the skip_cache line.

The most likely way this could happen is if:

1. A site was originally installed on a version that had this setting, with config exported to the config/sync directory.

2. Site is updated to a version with 📌 Get rid of using 'views.settings':skip_cache in ViewsData Fixed applied.

3. Database updates are run, but then after that, the config is not re-exported to the config/sync directory.

4. Later on, config is imported - this would re-introduce the 'skip_cache' key that was removed in the update.

#2628144: Ensure that ConfigImport is taking place against the same code base → would prevent step #4, but doesn't help sites that have already got into this state.

Fixes are made on on 11.x (our main development branch) first, and are then back ported as needed according to our policies.

Same issue here on 10.3.6. I was able to fix it on my site by editing views.settings.yml and removing the line that said skip_cache: false and then re-running the configuration import.

#8 worked for me. D10.4

Same here, upgraded to 10.3. I think the removal of the skip_cache key was introduced since 10.2 in web/core/modules/views/views.post_update.php, function views_post_update_remove_skip_cache_setting.

Ref: https://git.drupalcode.org/project/drupal/-/commit/3f6c5710fc9d044bc34de...

I tried to simulate the case, but after skip_cache is cleared, there is nothing for config to export. Maybe that's why the config still exist in the system.
Of course, #8 resolve the issue.

1. Running drush, see the config
dev-www>drush config:get views.settings skip_cache
'views.settings:skip_cache': false

2. Running the code copied from views_post_update_remove_skip_cache_setting manually:
\Drupal::configFactory()
->getEditable('views.settings')
->clear('skip_cache')
->save(TRUE);

3. Clear cache and verify
dev-www>drush cr
[success] Cache rebuild complete.
dev-www>drush config:get views.settings skip_cache
'views.settings:skip_cache': null

4. Drush export
dev-www>drush cex
[notice] The active configuration is identical to the configuration in the export directory (../config/sync).
../config/sync