- Issue created by @gugalamaciek
- ๐ต๐ฑPoland gugalamaciek
Proposed patch adds feature described in point 1. and implements performance improvements described in 2. - 4.
- Status changed to Needs review
9 months ago 1:14pm 8 March 2024 - last update
9 months ago 86 pass - Status changed to Active
9 months ago 4:20pm 8 March 2024 - ๐จ๐ฆCanada joseph.olstad
patch 27 didn't work out, working on a new one.
- Status changed to Needs review
9 months ago 4:21pm 8 March 2024 - last update
9 months ago 86 pass - ๐จ๐ฆCanada joseph.olstad
Hi Gugalamaciek, I'm submitting a patch to re-use our setting that we had for another patch , but using your logic as ours was not working correctly but the setting I don't want to lose it and have to do more work with configs that are already ignored.
- ๐จ๐ฆCanada joseph.olstad
not sure if patch #7 is good, if you're testing, try patch 2 instead. I'm testing #7
- ๐จ๐ฆCanada joseph.olstad
Patch 7 works well, basically the same as patch 2 except I renamed the config setting key to work with our settings (yes selfish me).
- ๐ต๐ฑPoland gugalamaciek
@Joseph Fine for me :) That's why it's on review ;) I checked briefly, and I think you should change
linkchecker.schema.yml
as well.As I see you've changed setting:
check.skip_unpublished
to:
search_published_contents_only
But when I check
linkchecker.schema.yml
, I have a feeling, that this property should be undercheck
. So it should be rathercheck.search_published_contents_only
. Also, if you want this change, I suggest to rename everywhere (e.g. form property as well). It will be less confusion for developers reading this code ;) - last update
9 months ago 86 pass - Merge request !62Issue #3426637 by gugalamaciek, joseph.olstad: Improve performance of... โ (Merged) created by joseph.olstad
- last update
9 months ago 86 pass - ๐จ๐ฆCanada joseph.olstad
Thanks again gugalamaciek, we really appreciate your great work on this solution! It has been deployed into our production environment.
- ๐ต๐ฑPoland gugalamaciek
joseph.olstad I'm glad I could help :)
FYI #11 looks good, I've added it to our site :) - ๐ฎ๐ณIndia bmahesh03121
#11 tested and works fine, thanks joseph.olstad and gugalamaciek
- last update
8 months ago 86 pass - ๐ฎ๐ณIndia bmahesh03121
Refined patch #11
Changes :
changed
search_published_contents_only
tosearch_published_content_only
changed
Search published contents only
toSearch published content only
- Status changed to RTBC
7 months ago 11:19pm 18 April 2024 - ๐จ๐ฆCanada joelpittet Vancouver
It would be nice to have these 2 features separate but the second part is exactly what I need as the unpublished nodes are outdated content in a lot of cases.
Anyways RTBC #17 with the text changes.
- Issue was unassigned.
- ๐จ๐ฆCanada joseph.olstad
While this functionality is an improvement, it is actually scanning published revisions of archived content.
This gets a bit tricky because workflows are customizable and while this flow may be undesired for the standard editorial workflow , anything hard coded could possibly upset those doing something completely different.
The latest change doesn't help us since we've already been using the other configuration name and renaming this makes more work for us to update the configuration but ok, sure ya that's ok.
- ๐ง๐ชBelgium rp7
As I already mentioned by others, perhaps we should idd look into separating the 2 features.
Skipping unpublished content could use/benefit from the solution being worked on in โจ Allow entities to be skipped programmatically Needs review . - First commit to issue fork.
-
VladimirAus โ
committed 0d2daf1c on 2.0.x authored by
joseph.olstad โ
Issue #3426637 by bmahesh03121, gugalamaciek: Improve performance of...
-
VladimirAus โ
committed 0d2daf1c on 2.0.x authored by
joseph.olstad โ
- Status changed to Fixed
4 months ago 7:03am 23 July 2024 - ๐ฆ๐บAustralia VladimirAus Brisbane, Australia
Thank you! Committed! ๐จ
Automatically closed - issue fixed for 2 weeks with no activity.