-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MaxFileSize settings not working #4
Comments
Hi, |
Hi, What happen if you try with smaller files ? Like 5 to 10 mo. It's not showing me timeout, but Since those errors appears every time something bad is done, i dont't really think this is helpful. Have a good day :). |
Hi, |
I made the update annndd... : odtplus2dw : er_file_upload : Une erreur s'est produite avec le fichier envoyé : 1 In french this time :). |
I really don't know how to help you... The only place in code where MaxFileSize is used is in hidden tag name="MAX_FILE_SIZE" (I think), so if it is working OK there should be no problem |
The MAX_FILE_SIZE field seems to have no effect indeed. What you have to do is to allow you php.ini to upload bigger files. It is not enough to adjust the nginx config. You have to make sure
are big enough. Otherwise dokuwiki will reject the upload. You can check the value easily via the dokuwiki upload page. P.S.: This is of course still true for https://github.com/qky666/dokuwiki-plugin-file2dw |
Hi everyone.
DokuWiki is installed on a docker container (with nginx+php7).
Note : The max file size for nginx and php7 has been increased to 10M. BTW it works. I can upload photos largers than the originally 1M size (tried 5M and it works like a charm).
Now, what happen if i change the maxfilesize settings to 4097152-(4Mo) in the plugin settings.
When i try to upload files < 2MB it works.
When i try to upload files > 2 MB it fails, like before.
I have to say that the parameters is indeed changed (the form with hidden "name="MAX_FILE_SIZE" is showing me the "4097152" number not the default one.)
Thanks for your help.
Great Plugin btw.
The text was updated successfully, but these errors were encountered: