Added link checker#3153
Draft
mnocon wants to merge 8 commits into
Draft
Conversation
mnocon
force-pushed
the
link-checker
branch
3 times, most recently
from
0772f58 to
21146e4
Compare
mnocon
commented
May 19, 2026
| provider: remote | ||
| options: | ||
| url_pattern: 'https://placekitten.com/%%width%%/%%height%%' | ||
| url_pattern: 'https://picsum.photos/%%width%%/%%height%%' |
Contributor
Author
There was a problem hiding this comment.
Fastly is behind this solution (https://github.com/DMarby/picsum-photos/blob/60d20d8f20bafbe727bbd37f03d2cb22dc7d4309/README.md?plain=1#L9), so should be safe to use this one.
mnocon
commented
May 19, 2026
| - 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 |
Contributor
Author
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
mnocon
commented
May 19, 2026
|
|
||
| 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). |
Contributor
Author
There was a problem hiding this comment.
This page is broken, no sense of ressurecting it right now
|
code_samples/ change report
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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