Problem/Motivation
Statistics module defines its own block type. The block settings used to be stored / managed by the module but then it was moved into the block. However migrate and the config schema was not updated. If you look for top_day_limit, top_recent_limit, top_all_limit, those are all only mentioned in config schema, default stats setting and migrations. Never used in code. Eg:
$ git grep "day_limit"
core/modules/migrate_drupal/config/install/migrate.migration.d6_statistics_settings.yml: 'block/popular/top_day_limit': statistics_block_top_day_num
core/modules/migrate_drupal/src/Tests/d6/MigrateStatisticsConfigsTest.php: $this->assertIdentical($config->get('block.popular.top_day_limit'), 0);
core/modules/statistics/config/install/statistics.settings.yml: top_day_limit: 0
core/modules/statistics/config/schema/statistics.schema.yml: top_day_limit:
Proposed resolution
1. Remove the extra config schema from statistics module
2. Fix migrate to not migrate block settings to global stats setting (it already does the block setting migration proper from the same source data in BlockSettings.php)
Remaining tasks
Review. Commit.
User interface changes
None.
API changes
None except useless config schema elements removed.
Beta phase evaluation
Comments
Comment #1
gábor hojtsyPostponed on #2391245: Resolve remaining misc issues with configuration schema fails.
Comment #2
gábor hojtsyActually we can produce a fail patch.
Also stats seem to be covered in the per block migration as well in BlockSettings.php:
Comment #3
gábor hojtsyActually this would be the whole thing.
Comment #5
gábor hojtsyComment #6
gábor hojtsyComment #7
penyaskitoBlockSettings is covering the migration and the clean-up looks good, RTBC.
Comment #8
penyaskitoComment #10
gábor hojtsyRerolled. #2391245: Resolve remaining misc issues with configuration schema fails landed, which is where I found this bug in the first time.
Comment #11
alexpottCommitted b388670 and pushed to 8.0.x. Thanks!
Thanks for adding the beta evaluation for to the issue summary.