**Rec 03** - ❌ **METADATA ATTRIBUTE ERRORS**
❌ METADATA ATTRIBUTE ERRORS
If you are using PMM nightly48 or newer, this is expected behaviour.
metadata_path and overlay_path are now legacy attributes, and using them will cause the YAML Error: metadata attribute is required error.
The error can be ignored as it won't cause any issues, or you can update your config.yml to use the new collection_files, overlay_files and metadata_files attributes.
The steps to take are:
:one: - Look at every file referred to within your config.yml and see what the first level indentation yaml file attributes are. They should be one of these(collections:, dynamic_collections:, overlays:, metadata:, playlists:, templates:, external_templates:) and can contain more than 1. For now, ignore the templates: and external_templates: attributes.
:two: - if it's metadata:, file it under the metadata_file: section of your config.yml
:three: - if it's collections: or dynamic_collections:, file it under the collection_files: section of your config.yml
:four: - if it's playlists:, file it under the playlist_files: section of your config.yml
:five: - if it's overlays:, file it under the overlay_files: section of your config.yml
*NOTE: If you only see templates: or external_templates:, this is a special case and you typically would not be referring to it directly in your config.yml file.
Within the attached log file, go to the indicated line(s) for more details on the exact issue and take actions to fix.
For more information on this, [https://metamanager.wiki/en/nightly/config/files/#example]
1 line(s) with METADATA ATTRIBUTE errors. Line number(s): 1800