sitespeed.io: Broken link(s) in results dashbaord when using urls.txt in combination with Aliases
Prerequisits:
This is the command I use:
docker run --rm -v "$(pwd):/sitespeed.io" sitespeedio/sitespeed.io:16.2.1 urls.txt --cookie remember_web_xxx=eyJpdiI6IkRoXC8wSExZZkIyM0t
This is my urls.txt:
https://staging.example.org/admin/dashboard Admin_Dashboard
https://staging.example.org/admin/users Admin_Members
(according to https://www.sitespeed.io/documentation/sitespeed.io/configuration/)
Issue
When I navigate through the results on Pages, the links to the subpages are broken:
There is a mismatch between the URL of the actual Admin_Dashboard Link:
./2021-01-11-19-31-14/pages/staging_example_org/admin/dashboard/index.html
and the location where I find the file in my folder:
./2021-01-11-19-31-14/pages/staging_example_org/Admin_Dashboard/index.html
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 17 (9 by maintainers)
Commits related to this issue
- Populate alias from file to Browsertime. https://github.com/sitespeedio/sitespeed.io/issues/3244 — committed to sitespeedio/sitespeed.io by soulgalore 3 years ago
- Populate alias from file to Browsertime. (#3245) https://github.com/sitespeedio/sitespeed.io/issues/3244 — committed to sitespeedio/sitespeed.io by soulgalore 3 years ago
- Handle alias the same way internally. https://github.com/sitespeedio/sitespeed.io/issues/3244 — committed to sitespeedio/sitespeed.io by soulgalore 3 years ago
- Handle alias the same way internally. (#3253) https://github.com/sitespeedio/sitespeed.io/issues/3244 — committed to sitespeedio/sitespeed.io by soulgalore 3 years ago
- Fix the result URL using Slack https://github.com/sitespeedio/sitespeed.io/issues/3244 — committed to sitespeedio/sitespeed.io by soulgalore 3 years ago
- Fix the result URL using Slack (#3254) https://github.com/sitespeedio/sitespeed.io/issues/3244 — committed to sitespeedio/sitespeed.io by soulgalore 3 years ago
Thanks for sharing @fmacgregor-wt let me fix that tonight.
I’ve fixed this and will release it either tonight or early tomorrow.
I just released the fix in 16.3.0, please verify that it works for you @AntoniusGolly when you have time!