FriendsOfFlarum upload, the intelligent file attachment extension

IanM

1.0.0

Address issue introduced in the beta 16 version which made it very difficult to extend additional file templates FriendsOfFlarum/upload281
Flarum 1.0 ready

Installing

composer require fof/upload:"*"
php flarum cache:clear

davwheat

IanM

Phoar! Great work updating this... I wouldn't have gone anywhere near it with a 10 foot barge pole (and not just because it's mainly PHP).

baolinh_vn

IanM thank you !!!!

edev

IanM So better to wait for v1.0.0 Flarum release and than fresh install the extension right?

- fof/upload 1.0.0 requires flarum/core ^1.0.0 -> found flarum/core[dev-master, 1.x-dev (alias of dev-master)] but it does not match your minimum-stability.

Thanks!

Ffuser1

Feature request: automatic image conversion and compression to web suitable format to reduce page loading time.

Hari

Ffuser1 Goto GitHub and open feature request. I think someone already requested this erlier .

clarkwinkelmann

Ffuser1 there is already a setting to resize the images (based on width and height)

I think we also have an event you can hook into to apply additional compression from your own code.

IanM

edev Correct, this version of the extension is for Flarum v1.0.

You can always install the latest version compatible with your installation using: composer require fof/upload:"*"

gyigi

Excuse me, im using imgur in this extension, but i dont know how to set it.
i've already input my client id,and that's all?
btw, i'm in china and will there be a way to get to it in china without a vpn
@luceos thanks.

TheRandomCrafter83

How would I go about allowing the uploading of Text Files, Zip Files? I may be blind as a bat, but the configuration page isn't very intuitive at all. I would rather store all files on my own server, but cannot for the life of me figure out how to do this.

clarkwinkelmann

ihhddis what's the error in the console?

It's normal to see method_not_allowed when visiting the endpoint since it's a POST endpoint but your browser will make a GET request when visiting manually. The error in the console or in the log file is the important one.

TheRandomCrafter83 I know it's not easy and unfortunately we don't ship with a list of examples. But if you scroll higher in the discussion I think those file types have been discussed in the past.

The easiest is to create one line with the MIME for each of the files and select the same template. More advanced users can try to combine the MIME types into a single regular expression but that's not required.

ihhddis

Has anyone managed to get this to work with BackBlaze B2? It is supposed to be 100% compatible with S3 but I can't get it to work.

In the console it generates an error in /api/fof/upload, if I go to that address it says the following:

{"errors":[{"status": "405", "code": "method_not_allowed"}]}

ihhddis

clarkwinkelmann The error in the console says this:
Failed to load resource: the server responded with a status of 504 ()
or
Failed to load resource: the server responded with a status of 500 ()

I have looked at the logs and found this plays constantly:

Next Aws\S3\Exception\S3Exception: Error executing “PutObject” on “Applicationone/2021-05-30/1622383429-672217-cookie.png”; AWS HTTP error: cURL error 6: Could not resolve hos$

"Applicationone" is the name I put in the "bucket" field of FoF Upload should I put something else? I put the name of my bucket of B2.

clarkwinkelmann

ihhddis AWS HTTP error: cURL error 6: Could not resolve hos$

I'm not familiar with that hosting service, but this error seems to indicate some sort of DNS issue. Are you able to resolve the custom Amazon S3 domain from the server command line? For example with dig <domain>

ihhddis

Is there any guide or something for BackBlaze B2? The guide on the S3 github wiki doesn't work because in B2 you can't edit the policy in text, I've been trying for 2 days and it's been impossible for me.

ihhddis

clarkwinkelmann I have made the dig, should I have a 1 in AUTHORITY?

I got this:

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64210
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

EDIT:

This is the complete error, it happened to be above before the other one, it happens when uploading an image:

[2021-05-30 21:01:28] flarum.ERROR: exception 'Aws\S3\Exception\S3Exception' with message 'Error executing "PutObject" on "//applicationonetestn./applicationonetestn/2021-05-30/1622408488-516791-cookie.png"; AWS HTTP error: cURL error 6: Could not resolve host: applicationonetestn (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://applicationonetestn./applicationonetestn/2021-05-30/1622408488$

GuzzleHttp\Exception\ConnectException: cURL error 6: Could not resolve host: applicationonetestn (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://applicationonetestn./applicationonetestn/2021-05-30/1622408488-516791-cookie.png in /var/www/flarum/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php:210

After trying to read the error I'm confused, I don't understand those URLs that it generates in which it uses applicationonetestn, in FoF Upload configure in the bucket field of the S3 settings: applicationonetestn

Should I put a URL in the bucket field and not the plain name? Even if I put the URL, it doesn't work either.

ihhddis

I have configured S3 Browser and it has worked without problem, I can sync local folders and send the content to the B2 bucket, during the configuration I have discovered that the BackBlaze S3 compatible API only works with V4 signature, maybe this is the problem but there is no setting to specify the signature type or maybe I have not seen it, do I have to modify some text file?

Darkle

Is it possible that the content uploaded through FoF Upload is saved in a folder within the bucket? Just as it does locally?

Currently it's saved in the root of the bucket in folders like this 2021-05-31/ and I'd prefer to save it in assets/2021-05-31/ or uploads/2021-05-31/

clarkwinkelmann

Darkle it's not an option at this time unfortunately.

Ideally we should rewrite the S3 adapter at some point to account for more use cases. It was originally just designed for basic S3 support. Some features have been PRed by the community but we aren't well equipped to test all of the situations.

To comment back on earlier issues I don't even think any of the FoF developers ever used S3 compatible hosts with the extension so our ability to help with that feature is very limited.

Our focus in the future will rather be on allowing custom adapters instead of adding new or more options to existing adapters. It's easier to maintain a good API instead of having to test 10+ drivers and various paid hosting services on each update.

Darkle

With clarkwinkelmann comment I decided to do some research on adapters and try to get this, after a few hours of experimenting I have managed it, it was actually quite simple but most of the time I was looking in the wrong files.

To change the save path of the images uploaded through FoF Upload to our bucket we will have to do the following:

Step 1: From the terminal on our flarum installation

cd /vendor/fof/upload/src/Adapters/

Step 2:

nano Flysystem.php
nano -l Flysystem.php (to list the lines of code)

Step 3: On line 84 of the Flysystem.php file we will change this

 79  protected function generateFilename(File $file)
 80     {
 81         $today = (new Carbon());
 82
 83         $file->path = sprintf(
 84            '%s%s%s',
 85             $today->toDateString(),
 86             $this instanceof Local ? DIRECTORY_SEPARATOR : '/',
 87             $today->timestamp.'-'.$today->micro.'-'.$file->base_name
 88         );
 89     }

'%s%s%s' --> 'uploads/%s%s%s'

(In this example the images will be saved inside the root folder of the bucket "uploads" you can change this to your liking)

Step 4: Done! check that the uploaded images are saved in your bucket in the new folder

« Previous Page Next Page »