2018-02-25, 12:52 AM
Thanks to one of my members who finally tracked down an occasional bug.
To replicate:
https://community.mybb.com/newreply.php?...rocessed=1
As you can see the error says "Can not upload file - Too large for php post_max_size directive. Please press the back button."
When in fact it's that the $post var is empty.
From newreply.php, editpost.php, and newthread.php
So the error says it's too large but actually it's just empty. This confuses members.
This appears to happen when you refresh the page btw. So the $post data might empty out and reload the page with that error.
The error should be corrected so it's not confusing people.
I recommend something slightly more generic like:
"There has been an error due to your post data being empty. Possibly cause is a browser page refresh or direct access to this page. We recommend you press your browser back button and begin again."
In any case the existing error is wrong and confuses people into thinking your site is the problem with some pseudo php error that didn't happen.
Honestly, got reports of this for years.
To replicate:
https://community.mybb.com/newreply.php?...rocessed=1
As you can see the error says "Can not upload file - Too large for php post_max_size directive. Please press the back button."
When in fact it's that the $post var is empty.
From newreply.php, editpost.php, and newthread.php
if((empty($_POST) && empty($_FILES)) && $mybb->get_input('processed', MyBB::INPUT_INT) == 1)
{
error($lang->error_cannot_upload_php_post);
}So the error says it's too large but actually it's just empty. This confuses members.
This appears to happen when you refresh the page btw. So the $post data might empty out and reload the page with that error.
The error should be corrected so it's not confusing people.
I recommend something slightly more generic like:
"There has been an error due to your post data being empty. Possibly cause is a browser page refresh or direct access to this page. We recommend you press your browser back button and begin again."
In any case the existing error is wrong and confuses people into thinking your site is the problem with some pseudo php error that didn't happen.
Honestly, got reports of this for years.