• Welcome to the Chevereto user community!

    Here users from all over the world gather around to learn the latest about Chevereto and contribute with ideas to improve the software.

    Please keep in mind:

    • 😌 This community is user driven. Be polite with other users.
    • 👉 Is required to purchase a Chevereto license to participate in this community (doesn't apply to Pre-sales).
    • 💸 Purchase a Pro Subscription to get access to active software support and faster ticket response times.
  • Chevereto Support CLST

    Support response

    Support checklist

    • ⚠️ Got a Something went wrong message? Read this guide and provide the actual error. Do not skip this.
    • ✅ Confirm that the server meets the System Requirements
    • 🔥 Check for any available Hotfix - your issue could be already reported/fixed
    • 📚 Read documentation - It will be required to Debug and understand Errors for a faster support response

Short URL Implementation

mrladeia

Chevereto Member
Website URL

Chevereto version
3.10.5

Description of the issue
I'd like to use a shorter URL, for example:

domain.com/Rzf.jpg


I think somebody already asked that. Do you already have some thought-out solution?
 
Last edited:
The system doesn't include any configuration that allows you to store images in the public root path.
 
@Rodolfo This configuration:

Salve only one folder? This case, only "i", not subfolders? Ok?

IaYKVdF9.png
 
Last edited:
You need to go to Settings ==> Routing and put "i" (without quotes) in the Image Routing field.

Can't see why it shouldn't work.
 
@Oakley This is to display the image on the site and not "direct link".

The question is, when I put in storage mode it saves everything in a single folder? All images in a single folder, in the server?
 
dashboard/settings/image-upload

But you can't configure the system to store images on the root path. You just can't.
 
This is a feature of your system!

I figured you could create subfolders inside the images folder.

Example:

Image URL: domain.com/Rtz.jpg

Path: public/i/R/t/z/Rtz.jpg

This would prevent everything from being in one directory.

--------------

So I could configure nginx to receive these requests in a php file that would be responsible for creating the image in the browser, but that would be very heavy. Php is responsible for everything.
 
Thanks, but your argument only works for those that list images using slow stuff like FTP. Everybody else is fine without extra folders.
 
Back
Top