I have added a channel form with file upload for images and am getting the error “avatar: The file you are attempting to upload is larger than the permitted size.”.
I’m trying 5 different image files 1 @ 800kb, 1 @ 1.2 MB, 1 @ 2.8MB, 1 @ 3.5MB and 1 @ 5.8MB. Each of these give the message that the file is too big even the 800kb file!!????
All the usual checks have been performed … - The directory on the server has 777 permissions - I can successfully upload the same files in the CMS to the same directory - PHPINFO shows that ‘upload_max_filesize’ is set to 64MB and ‘post_max_size’ is also set to 64MB
In my console I see the following error with 403 forbidden message. Does this give any info on what’s going on? POST ADDRESS?RET=https%3A%2F%2FXXX%2Fregister%2Fstep1%2F40&URI=register%2Fstep1%2F40&return;_url=%2Fregister%2Fstep2%2F40&author_id=1&channel_id=1&entry_id=40&ACT=1&meta=0DVFM7pXfghG8kYAXZl%2Bjdr%2FOBkD4rBhuGLCmRavueU5JfDblap71R4xfvAQPMBbPtwTHc36I25EmTU7zxsF5VxTX8vDw7tS3UFMe3xSVf6tf0GgYoGC1s4lmsvKT3SmLp54q0ch5g8k5ourEol4FMnfEXD2QnvED8vPsWjce94eoHzAZolS4RvYe5yWWbm5AlrG46b4BiyOxr5ZiBdpwjImUMR9T39n35DoHcq3YOFwLY3fyCf6hVhgCx6p2SDenkZeA1PAbT4CS2o78DYd%2FthAva5dm4pkrIZIAsLD%2FBrW1WA3RBFJB5b7eVJH4UvXnH8j92D%2BIlek%2Fc9mZVGvfttNTNnc%2F655thJyU%2BKUmlBXG%2FU2srsq6Jgh8tX9x70z2RWQ2KxIz2L3IiX7D19lOzpvbGWFQnnmvSxkaajo4bk%3D&return;=%2Fregister%2Fstep2%2F40 403
It’s now been 2 days fighting this and searching online for solutions but I can only find posts about EE V2 and I’m running EE V5..3.2
If anyone could possible opint me in the RIGHT direction that would be appreciated.
It’s completely beaten me.
Ok I have fixed the issue…
It was due to my custom field being called avatar.
I changed the name of the field to My Avatar and short name my_avatar and all started working with no errors.
Wow, 3 days I was trying everything from changing server settings to a million different htaccess doc rules and more and it was just because a custom field for entries was called ‘avatar’.
Ouch- and good catch Rob! I can see how the variables could get confused- though it is an odd way for the error to play out. Probably any way it played out would be odd.
I’m thinking we just flat need to make that an invalid field name, though there are a number of globals that we don’t block.
I’ll bounce it around with the team, but I’m thinking a validation check on that would not be untoward.
huh? lol he thought I was uploading to member profile 😊
It was I that discovered the file name causing the issue