Closed (works as designed)
Project:
Link checker
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
23 Oct 2012 at 17:13 UTC
Updated:
1 Mar 2013 at 18:30 UTC
Linkchecker seems to ignore unpublished nodes (is that correct ?).
It's probably often what you want.
And then ofcourse, there's times you really want to batch through those 1000 freshly imported nodes and fix them before you publish them. Which is what I wanted to do now ;-)
Is there a way to do this already - is there an easy hack or patch I could revert when done ?
curious,
*-pike
Comments
Comment #1
hass commentedI'm sorry, only published nodes are checked, but you can force the check after it has bern published. Shouldn't be a big issue... if a few links are broken the world does not collapse :-)
Checking unpublised nodes would bring up hundreds of fixed links if you have revisions.
Comment #2
joverstreet commentedIs it that difficult to only get the most recent revision? We also have a need to check links BEFORE they're published both for those batch imports and as part of the workflow.
Thanks!
Comment #3
hass commentedLinkchecker does only support basic functionality of forward revisions (and only with workbench suite and linkchecker 7.x-1.1+). Always keep in mind that link checks are made in background only. The links will than checked a few hours after the draft/needs review content has been saved. There is no guaranty when this check will happen as it's a low priority downstream task. It will be very difficult to implement this. I expect a lot of users complaining why they are stressed by linkchecker about their drafts that are under heavy work...
We can look into this in D8 again. At least forward revisions are a lot easier to handle there.
Comment #4
hass commentedTagging
Comment #5
joverstreet commentedThank you for addressing this. Maybe one possible update in the future would be a 'check links now' button next to the save or something similar.