How do I install the dev version? I am trying with
composer require fof/upload:1.3.0-dev.2
but it doesn't work.
FriendsOfFlarum upload, the intelligent file attachment extension
CyberGene but it doesn't work.
Either:
- make sure your composer.json contains
"minimum-stability": "dev"
and"prefer-stable": true
then you should be able to add it, or - add the entry manually in your composer.json under
require
"fof/upload": "1.3.0@dev"
I think
If you encounter an error, please share the error.
- Edited
luceos Thanks, I tried the first one, however I couldn't install by version/tag but had success with the branch name:
composer require fof/upload:dev-dk/map-files-posts
I'll test now.
A simple sanity check tells me it's probably working, it lists files, I checked some of them, seems they are indeed unused. Good job so far!
But it fails for the AWS S3 ones, I guess you have to implement that support, so I'll be looking forward to it since we switched from local storage to AWS S3 sometime ago and I will need to clean-up there too
Thanks for your effort and cheers!
- Edited
It stopped with this error:
In Manager.php line 85:
No adapter configured for aws_s3
- Edited
CyberGene I had this error in my first local test, to fix it I had to purge the extension, it must be something in the database and I couldn't find any other way, I think the problem arises if you already had an S3 adapter configured. Don't purge if you are in production.
I hope to be able to continue with the tests of this PR, that for now I have them stopped, with all this I tried to take the opportunity to check some things of the bucket and the CDN, and well, big mistake...
Darkle I’m working on a copy of my forum, not risking I’ll purge and reinstall the extension then.
- Edited
CyberGene in your local database try replacing upload_method
in the fof_upload_files
table from aws_s3
to aws-s3
. And see if it continues with that. So:
update fof_upload_files set upload_method = "aws-s3" where upload_method = "aws_s3";
Purging won't be a solution as we want to retain the files data in the database. Without it all references to uploaded files in posts will be lost.
Hey guys, very very very new and green to flarum.
Wanted to point out that this is still an issue making any non Amazon S3 compatible service i.e. R2, wasabi, B2 unusable for image storage as images cannot be rendered due to the URL hardcoding.
Is there a solution to this? I guess if not should be a warning that the extension doesn't really support S3 compatible storage for reads?
Maybe I missed an update.
I know you can set image size via pixel but it would be amazing to set a constraint of actual image size in megabytes or kilobytes and have it run a compression on the file.
Since I use. my site as a blog, I have to open each image in Photoshop and compress the image down to between 300kb-400kb which is what I aim for when uploading an image so I dont get hit too much on aws fees when people view the site. And it helps the page load faster for the user as well.
This would be awesome but maybe kill my server with multiple people compressing images at the same time...
Will there be a function at some point so that you can display unlinked pictures and delete them if necessary? This means that many images are uploaded and require an unnecessarily large amount of storage space without all of them being used. That would be really great
Hi, your extensions is not working well. I settings up the client id and is not working well. There a way to make FOF Upload working with imgur services?