-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
[Fix] PAGES: homepage.html broken issues url #84
Conversation
Signed-off-by: Remy Bos <[email protected]>
Unfortunately, this does not help if a slash is already present. Therefore, the update script should ensure the correct URL.
Sure. |
Signed-off-by: Remy Bos <[email protected]>
@sjokkateer |
@sjokkateer |
I will check now all documentations for the broken link. |
@froschdesign Awesome, glad to hear that! |
@froschdesign, Were any of laminas-di, laminas-log, or laminas-diactoros rebuilt? |
Broken links are included in:
Everything is good in Mezzio and laminas-mvc. |
@froschdesign Barcode seems to be working for me, what is considered a broken url on that page? |
laminas-barcode is wrong on this list. Sorry and thanks for the hint! |
The problem in laminas-di will be fixed with the next release. But laminas-log is not in active development. |
Alright that would be nice :)! |
If you find other problems or have ideas for improvements, please let me know. |
Any time, thank you too for your time! |
@froschdesign Awesome, it seems that after the release laminas-di's URLs are fixed too again! |
Signed-off-by: Remy Bos [email protected]
Description
This PR attempts to fix an issue where the url to the issues page of the repository of a particular laminas component is broken.
Pages with a broken issues URL:
What I've done:
mkdocs.yml
file in the repo and inspect therepo_url
property for trailing slashes.What I've discovered:
Source
, one example: laminas-cache.mkdocs.yml
file, one example: laminas-cache#L39What I've concluded:
The components that don't have the broken URL are either cached or some caching is applied somewhere in the build process. Although the same error does not apply to the other component's homepage (yet) this will most likely apply at some point in the future.
Please let me know what you think of the 'investigation' and proposed change. And whether or not it is possible to freshly rebuild the documentations after the change takes effect?