File Field Broken?

I have the same issue, running 5.2.2 now and no change.

I also have this issue on v 5.1.3 as a clean install as well as auto upgraded versions.

It’s not a known bug and I’m not able to replicate. There is a known issue with MSM and file upload fields- directories are site specific in the CP, which can cause issues using file fields across sites. But otherwise, it should be working.

First, check that you can upload to the directory via the file manager. Then, make sure the file field is using a directory you know you can upload to in the file manager. If there’s still nothing, take a look at the network traffic using your browser developer tools and see what the response is you’re getting, if anything.

It’s definitely working for the vast majority, so something odd must be going on.

Robin, I can successfully load images to all folders in the file manager. The only changes to my 7 ee 5.1 sites has been an auto upgrade to v 5.2.2 - I have a site running 5.1.3 that has this same issue and is an empty install.

I have read in other threads that I can remove certain mod_securities to fix the issue - but that seems odd to have to update those settings.

What would you advise for me? Thank you.

I would expect mod_security/server issues to affect the file manager as well. Try it with one of the native avatars EE ships with. They’re tiny. Upload it via the file manager, make sure it’s ok. Delete it. Upload the same image via a file field in a channel entry.

If it fails- you’re getting to the part where you’ve chosen a file upload directory (same one you already tested in file manager) and you drag the image over and- it spins. No javascript errors? Anything interesting in the headers?

Aha- I got a closer look at one site running into this, and it was mod_security objecting to the format of some of EE’s assets, namely some combo_load javascript. Which was causing a javascript error and breaking the field.

Use your dev tools and look at the network traffic when you open an entry with the file field- see if you’re getting any resources that fail to load- 406, 500, whatever. I’m betting that’s it. In which case, check with your host and let them know the url that’s tripping the filter. They should be able to adjust the security check.

I do wonder what exact pattern is causing the problem- if you find out, let me know.

See my reply on this thread: link

In my case it has to with “/cp” being in a request, which on Linux is a copy command line and could potentially be used to do harm… which is why my hosting provider blocks it