Our unique server environment is choking on the filemanager page.
I installed EE 2 (currently at build 20100810) for a client. It is unique in that it is installed on a college’s dedicated server, where it is maintained internally (as opposed to shared hosting which is my usual). There is not a lot of difference, except there are more safety measures in place, and a keener eye on file sizes and efficiency.
What we figured out was happening (as I was told by the administrators of the server) was that the output of the filemanager page was exceeding a server imposed limit. From my guy in the know:
The base64 encoded hashes that are used to reference the file path in the URLs for each file (delete, edit, etc.) are extremely large. Including the table markup, each file adds approximately 2 KB to the output HTML as pagination is done entirely on the server side. With the current number of files being listed, the output weighs in at a hefty 565.76 KB.
Their limit was 512kb and they have reluctantly upped it, but that will only suffice until about 200 more files are uploaded in which case the server will choke again.
Regardless, I’ve recommended they update EE to the latest build, although I have a feeling this particular issue won’t be resolved (looking through the change logs). Is there a solution to this problem? It may just be that I suggest to the content administrators that they avoid the filemanager page because of these limitations. Expression Engine is my jam, and I’m quite the proselytizer, but I can add this to my list of filemanager woes. Is this worth mentioning as a bug report or feature request? Even if most servers can handle it, it does seem this issue is worth bringing up in hopes of improvement.
Thanks!