Hi all,
I would like to inform you that the link at the top of this page to information about this PHYSLITE data format is broken.
" The PHYSLITE Data Format "
Thanks for the report! Where did you find the bad link exactly?
Just to be extra clear, the link we have in the phrase âwhich you can learn more about in The PHYSLITE Data Format sectionâ is to:
https://opendata.atlas.cern/docs/documentation/data_format/physlite
and we canât find where youâve hit the link to:
https://opendata.atlas.cern/docs/userpath/documentation/data_format/physlite
(with the extra âuserpathâ in there)
Ok, it looks like weâve identified the source of this, which is a kinda weird feature (to me) that the docusaurus folks know about already:
opened 05:07PM - 29 Jul 21 UTC
closed 04:05PM - 02 Aug 21 UTC
closed: question
## đ Bug Report
### Prerequisites
- [x] I'm using the latest version of Do⌠cusaurus.
- [x] I have tried the `npm run clear` or `yarn clear` command.
- [x] I have tried `rm -rf node_modules yarn.lock package-lock.json` and re-installing packages.
- [ ] I have tried creating a repro with https://new.docusaurus.io **(the issue happens randomly, I could test for hours and not come across it so making another repo wouldn't work/help)**
- [x] I have read the console error message carefully **(not applicable)**
### Description
Relative links will inconsistently create incorrect paths to the desired pages.
A normal refresh on the page the link is located on will fix the issue temporarily, so I doubt it is a cache issue.
### Have you read the [Contributing Guidelines on issues](https://github.com/facebook/docusaurus/blob/master/CONTRIBUTING.md#reporting-new-issues)?
(Yes)
## Steps to reproduce
As this is inconsistent it is not something I can tell you how to reproduce with guaranteed success; it happens randomly to users. When I hear about instances of this occurring, going to the page the link is on myself the link will work fine.
It does happen to me as well though, and a refresh of the page the link was on does always fix the problem for that instance.
## Expected behavior
I expect the links that are all correct as they pass github actions and work after a refresh to work consistently.
## Actual behavior
Links will randomly go to the wrong path, seemingly by either not going far enough back up the hierarchy and then trying to go from a folder shouldn't be in the path.
E.g. A relative link such as `(../../nextPage)` from a page at say `folder1/folder2/currentPage`
Will randomly create a path of `docs/folder1/nextPage` rather than the correct url of `docs/nextPage`
## Your environment
- Public source code:
- Public site URL:
- Docusaurus version used:
- Environment name and version (e.g. Chrome 78.0.3904.108, Node.js 10.17.0):
- Operating system and version (e.g. Ubuntu 20.04.2 LTS):
Public source code: Not available publicly
Public site url: https://docs.lunalabs.io/
Docusaurus version used: 2.0.0-beta.4
Environment name and version: Chrome 92.0.4515.107, Babel 7.12.16, Node 14.15.0
Operating system and version: Windows 10 Pro, Version 21H1
## Reproducible demo
You can try links on our docs at https://docs.lunalabs.io/ but as I have stated this issue happens inconsistently and randomly.
We will try to fix the links across the site; in the meantime it seems that if you just reload the page, or click on the page location from the left bar immediately after arriving at it, youâll get the right links. This only seems to affect a limited number of pages on the site, so I hope it wonât mess with your experience too much. Sorry for the inconvenience!
1 Like