Update Upload.php #9
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
“Added an option to use {resourceIdPath}, which generates the path based on the resource ID (e.g. 234 becomes 2/3/4/).”
Clients often want to display a file from specific content in another place, but it is difficult to find it. If the path is defined with {year}, {month}, {day}, you have to know when the file was uploaded in order to locate it. Using {user} is also not practical. The best option is to use {resource}, because users can quickly find the desired files based on the ID. However, this approach causes problems when displaying the structure in the tree menu, since all folders are on the same level.
The prepared solution {resourceIdPath} converts the path into folders created based on the content ID, which allows easy searching by ID and ensures that there are no more than 10 folders on a single level at any time.