Skip to content

Default logo returns a 404 error (fixes #5041)#5043

Merged
awalkowiak merged 1 commit intodevelopfrom
5041-default-logo-not-found
Feb 17, 2025
Merged

Default logo returns a 404 error (fixes #5041)#5043
awalkowiak merged 1 commit intodevelopfrom
5041-default-logo-not-found

Conversation

@jmiranda
Copy link
Member

@jmiranda jmiranda commented Feb 12, 2025

Fixed a long-standing bug with 0.9.x releases where the default configuration leads to a 404 error when rendering the default logo. See #5041 for more information.

This was tested locally using grails run-app, but I have not tested this as part of an actual deployment. If we encounter any issues with this approach, I'm going to hard-code the context path.

@github-actions github-actions bot added the flag: config change Hilights a pull request that contains a change to the app config label Feb 12, 2025
@codecov
Copy link

codecov bot commented Feb 12, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 7.84%. Comparing base (6bb60bc) to head (a103d75).
Report is 205 commits behind head on develop.

Additional details and impacted files
@@            Coverage Diff            @@
##             develop   #5043   +/-   ##
=========================================
  Coverage       7.84%   7.84%           
  Complexity       876     876           
=========================================
  Files            624     624           
  Lines          42815   42815           
  Branches       10375   10375           
=========================================
  Hits            3357    3357           
  Misses         38955   38955           
  Partials         503     503           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Member

@ewaterman ewaterman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this is 404ing already, I'm fine with merging it in and seeing what happens

# Allow users to customize logo image url as well as label
logo:
url: "/assets/openboxes_logo_40x40.jpg"
url: "${server.contextPath}/assets/openboxes_logo_40x40.jpg"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And this does not affect the displayLogo tag? I mean, that this won't produce there /openboxes/openboxes/assets/openboxes_logo_40x40.jpg?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@awalkowiak Good point. I'll test it out, but I'm sure it does do that.

Can you and @alannadolny review ticket #5041 and see if you can think of a better approach?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps, we just need to make the change on the API side like Approach 3 suggests.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like it works fine within displayLogo too. Therefore I'm going to merge as-is

image

@awalkowiak awalkowiak merged commit 7c8579c into develop Feb 17, 2025
9 checks passed
@awalkowiak awalkowiak deleted the 5041-default-logo-not-found branch February 17, 2025 12:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

flag: config change Hilights a pull request that contains a change to the app config

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants