-
Notifications
You must be signed in to change notification settings - Fork 105
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
New links get the same address as peeringdb #145
Comments
Hmm, I'm not able to reproduce this. My config: web:
links:
- title: PeeringDB
order: 2
url: https://peeringdb.com
- title: Another Link
order: 1
url: https://www.google.com
side: right
- title: Yet Another Link
order: 3
url: https://www.cloudflare.com
show_icon: false When I have that in my config and start hyperglass (with |
I can see it correctly in the build ui but even after a manual build it still goes to the wrong link. [{'order': 0, 'show_icon': True, 'side': 'left', 'title': 'PeeringDB', 'url': 'https://www.peeringdb.com/asn/{primary_asn}'}, {'title': 'NFOrce Website', 'order': 5, 'side': 'right', 'url': 'https://www.nforce.com/'}] If you want to see it as well, https://lg.nforce.com/ Nvm seeing the website here, guess it's easier like this. |
I actually still do indeed, but it seems to be a firefox issue now that I can see as in Chrome it displays them correctly. |
I can confirm that this issue exists:
That being said, the issue appears to be fixed on the v2.0.0 branch, for reasons unknown. More than likely, a dependency update fixed the underlying issue accidentally. 🤷♂️ |
Hi |
I added the peeringdb link on the left which works fine, but also tried adding a second link on the right, which still has the peeringdb link even though it has a different value.
links:
- order: 0
show_icon: true
side: left
title: PeeringDB
url: https://www.peeringdb.com/asn/{primary_asn}
- order: 5
side: right
title: Website
url: https://google.com
I replaced the website with a generic one since this is my private github account :)
The text was updated successfully, but these errors were encountered: