Added link checker#3153
Conversation
mnocon
force-pushed
the
link-checker
branch
4 times, most recently
from
21146e4 to
deb36e3
Compare
| - Rewrite custom web front end to use the new Platform/Symfony stack, see [Beginner Tutorial](beginner_tutorial.md) | ||
| - Rewrite custom admin modules to use the new Platform/Symfony stack | ||
| - And if you do this while on 5.x, you can use several of the [available legacy migration features](https://doc.ez.no/display/EZP/Legacy+code+and+features) to make the new code appear in legacy admin | ||
| - And if you do this while on 5.x, you can use several of the [available legacy migration features](https://web.archive.org/web/20140911035812/https://doc.ez.no/display/EZP/Legacy+code+and+features) to make the new code appear in legacy admin |
There was a problem hiding this comment.
These pages are no longer online, I feel linking to their archived versions is the right thing to do - in case someone is stuck on a legacy version
|
|
||
| Also, you can now apply new filters that are intended to help you declutter the calendar view. | ||
|
|
||
| For more information, see [Calendar widget](https://doc.ibexa.co/projects/userguide/en/latest/publishing/advanced_publishing_options/#calendar-widget). |
There was a problem hiding this comment.
This page is broken, no sense of ressurecting it right now
There was a problem hiding this comment.
If it's in 3.2 and https://doc.ibexa.co/projects/userguide/en/3.3/publishing/advanced_publishing_options/#calendar-widget is still there, that could be the fix.
There was a problem hiding this comment.
Thanks, added that in the latest commit
|
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| lychee- | ||
|
|
||
| - name: Check links | ||
| uses: lycheeverse/lychee-action@v2 |
mnocon
force-pushed
the
link-checker
branch
2 times, most recently
from
d7aae42 to
15d6488
Compare
ibexa-workflow-automation-1
Bot
requested review from
adriendupuis,
dabrt and
julitafalcondusza
and removed request for
a team
Co-authored-by: Adrien Dupuis <61695653+adriendupuis@users.noreply.github.com>
| # userguide en/latest/ — map to the newest available clone (userdoc-5.0) | ||
| "https://doc\\.ibexa\\.co/projects/userguide/en/latest/([^#]+\\.html)(#.*)?$ file://__BASE_DIR__/repositories/userdoc-5.0/site/$1$2", | ||
| "https://doc\\.ibexa\\.co/projects/userguide/en/latest/([^#/]+(?:/[^#/]+)*)/?(#.*)?$ file://__BASE_DIR__/repositories/userdoc-5.0/site/$1/index.html$2", | ||
| "https://doc\\.ibexa\\.co/projects/userguide/en/latest/$ file://__BASE_DIR__/repositories/userdoc-5.0/site/index.html", |
There was a problem hiding this comment.
I think we should fail on latest. We should always use 5.0. latest will be 6.0 one day, and having 5.0 targeting 6.0 will be wrong. And maybe we already have 4.6 targeting 5.0 issues.
userguide/en/latest → userdoc-5.0 remapping shouldn't be needed and we shouldn't have to maintain this block on 6.0 release.
There was a problem hiding this comment.
Nice, like the idea! Will implement
3 participants
This PR makes it possible to check links in the documentation
Problem, constraints, and assumptions:
Tool used
Lychee is used: https://lychee.cli.rs/
How it works
.lycheeignoreis used for URLs that cannot be checked easilyLinks leading to doc.ibexa.co are remapped to local instances of the doc:
I've checked links to lower versions of the doc (which cannot be checked on CI) manually, fixed them, and then added to the
.lycheeignorefile.The idea is that we can use the release_4.6.x branches, to make sure all the links are correct before the release
Fixing the links
The rest of the PR fixes existing links:
This PR is split into 2 commits:
The job with broken links is here:
https://github.com/ibexa/documentation-developer/actions/runs/26101343148/job/76752887924
404 - external link broken
30x - redirects
Cannot find file: File not found- documentation link broken