Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

oc-1510 - Wrong maximum possible upload size in Admin panel of web interface #856

Closed
msrex opened this issue Dec 12, 2012 · 3 comments
Closed

Comments

@msrex
Copy link

msrex commented Dec 12, 2012

From http://bugs.owncloud.org/thebuggenie/owncloud/issues/oc-1510 and http://bugs.owncloud.org/thebuggenie/owncloud/issues/oc-2008

This is not fixed, is still a bug in v4.5.4 and stable45, and very visible. Sorry @karlitschek :)

Description:
The admin panel always shows PHP_MAX_INT as maximum possible upload size. See also this forum post.

Reproduction steps:
As administrative user, go to the Admin Panel. Next to "Maximum upload size" you will see 8589934592 GB. Expected: upload_max_filesize (or free disk space) - at least something reasonable, or nothing at all, should be shown instead.
#3 Comment posted by Frank Oct 02, 10:51

This is no longer visible in 4.5

The issue was updated with the following change(s):

This issue has been closed
The status has been updated, from New to Closed.
This issue's progression has been updated to 100 percent completed.
The resolution has been updated, from Not determined to RESOLVED.

#4 Comment posted by Randolph Carter Oct 11, 22:23

Don't want to be pedantic, but this still is an issue in 4.5. Just updated to 4.5 and it still shows the same value as stated in the description!

@ghost ghost assigned DeepDiver1975 Dec 26, 2012
@DeepDiver1975
Copy link
Member

On a 32bit OS/PHP the max possible is 2GB - on a 64bis system 8589934592GB will be displayed.
But this is stable45 related - in master we have a different behavior 7f2208b#commitcomment-2359483

I'm question the need of this maximum possible value as we neither validate it not it seems to be related to any real technical barrier.

Asfar as I can tell: it's pointless - let's drop it!

@icewind1991
Copy link
Contributor

I think it's best to only show the max possible size for 32bit systems, since the 64bit limit is completely irrelevant for all intents and purposes.

Free disk space is not an option since it's subject to change

DeepDiver1975 added a commit that referenced this issue Dec 28, 2012
for a 64 bit system we have no such limitation
refs #856
DeepDiver1975 added a commit that referenced this issue Dec 28, 2012
for a 64 bit system we have no such limitation
refs #856

Conflicts:
	apps/files/templates/admin.php
DeepDiver1975 added a commit that referenced this issue Jan 2, 2013
@DeepDiver1975
Copy link
Member

fixed in master and stable45 - will be part of 4.5.6

@lock lock bot locked as resolved and limited conversation to collaborators Aug 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants