We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Course duplication creates a new folder in coursemology2 bucket and populate it with logos copied from the original course.
This path/folder failed to be created for the new course, causing logos for the new course to appear broken
For example, when course 1776 is duplicated to create course 1777, coursemology would try to display the new course's logo from https://coursemology2.s3-ap-southeast-1.amazonaws.com/uploads/images/course/1777/logo/medium_logo-x.png.jpeg. But since the path does not actually exist on S3 bucket, trying to access this link with the correct credentials will yield invalid key error message from AWS.
So it seems that our DB assumes that the logos are correctly duplicated on S3, when in fact it is not.
The text was updated successfully, but these errors were encountered:
Sorry, something went wrong.
Earliest course to encounter this was https://montfortsec.coursemology.org/courses/1758 (Copied at 16-09-2019 11:18).
Could have been broken since #3641
Successfully merging a pull request may close this issue.
Should
Course duplication creates a new folder in coursemology2 bucket and populate it with logos copied from the original course.
Is
This path/folder failed to be created for the new course, causing logos for the new course to appear broken
For example, when course 1776 is duplicated to create course 1777, coursemology would try to display the new course's logo from https://coursemology2.s3-ap-southeast-1.amazonaws.com/uploads/images/course/1777/logo/medium_logo-x.png.jpeg. But since the path does not actually exist on S3 bucket, trying to access this link with the correct credentials will yield invalid key error message from AWS.
So it seems that our DB assumes that the logos are correctly duplicated on S3, when in fact it is not.
The text was updated successfully, but these errors were encountered: