Skins and Modules
Off Topic
no, you only need to keep the very latest version.
What is happening is that initially you will have this structure
/modules/jrAudio/(all the module files)
then a new version comes out and the url /modules/jrAudio will turn into a 'symlink' to the newest version which will be put on
/modules/jrAudio-version-1.2.3
The main reason its done like this is because its quicker to copy all the files over from the main code repository to your server into the new directory /modules/jrAudio-version-1.2.3 then once they are all there change it to a symlink.
If instead the flow was to copy the files from the jamroom repository over directly to /modules/jrAudio/index.php or other file then if someone was using that at the time they could see errors.
If its just disk-space you're concerned about you can set the marketplace to just keep 1 version of everything at
ACP -> CORE -> MARKETPLACE -> GLOBAL CONFIG -> GENERAL SETTINGS -> MARKETPLACE VERSIONS
set it to 1.
If you're using the GIT version control system and you want to get /modules/jrAudio-version-1.2.3 back onto its main url of /modules/jrAudio/
then you can use the REBASE MODULE tool found at
ACP -> MODULES -> DEVELOPER -> DEVELOPER TOOLS -> GLOBAL CONFIG -> DEVELOPER SETTINGS -> ENABLE RESET TOOLS
Then
ACP -> MODULES -> DEVELOPER -> DEVELOPER TOOLS -> TOOLS -> REBASE MODULES
updated by @michael: 08/03/21 07:14:19PM