BoldMinded acquires Ansel, support ending for all add-ons. BoldMinded acquires Ansel, support ending for all add-ons. Read More →
Support has been discontinued. Issues remain available as an archive. Support has been discontinued. Issues remain available as an archive.
Ansel saves processed images in the wrong directory
#236 opened by Jules
Description
The original uploaded images go to the correct directory. But the processed images do not. Their NAME shows up in the right EE upload directory but with broken links. The actual processed files are saved in the root directory
Replies
- TJ Draper
Replied 2/19/2024 3:49 PM
Hi, could you share the settings on both of the upload directories (original uploads and processed images)?
And could you also share the settings for "Upload Directory" and "Save Directory" that you have set for the Ansel field in question?
Thanks TJ
- Jules
Replied 2/19/2024 6:05 PM
Thanks! As you probably suspected, answering your question helped me to discover the issue. I forgot to set the upload path. It still said {base_path}/ and nothing else.
While I'm here, could you tell me what a "cover field" is and what it is used for?
- TJ Draper
Replied 2/20/2024 10:47 AM
Yeah, my suspicion was an incorrect path setting. 🙂
How you use it is really an implementation detail. Or you can opt not to use. You can also opt to show a different label to the user (in the documentation, in the screenshots, or one of them anyway, you can see I set the label to "favorite image"). The idea of the "cover" image, however, was that you might want to designate a particular image to represent the set. That was the idea behind making that field available. But I made it flexible in its use.