• Welcome to the Chevereto User Community!

    Here, users from all over the world come together to learn, share, and collaborate on everything related to Chevereto. It's a place to exchange ideas, ask questions, and help improve the software.

    Please keep in mind:

    • This community is user-driven. Always be polite and respectful to others.
    • Support development by purchasing a Chevereto license, which also gives you priority support.
    • Go further by joining the Community Subscription for even faster response times and to help sustain this space
  • 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

3.5.5 - external storage not active even active selected; storage url not shown; images output as 60

Status
Not open for further replies.
choksw

choksw

Chevereto Member
Hi Rodolfo,

I confirmed the following as I downgraded and reinstalled 3.5.4.

The following needs to be checked out (for 3.5.5):

1. External storage set up and active ticked but unable to upload to external storage. At the same time, storage url not reflecting in embed codes

2. original images uploaded have permissions 600 and not viewable. However, thumbnails created have readable permissions.
 
Before confirm something you have to make sure that it happens outside your installation and that is not a config/external issue. The demo is running 3.5.5 with an FTP as storage and the uploaded images are not output as 60 so I respectful ask you to avoid using the term "confirmed" because you can confuse other users.

1. The embed codes will be reflected only for the images uploaded to that storage. It won't do anything to the existing images. So if you are saying that you can't upload to the external storage I'm assuming that you believe that activate an external storage will be reflected in the old uploaded images which won't happen.

2. The FTP method uses the same put (FTP STOR) operation for all files, there is no special permissions set for each one of the images. The images are stored in the temp folder and later they are pushed directly to the FTP server. Is rare that a file gets readable permissions and other don't. To understand what is going on a several things must be tested and for that I need the FTP info, your website info, your website FTP etc.
 
Last edited:
Hi Rodolfo,

Apologies for the wrong choice of words...

Yes, I understand that embed codes for storage url will only work if the images are uploaded to external storage. Let me rephrase the scenarios:

1. No external storage, just purely upload to local storage --> original-image.jpg has permissions of 600. Thumbnail has 755 (I need to confirm this). Permissions of 600 is checked via filezilla FTP and cpanel file manager. Hence, original image is not viewable on frontend.

2. I have S3 set up, have not tried FTP storage. After S3 is set up and marked "active", uploading of files does not get stored in S3, but will store in local storage. And hence, embed codes reflect local storage url, and not external storage url.

I would love to share FTP details but I have currently downgraded to 3.5.4 as I need to set up image sharing urgently for my ecommerce site! sorrryyy and thanks for all the quick replies, really appreciate it!
 
1. Make sure that PHP has the right witting permissions. The system even tries to fix that in class.upload.php:
PHP: 
@chmod($this->uploaded_file, 0644);
The thumbs and medium sized images are generated using the class imageresize which creates a file from scratch. Most likely PHP can create files with the right permissions but it can't move a file and then set the 0644 permission. This is at server layer, if the files are 0600 and not 0644 is because PHP can't set group and public permissions. This always happen with hostings that rely in directory permissions rather than process permissions.

2. That's weird. I'm also seeing that in the demo but not in the local dev website. I will dig it.
 
Last edited:
Is because of the quota. I forgot to add a case to consider 0 or null as unlimited so the thing is not considering that case and assuming that the storage server is full. Try to put something like 100 GB for now, I will fix the case for the next version.
 
Last edited:
Status
Not open for further replies.
Back
Top