-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Support a URL address as FOOTER_ORGANIZATION_LOGO #20001
New issue
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
Conversation
Thanks for the pull request, @mahyard! I've created OSPR-3206 to keep track of it in JIRA. JIRA is a place for product owners to prioritize feature reviews by the engineering development teams. Feel free to add as much of the following information to the ticket:
All technical communication about the code itself will still be done via the GitHub pull request interface. As a reminder, our process documentation is here. |
@mahyard Thank you for your contribution. Please let me know once all checks are green and it is ready for review. |
jenkins run all |
@natabene can I ask to run tests again please. |
jenkins run all |
9f4ccff
to
2a4f067
Compare
jenkins run all |
1 similar comment
jenkins run all |
@natabene |
jenkins run all |
@natabene, |
@edx/testeng Could you help us here with the bokchoy test? |
Looks like that test has been intermittently failing, starting the process to remove it now. You can go ahead and ignore that failure. |
@ormsbee This is ready for your review, should be quick |
Excuse me @ormsbee, |
@edx/fedx-team Team, could you give this a look? CC @georgebabey |
thank you @natabene, |
jenkins run all |
Please address js failure, @mahyard |
what? These errors doesn't look to be generated because of my changes. |
jenkins run js |
Your PR has finished running tests. There were no failures. |
@edx/fedx-team Do you guys want to review this? It is ready for review and merge. |
@natabene A long time have been passed from this PR. |
@georgebabey When you have a chance, can you let me know if fedx team can review this? |
@nasthagiri Can you give this a look when you have a chance? |
hello @natabene , |
@mahyard This is on our radar, I have queued it for the appropriate team, but it might take a while to review. |
@mahyard Thank you for reporting this issue, and even more so, proactively taking the time to contribute a fix (to the code and to the mocked test). We very much appreciate your effort. I am merging this PR now. |
@mahyard 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future. |
EdX Release Notice: This PR has been deployed to the staging environment in preparation for a release to production on Tuesday, July 30, 2019. |
EdX Release Notice: This PR may have caused e2e tests to fail on Stage. If you're a member of the edX org, please visit #e2e-troubleshooting on Slack to help diagnose the cause of these failures. Otherwise, it is the reviewer's responsibility. E2E tests have failed. https://gocd.tools.edx.org/go/tab/pipeline/history/STAGE_edxapp_M-D |
EdX Release Notice: This PR has been deployed to the production environment. |
@ormsbee @mahyard The footer logos (edX logo, mobile app logos) are breaking due to this PR because Now, url path of the logos are not generated as they should be.Expected url path is https://prod-edxapp.edx-cdn.org/static/images/app/app_store_badge_135x40.d0558d910630.svg |
Hi,
this is a fix for the problem reported in this google-groups thread
More information:
without this code change it is not possible to give an absolute URL to the FOOTER_ORGANIZATION_LOGO in settings. doing so will produce an HTTP 500 error in homepage and any other place
branding.api.get_footer()
has been called.@ormsbee could you please take a look?