I found the solution.

I uploaded the file to ./files/incoming and then under the multiple upload link there is an add incoming tab that will allow you to add a file that you have FTP'd to ./files/incoming

Matt

Then again this doesn't work if the file is larger than 2MB.

The fact that File Manager used PHP as the only method to upload files is a horrible decision.

How am I supposed to use a file greater than 2MB? I know, I know, edit my php.ini file, easier said than done when you don't control the php.ini file, your hosting company does.

And what happens if you try and upload a file larger than 2MB, well Concrete5 doesn't give you an error or even a warning, it just goes off and acts like it's doing something? Seriously no trap for this?

The File Manager issue is seriously holding Concrete5 back. There has to be another way that everyone is used to like say FTP, and use File manager to just browse the files? I don't need version control on my jpegs, mp3, pngs, ect.

Matt

Have you tried placing a php.ini file in your websites root directory with your increased limit settings?

Does your host limit you from doing this?

This is a limit set by your host on the server you have your site setup on.

This is not a limit of concrete5 itself.

I shot an email off to the my hosting support, we'll see what they say. I know the limit is set by the php.ini file, so it's not directly and issue with Concrete5.

I am questioning why File Manager cannot just browse a directory structure, PHP is capable of that, and it just seams like Concrete5 is making this much more difficult than is should be.

Maybe there is a design decision where this makes sense, however I think the more natural way for it to work is for it to have the capability to browse a directory structure.

The current implementation is very limiting, and I'm not sure that is a good thing, and it may even be a deal breaker for some folks.

Matt