A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize request, please see:
Allow full customization of Application Storage Path
Merged
Certain customers already have an "application" folder for all of their application content for CMSource. Creating a second "Applications" folder in the path is confusing can make it challenging to sort/find source content.
The other half is they don't want an "application" folder period. they just want all content to be in "CMSource". - regardless of if it's a package application etc. Their standard is just that the folder name needs to match the name of the package/application.
This was mainly a requirement to differentiate between legacy packages we created and the new applications. You could also change the path to go back one level so it will use the existing applications subfolder as a workaround?
Gotcha, I think we will be able to look at this for a future update.
The other half is they don't want an "application" folder period. they just want all content to be in "CMSource". - regardless of if it's a package application etc. Their standard is just that the folder name needs to match the name of the package/application.
This was mainly a requirement to differentiate between legacy packages we created and the new applications. You could also change the path to go back one level so it will use the existing applications subfolder as a workaround?