playframework / playframework/playframework.com
When a page is not found, the info displayed is incorrect.
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 44
- Forks
- 62
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 3
Description
https://www.playframework.com/documentation/2.7.x/JavaEbean started failing and it lists the following:
This page was found in other versions of the documentation:
Found page JavaEbean in version 2.8.0-M1. --> returns 404 (it's not even the last milestone in the 2.8.x series (2.8.0-M3 is already released)
Found page JavaEbean in version 2.7.x. --> returns 404
Found page JavaEbean in version 2.7.3. --> returns 200
Found page JavaEbean in version 2.7.2. --> returns 200
Found page JavaEbean in version 2.7.1. --> returns 200
...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the 404 at the reported JavaEbean documentation URL and trace the version lookup that generates the alternate-version list. Compare the listed versions with their actual responses; done means the not-found page reports only valid versions and links or statuses match the available documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100