Replies: 1 comment
-
|
Hi, right: only the first level is supported; this is a limitation and not an error. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I'm quite new to FUXA, so I might be missing something — apologies if this has already been discussed.
I've been trying to organize my custom images by placing them in
/usr/src/app/FUXA/server/_images.However, it seems that only one level of subfolders is recognized by the editor. Is that correct?
Here’s an example of my folder structure:
/usr/src/app/FUXA/server/_images ├── SET1 │ ├── heating │ │ ├── heating1.png │ │ ├── ... │ │ └── heatingN.png │ ├── cooling │ │ ├── cooling1.png │ │ ├── ... │ │ └── coolingN.png └── SET2 ├── heating │ ├── heating1.png │ ├── ... │ └── heatingN.png └── cooling ├── cooling1.png ├── ... └── coolingN.pngFrom the editor’s
imageselector, I can only see the first-level directories (SET1andSET2), but not the nested folders (heating,cooling, etc.).It looks like deeper subdirectories aren’t being listed or recognized.
Is this a known limitation or an issue?
How do you usually organize your graphic assets to handle more complex image structures?
Thanks in advance for your help and for this great project! 🙏
Beta Was this translation helpful? Give feedback.
All reactions