You are viewing this forum as a guest. Login to an existing account, or create a new account, to reply to topics and to create new topics.
Hi Nick
Is the software limiting the size of file uploads somewhere?
I can't upload files of more than a few mb, and get this error "413 Request Entity Too Large"
PHP setting are correct and upto 50mb, and I can upload using ccp8 on same server set up.
memory_limit = 1024M
upload_max_filesize = 50M
post_max_size = 50M
I have tried using the file upload option built into K9, and using a third party script in a html web page.
Any ideas?
Offline
You will fine the upload max size for the software as a setting under System / Component / Settings / Security Settings, but you already ruled out an issue with K9.
You're getting a '413 Request Entity Too Large' error. I assume this could only be coming from Apache, prior to PHP or K9 getting the request. Perhaps you've got a wrapper running on Apache that provides increased security (mod_security maybe) and is limiting max POST size. That would be the first place I'd look.
Offline
The upload works correctly in V8 on the same server, same script, same php version and settings.
Can you add a file upload option to one of the products on your developer site, just so I can try the same image and see the ajax response
Offline
https://kryptronic.com/DEV/public/Item/ … tar-Tuning
Let me know when you're done with it. 50MB upload a good idea for an Ajax form? I wouldn't do it based on that being a huge request, but if you can get it to work, by all means. The JS function that does the POST is postAJAX() found in {public}/media/scripts/common.min.js. The function that handles transforming your form data into the post data is in the same file, named formGetObject().
Offline
Your site doesn't work either. Try uploading a 5mb file and clicking add to cart.
I have 'resolved' my problem by excluding my file upload id from the formGetObject() here
jQuery('#' + params.formid + ' input[type=file]').each(function(){
The ajax response is too long as you are converting the image to a url.(I think!!!!)
Offline
I think file uploads on the dev site are limited to 750kb. You should really not mod the code to handle this - the files are too big. I'd change over to a non-ajax add to cart scenario - see Store / Component / Settings / Shopping Cart and Wish List and set 'Enable Ajax Add (Quick)' to false and you'll be good to go.
Offline
If I use the K9 File upload product option and upload a file of 27kb, you get a error with the data size.
Smaller files are ok because enough data is received to proceed, but if you view firebug > net > xhr >post, you will see an error around half way down of the response:
POST data request size limit has been reached by Firebug
I got this on your site for tiny images and larger images
Offline
Right, if you're using Ajax for the add to cart processing. At some point the files become too big to process via pure Ajax and you need to leverage something else like flash, which we won't do. Instead, for larger file uploads you can turn off the Ajax functionality (this doesn't disable the auto-price updating, just the add to cart itself). See my post 6.
Offline
I think I prefer having the images stored on my server and bypassing the data image conversion in common.min.js, than disabling the ajax add to cart.
I would think alot of users who utilise the file upload field in K9 would be expecting files larger than 1mb to upload without any issue and without having to disable the ajax add to cart first??
Offline
I would think alot of users who utilise the file upload field in K9 would be expecting files larger than 1mb to upload without any issue and without having to disable the ajax add to cart first??
Same-page ajax add to cart is a new feature in K9 so we'll have to wait and see how it's received. Most clients love it as it's a conversion maker, especially in product listing view. When the function was built it was noted that it may not be usable for file uploads, thus the setting to disable/enable it as needed. It will allow that 50 meg image upload option, it just won't work via Ajax, unless your settings are right. You set post_max_size, I wonder if there was another setting for variable max size you missed.
Offline