I know this is weird but the result is that assets are browsable on disk in a coherent, human-readable way. I would like to do the same thing with assets attached through Vizy using something like this on the asset field:
Where .../2021/08/ferrari-365-gt4-3143/Story/IMG_1759_2021-08-12-154418_xtsf.jpeg is the desired result.
Is there any reason why this particular dynamic field (working and available to the entry assets field) wouldn't jive with Vizy? Should I give up on this or is there another way to tackle it?
Description I use a dynamic path for assets attached to entries, and it's a little bit unusual. It looks like this:
I know this is weird but the result is that assets are browsable on disk in a coherent, human-readable way. I would like to do the same thing with assets attached through Vizy using something like this on the asset field:
The result is always something like:
Where
.../2021/08/ferrari-365-gt4-3143/Story/IMG_1759_2021-08-12-154418_xtsf.jpeg
is the desired result.Is there any reason why this particular dynamic field (working and available to the entry assets field) wouldn't jive with Vizy? Should I give up on this or is there another way to tackle it?