Possible to change assets path?

Support
1

Hi, I have a question regarding assets and whether there is an alternative way to change the structure for where assets are stored.

Currently, we have a custom setup that works by linking to multiple internal assets, with each asset located under its respective route. Here are some examples:

/product-catalog
“downloads/product-catalog/someasset.pdf”
“/downloads/product-catalog/someasset.pdf”

/manuals
“/downloads/manual//someasset.pdf”
“/downloads/manual//someasset.pdf”

/doc
“/downloads/doc//someasset.pdf”
“/downloads/doc//someasset.pdf”

And so on…

All link names are static and must remain the same. We are now looking at migrating this site and its content to Squidex, but I am struggling to figure out how to achieve this.

At first, I considered using redirects, but Squidex’s asset management makes it difficult because all assets are placed in the same folder:

perl
Kopiera
Redigera
http:///api/assets/{app}/{idOrSlug}/{*more}

Is there any way to modify the asset structure? For example, if I have a schema named “downloads,” could all assets uploaded under this schema be placed under api/assets/downloads?

We have a self hosted squidex using the docker image

2

This is not directly possible. Squidex supports different storage providers and a flat list was just easier.

But I would create a mapping schemea with just two fields:

Path (Unique),
Asset

Squidex also supports custom IDs. They need to be unique across the app, but you could use something like that

redirects-{{path.Slugify()}}

as custom IDs. Then you can get the actual asset ID with single request to the primary key, which is faster than an extra field.