Version 2.7.0: Upload logo/scoresheet function not working properly?

[bigirishape]

Verify the Following
Reporting About the Latest Version? Yes
If you are not running the most current version in your environment, please update prior to reporting your bug. Your issue may have already been addressed.

Searched Issue Reports for Bug? Yes
Please search open and closed issues for issues similar to yours. Your bug may already have a posted solution.

Reviewed the Good To Know Issue Reports? Yes or No
Please review the Issue reports that are labeled Good to Know. Find one and click on the label to view them all.

BCOE&M Info
Version: 2.7.0(e)
Installation URL: fwiw.abnormalhomebrewers.com
Hosted Installation? No

Describe the Bug
I am running BCOEM alongside my Lightsail Wordpress server. Having issues with the UPLOAD function in both Sponsor Logos and Paper Scoresheets (the only two upload features I've attempted). If I upload the logo files via WinSCP to the user_images directory, then the logo files are available for BCOEM to use. However, I cannot locate which directory to upload the scanned PDF scoresheets to.

Both upload attempts, when using the "multi-upload" option, report a Success but do not actually upload any files. When I switch to the "single-file" upload option, the server returns a 500 error code.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Admin > Scoring > Upload Scoresheets'
2. Drag/drop a file to the window or click box to find the file.
3. Select Upload
4. In the case of multi-file upload, it reports success but no files are located. In the case of single-file upload, it returns an error 500.

Expected Behavior
The files should upload and be presented in the upload screen.

Screenshots

Server Environment

• PHP Version:
• MySQL Version:
• Other Info: [if applicable. Apache, nginx, etc.]

Local Environment

• OS:
• Browser:
• Browser Version:

Additional Context
Add any other context about the problem here.

[geoffhumphrey]

Hi @bigirishape, do you have any log files you could share that detail the error? This will help to pin down the file that is causing the error.

[graemecoates]

@geoffhumphrey I'm sure this is the same issue as #1574 . See log files in that bug.