When attempting to attach larger files, in this case, 17MB....I'm getting this error, just as the attachment upload looks like it's completed (I first get taken to a blank white page, then a few seconds later to this page which displays the error - all within the pop-up)....and yes, I have message text already composed and awaiting to be posted...



Have disk space limits been instituted? I've never run into this before with files of this size? It should be noted I tried a few smaller sizes without a problem (a few KB, to a couple of MB). Or perhaps it's a timeout issue? But again, never seen this until now.

Please let me know asap, thanks.

Indeed. There is a 16MB limit on uploads.

Are you saying this is by design or for whatever reason it's been set this way temporarily?

If by design....I wasn't informed of any such limits being imposed and there's no mention of it in the "Forum Message Attachments" section of the Control Panel, in fact, as it has always stated in the "Limit Attachment Size:" section of the CP, it states quite clearly, "Specify an attachment size limit. By leaving this field blank, there will be no limit."

Is this going to affect my existing attachments that are over 16MB? They're still accessible, correct? This very much impacts the use of my forum as file attachments is the number 1 reason I use OT versus other hosted forums. I understand it can't be unlimited storage, but 16MB is way too low - 30MB would be acceptable.

If it's temporary...forgive my rant...and please let me know when this restraint is going to be lifted Also, can you please adjust the above error text to be more specific as to why it threw the error, instead indicating there was no message entered.

Thanks.

Please let me know the deal!

Bump!!!

The limit is 16MB. We may consider increasing it at a later date.

A warning message prior to upload may be an idea. Though this is the first occasion I can recall that anyone has butted up against the 16MB limit on attachments.

In future, please can you inform us of changes to the backend...has anything else changed that hasn't been announced?!?!

What's happened to you guys...you used to be anal about informing customers of changes, now it seems, it's the customer who has to stumble across something before it's mentioned. Plus you seem more concerned with the UI these days vs. working production functionality...(as evidenced by what you just said, "A warning message prior to upload may be an idea"). This feels like a real change in mindset....at least from this customer's standpoint.

I'm trying to stay faithful to you guys, but you're not making it easy!

So...are my existing attachments that are over 16MB safe or are they in the bit bucket? And what about next week, during the data center move, will the >16MB attachments still be there, if the system is configured for only 16MB or less? At least let me keep those.......

Thanks

[This message was edited by dharrison on March 02, 2003 at 06:11 PM.]

Hi. FWIW the 16MB limit has been in place since day one. It's not something we've just changed.

I hear what you're saying about wanting 16MB+ attachments. But there are real good reasons _not_ to let that happen. E.g. It's open to abuse (overuse, hiving). And there are better ways of hosting large files.

quote:

---

FWIW the 16MB limit has been in place since day one. It's not something we've just changed.

---

So, the process to check file sizes was broken all this time? As I mentioned, since I first signed up back in 2000, I had always been able to attach larger files...the largest ever attached was 25MB (since been deleted).

Anyway...if you could create some meaningful warning message prior to upload...that is more of a priority for me now. Plus as requested previously...a status message indicating that the file is being uploaded (rather than just being left at the "Post" pop-up...with large files, you're there for quite sometime and it's too tempting for a regular user, to just hit the "Post Now" button over and over or worse, just give up and close the pop-up entirely!!

Thanks.

[This message was edited by dharrison on March 02, 2003 at 07:10 PM.]