Closed (fixed)
Project:
Link checker
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
7 Feb 2011 at 20:50 UTC
Updated:
19 Jan 2012 at 22:00 UTC
When cloning a node (using this module: http://drupal.org/project/node_clone), looks like the new node is created and links in the new node are appropriately indexed.
In either mode (save-edit or prepopulate) after the scanning status screen is published, users are routed back to an intermediate page. Users should be routed to view the new node, so they believe that the cloning failed.
Comments
Comment #1
stacysimpson commentedI should re-state to be more clear:
In either mode (save-edit or prepopulate) after the scanning status screen is published, users are routed back to an intermediate page, so they believe that the cloning failed. Users should be routed to view the new node.
Comment #2
hass commentedI'm sorry, but I don't understand you. Node clone creates 1:1 copies of a node. Therefore if a link is broken in the source node, they are also broken in the new node. As the copy is not a new revision of the source, both nodes need to be reported to have broken links. Sounds all normal. I don't understand what you are doing and what should be broken.
Comment #3
stacysimpson commentedSorry about that...the issue isn't with links embedded within the content. It's with the contributor's browser session and redirection.
Lets take the "prepopulate" option as an example.
Without link checker:
1) User selects the 'clone' option.
2) User is presented with a node edit form.
3) User makes appropriate changes.
4) User selects 'save'.
5) User is redirected to view the new node.
With link checker enabled:
1) User selects the 'clone' option.
2) User is presented with a node edit form.
3) User makes appropriate changes.
4) User selects 'save'.
5) User sees the 'scanning for new links' status screen.
6) User is redirected to a node edit form. At this point, the contributor assumes that the clone process failed. (After the scanning status screen, users should be redirected to view the new node.)
HTH
Comment #4
hass commentedAh ok, it only happens if the scan batch process appears? I may have not seen/overseen this while testing... Need to investigate if this can be changed. I guess it also happens without node_clone.
Comment #5
hass commentedHopefully fixed with the following commits. Can you test, please?
D6: http://drupalcode.org/project/linkchecker.git/commit/0009482
D7: http://drupalcode.org/project/linkchecker.git/commit/9f7388b
Comment #6
stacysimpson commentedVerified the latest dev version, 6.x-2.x-dev 2012-Jan-04, works fine. Thanks again!
Comment #7
hass commented