Hi All,
Recently, I have been looking into using Amazon S3 as a media source within Modx. I would use S3 to store any files/images for my sites (in their appropriate buckets). I have a test bucket currently with one folder containing 1g of images (300+ items) that I plan to use on one of my sites, however MODX, both in the modx resource browser, and in the file-tree, timeout when accessed upon.
As it so happens, 1g worth of files is not a large amount for a site, and this is my largest holdup for primarily switching to using S3. I have looked into timeout issues, as well as any php timeout settings, but have found none that improved this.
Does anyone have any suggestions on how to speed things up?
Thanks!
Hmmm, you are storing the images in S3, right? Why do you have to download them to the server? Can't you just link them?
Hi Stefany,
I am not downloading the images. When I look in the resource tree in Modx, where the Amazon S3 files are located, upon opening the folder that the images are in, modx 'loads' for around 1 minute before showing an empty folder and doing nothing after that. I have tried accessing a folder with less files, and it works like a charm. I have attached a screenshot for reference.
Ok I understand. The images are being stored in S3 and you only get to "see them" in the filesystem when it crashes.
Check the errors logs, both PHP & the server one. Are you running Apache or Nginx? It could be a server timeout issue as well.
Incidentally, why do you want to browse the images via the MODX manager filesystem?
Hi Stefany,
My overall goal would be to host the images on the Amazon s3 server, and import them into MoreGallery (a gallery extra) into MoDx, which then uses pthumb to generate a thumbnail. The way you import photos into MoreGallery is through the Modx Resource Browser, which functions exactly as the modx file tree screen-shotted above. Right now, the same thing happens to the Modx Resource browser where it times out after a minute. I have checked the php error logs in modx and on the server with nothing triggering that has to do with this unfortunately.
OK so it times out and there are absolutely no errors in the errors logs? That's odd. Are you sure the errors are being written in the logs? You might need to enable it, especially if you are on a shared hosting sometimes they don't allow you to access the logs.
Try to force the system to spit out the error on the screen -> check the "debug" System Setting and set to -1
OK so it times out and there are absolutely no errors in the errors logs? That's odd. Are you sure the errors are being written in the logs? You might need to enable it, especially if you are on a shared hosting sometimes they don't allow you to access the logs.
Try to force the system to spit out the error on the screen -> check the "debug" System Setting and set to -1
Another thing you can do it duplicate the MODX website on your local machine and if it doesn't time out then it is the server's fault. Are you on Apache on Nginx? Nginx has low timeout limits.
