Module installation included modules

[Gerome]

Module development since v6.2

Starting with version 6.2 OXID does not automatically scan modules in source/modules folder. This means, that you can’t simply upload and activate a module anymore. From now on module metadata is stored in a yaml text file, where it will always be retrieved from, instead of the metadata.php file. This means in particular, that OXID does not notice your changes in the metadata.php file after you installed and activated the module. Therefore, if you are actively developing a module and you need…

Hello. Why are modules with metadata 1.1 in the folder of modules when downloading? the only difference between these modules and a new module is that the new has no information in the database, right?

[vanilla_thunder]

those modules are installed by composer during the "composer create project " command.
If you are using the prebuilt/precompiled archive for installation without composer, you are basically getting just the result of “composer create project …” command on a linux server.