Store Community Support Documentation
JohnJr

I changed it from unlimited to a megabyte number and the result description didn't match on the profile page so I raised it up to 200,000 megs and look what is say on the profile page below.  The code calculation seems to work (although you can check it again) but the description of bytes vs megabytes is wrong as it is not using a phrase to describe the results but instead filesize(filename) php function.

Be the first person to like this.
#1

Dear JohnJr,

This issue has been fixed on v.4.7.9 already. Could you please upgrade your site on this version and check it?

Regards,

Hannah

Be the first person to like this.
JohnJr
#2

I would always update to the newest version before posting a bug :)

here it again with 200,000 megs

here with 50 megs

Be the first person to like this.
JohnJr
#3

Plus you can also check out when you have some time, why when a user reaches their max storage with the last image it says the photo is too large try a smaller one instead of saying with this current image they will exceed their maximum allowance for storage or something to indicate a storage issue.

Be the first person to like this.
#4

Thank you for your information.  we will recheck and inform you.

JohnJr
#5

Been almost 4 months with no reply.  Did you forget me :(

 

 

Last update on March 25, 12:25 pm by JohnJr.
Be the first person to like this.
#6

Hi JohnJr,

Thank you for reminding me on this issue.

We would like to confirm that the wrong conversion issue will be fixed in our next release 4.7.10. If you want to fix this issue immediately, please open a ticket for this request.

Regarding your feedback " why when a user reaches their max storage with the last image it says the photo is too large try a smaller one instead of saying with this current image they will exceed their maximum allowance for storage or something to indicate a storage issue."

>> This is the message returned from the server, the reason we did not change this message because it is used not only for this case but also for some unexpected cases. 

Regards,

 

Last update on March 25, 9:21 am by Hannah.
Be the first person to like this.
JohnJr
#7

Guess it didn't get fixed in 4.7.10.

 

Just post the few lines of code here and I will fix it myself...thanks!

Last update on April 9, 5:15 pm by JohnJr.
Be the first person to like this.
JohnJr
#8

So I decided just to fix it myself.

Line 101 for file: PF.Base/module/profile/include/component/block/info.class.php

Old Code:

$totalUploadSpace = Phpfox::getUserParam('user.total_upload_space');

New Code:

$totalUploadSpace = Phpfox::getUserParam('user.total_upload_space').'Mb';

Last update on April 9, 5:26 pm by JohnJr.
Be the first person to like this.