Bug 1411303
| Summary: | lists.gluster.org shows the (very) old Gluster logo as favicon.ico | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Niels de Vos <ndevos> | ||||
| Component: | website | Assignee: | bugs <bugs> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | |||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | mainline | CC: | amye, bugs, gluster-infra, mscherer | ||||
| Target Milestone: | --- | Keywords: | Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-01-11 01:17:33 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Niels de Vos
2017-01-09 12:11:53 UTC
I can't see the favicon, but I think that's a wordpress setting. Uh, I really meant lists.gluster.org, changing back the subject. When I open http://lists.gluster.org/pipermail/gluster-users/2016-October/028818.html , the old logo appears in the Firefox tab. Created attachment 1238799 [details]
Screenshot showing the old logo in a Firefox tab
But yes, this is the same for blog.gluster.org. Maybe there is a webserver redirect/alias to return a *.gluster.org/favicon.ico file somewhere? Ok so I fixed the vhost to go to the main website. Since the bug was explicitly for lists.g.o and not blog.g.o, I close it. Marking as closed, this is on the list of things to review in the next website improvement cycle. Could you provide a link to the "list of things" please? It's probably not a bugzilla tracker, otherwise this bug would have been added as a blocker there... This is something that will be built out as part of the website review in connection with the team that's working on it. It'll be part of discovery in that process. Keeping as closed, not a bug. |