Skip to content

Conversation

@theuros
Copy link

@theuros theuros commented Jun 3, 2025

“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.

Added option to generate path by resource ID => For example 234 goes to 2/3/4/

This is useful to quick find any file by resource ID
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant