Skip to content
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

MapRoulette Favicon Not Displaying in Browser Tabs #2202

Closed
ljdelight opened this issue Dec 11, 2023 · 2 comments
Closed

MapRoulette Favicon Not Displaying in Browser Tabs #2202

ljdelight opened this issue Dec 11, 2023 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@ljdelight
Copy link
Collaborator

Describe the bug
The browser should display the MapRoulette favicon, as illustrated in the screenshot below. In the example, you can see that the tabs for Google and Firefox each have their respective icons visible, but the MapRoulette tab currently does not have its favicon displayed.

Expected behavior
The MapRoulette favicon should be displayed.
image

To Reproduce
Steps to reproduce the behavior:

  1. Open your choice of browser and the dev tools
  2. Visit the maproulette.org site
  3. See that the favicon is not displayed
  4. Look at the 'Network' request and look for 404s for the favicon images

Desktop (please complete the following information):

  • OS: Fedora 38
  • Browser: Firefox
  • Version: 120.0

Additional context
The nginx logs confirm this was not found:

[11/Dec/2023:04:22:11 +0000] "GET /assets/images/favicons/favicon-16x16.png HTTP/1.1" 404 472 "https://staging.maproulette.org/" "Mozilla/5.0 (X11; Linux x86_64; rv:120.0) Gecko/20100101 Firefox/120.0"
[11/Dec/2023:04:22:11 +0000] "GET /assets/images/favicons/apple-touch-icon.png HTTP/1.1" 404 476 "https://staging.maproulette.org/" "Mozilla/5.0 (X11; Linux x86_64; rv:120.0) Gecko/20100101 Firefox/120.0"
@ljdelight
Copy link
Collaborator Author

ljdelight commented Jan 18, 2024

This is resolved via a small tweak to the deployment scripts (which has its own FE nginx configuration).
The next deployment will pick this up automatically

@ljdelight
Copy link
Collaborator Author

The previous caused a regression by breaking swagger. The /assets path is shared between the API and FE containers, so /assets/lib/ and /assets/swagger.json going to the FE container caused swagger to break.

Resolved with maproulette/maproulette2-docker#95
Swagger is once again working fine on prod 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

No branches or pull requests

1 participant