Notice about views.view.aggregator_rss_feed.yml

Hey 👋

The contents of the file can be imported via copying it's content and pasting it in the 'single import' form from admin/config/development/configuration/single/import after selecting 'View' as the configuration type and then 'aggregator_rss_feed' as the view - just leave the UUID from the existing one.

If you're using drush, you could also copy the contents of that file into your exported .yml file - again leaving the UUID from the existing one.

The drush approach would allow you to visit admin/config/development/configuration and see a diff between the two files - or you could also do this with git if you were using source control for your configuration files.

In terms of what changed - https://git.drupalcode.org/project/aggregator/-/commit/620743b3e053a660e... is the only change which is:

• Adding a sort
• Ensuring empty items aren't output

LR

Hello @larowlan,

Sorry for the late reply, I just saw your comment now. The GUI method may be more my level, though I do use Drush for the basics.

Within the GUI I'm not seeing Steps 3 and 4 as you've instructed, please you can clarify.

1. Navigate to admin/config/development/configuration/single/import
2. Select configuration type as "View"
3. 'aggregator_rss_feed' as the view
4. Leave the UUID

After selecting "View" as the configuration type in Step 2, for Step 3 there isn't an option to define or select 'aggregator_rss_feed' as the view (see screenshot), unless you mean to paste the contents on the views.view.aggregator_rss_feed.yml into the text box?

For Step 4, are you saying to leave the UUID (advanced) filed empty?

Also, does an import reset what is configured for the view, and if I choose to just leave the view as is will that be a problem for future module upgrades?

I'll try to explain the part about the UUID.

Hypothetical scenario:
Let's say you have an existing configuation object in your site. It could be a view or some module's basic settings. You decide that you need to completely overwrite it for some reason. It doesn't matter why. You just need to completely replace the existing contents of that configuration with something else - let's say it's a fresh copy of the configuration from the source module. So you take that configuration, paste it into the config importer, and hit Save. Drupal will cancel the import and display the following error:

An entity with this machine name already exists but the import did not specify a UUID.

I don't know the details, but I'm sure this is protection against improper configuration imports. Try it for yourself! It won't hurt anything because Drupal will stop it.

Now let's go back to your situation. You really do want to overwrite the existing view configuration, at least for the sake of testing. So you would copy the view config from https://git.drupalcode.org/project/aggregator/-/blob/2.x/config/optional.... But you can't just put it into the config import form like that. You'll get the same error I showed above. You also need the UUID from the existing view configuration. You have to add that UUID to the configuration that you're copying and pasting. Without it Drupal won't allow you to do the import.

I hope that cleared things up.