You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 2, 2022. It is now read-only.
When uploading media via Buoy, the incident interface provides no indication of a failed upload due to over-large file sizes.
Platform: All
Browser: All
URL: N/A
Is it reproducible: Yes
Steps to Produce/Reproduce
Create a new Buoy alert.
In the incident view, press the "Record" button in the incident toolbar.
Select or create a file that exceeds the WordPress instance's "Max upload file size" setting (fileupload_maxk) value.
Observe no feedback from the Buoy user interface.
Expected Results
A warning or other indication of an overly large file is given.
Actual Results
No interaction or feedback whatsoever is shown. There is no change in the interface.
Workarounds
Increase the filesize_maxk value manually in the WordPress admin (or Network Admin, for Multisite installs) screens, or upload smaller files. #186 covers adding this to the admin UI.
The text was updated successfully, but these errors were encountered:
When uploading media via Buoy, the incident interface provides no indication of a failed upload due to over-large file sizes.
Steps to Produce/Reproduce
fileupload_maxk
) value.Expected Results
A warning or other indication of an overly large file is given.
Actual Results
No interaction or feedback whatsoever is shown. There is no change in the interface.
Workarounds
Increase the
filesize_maxk
value manually in the WordPress admin (or Network Admin, for Multisite installs) screens, or upload smaller files. #186 covers adding this to the admin UI.The text was updated successfully, but these errors were encountered: