Blank page upgrading
How do I fix it?
What version are you upgrading from?
And upgrading to?
And what URL does the error happen on exactly? (this will let us know the step that is failing)
Get now:
It appears that you have made a file upload but exceeded this servers ‘post_max_size’ limit (50 MB) or ‘upload_max_filesize’ limit (50 MB). Unfortunately this makes your form submission invisible to NA7KR. Please try again with a smaller size, or get the post_max_size limit increased. An alternate explanation is if you reached this URL manually – this URL is intended solely for processing the result of a form submitted to it, and the main_news_categoryparameter is missing. (version: 10.0.22, PHP version: 7.3.2-3+0~20190208150725.31+stretch~1.gbp0912bd, URL: /cms/cms-blogs/__edit/38.htm?uploading=1&keep_fatalistic=1)
Trying to delete Spam in blog
For example, if your base URL is 'www.example.com', and someone has decided to redirect all 'www.example.com' traffic to 'example.com', then the form will be coded to submit to an 'www.example.com' URL but the web server will then redirect it immediately to a 'example.com' URL. The process of doing the redirect throws out form data.
As your PHP version was recently changed, I don't find it unlikely other server-level changes were made.
Next
View a user
PHP WARNING [2] count(): Parameter must be an array or an object that implements Countable in sources/hooks/systems/profiles_tabs/about.php on line 163 (version: 10.0.22, PHP version: 7.3.2-3+0~20190208150725.31+stretch~1.gbp0912bd, URL: /members/view/mmocs.htm)
Here is the stack trace:
Below is a stack trace revealing the state NA7KR was in when the error occurred. If this represents a bug in the unmodified software, you may want to check NA7KR website for a fix, and if there isn't one, report this as a bug. Please note that merely posting a stack trace is not sufficient for us to solve your problem; the stack trace is just an aid that presents us with additional information. We still need to know the error message, what you tried to do, how you tried to do it, version numbers, and any other appropriate information.
We apologize for this problem and if it's a bug we hope you will work with us so that we can fix it for you promptly.