Non-technical users would benefit from slightly more robust status report notifications. If something is missing from s3 settings, we can notify on the status report rather than have it only surface when a user tries to read or write.

It would be nice in the future to test write-ability if amazons3_folder is provided.

CommentFileSizeAuthor
#4 additional_status-2271881-4.patch4.74 KBbkonetzny
#3 2271881-status-reporting-3.patch4.29 KBdrnikki
#2 2271881-status-reporting-2.patch4.27 KBdrnikki
#1 2271881-status-reporting.patch4.52 KBdrnikki

Comments

drnikki’s picture

drnikki commented
StatusFileSize
new 2271881-status-reporting.patch4.52 KB
drnikki’s picture

drnikki commented
StatusFileSize
new 2271881-status-reporting-2.patch4.27 KB

Updated paths.

drnikki’s picture

drnikki commented
StatusFileSize
new 2271881-status-reporting-3.patch4.29 KB
bkonetzny’s picture

bkonetzny commented
Status: Active » Needs review
StatusFileSize
new additional_status-2271881-4.patch4.74 KB

Updated the patch to show the configured bucket name or link to the configuration page, if no bucket is configured.

deviantintegral’s picture

deviantintegral commented
Version: 7.x-1.x-dev » 7.x-2.x-dev

I ported this to the 7.x-2.x branch over at https://github.com/justafish/drupal_amazons3/pull/21

I also added test coverage for using Drupal variables, and fixed issues where someone doesn't run composer install but enables the S3 module.

deviantintegral’s picture

deviantintegral commented
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.