Hi Alexander
I Downloaded the latest dev version today, to ensure I have the latest changes,
(Some of this may explain some of my previous reports)
After installation I cleared the links
Recent log entries displayed "Wiped out obsolete links."
Check number of links per cron run: is set to 50
After the first cron run their were 74 entres in the Broken links report
After a later cron run (which is a good sign) I have an entry in the report as follows
URL http://www.mydomain.com/node/8866
Response 301
Operations EDIT Node 76
If I go to the node 76, the link is there to node/8866, so all as expected
And i know their is a URL Alias
Now we go to "Recent log entries" and find the associated entry
Type - linkchecker
Message - Link http://www.mydomain.com/node/8866 has ...
Operations - Brokens links
Opening the details for the message
Message - Link http://www.mydomain.com/node/8866 has changed and needs to be updated
Referrer http://www.mydomain.com/my_path1/my_path2/my_path3/my_node1
Location http://www.mydomain.com/my_parth1/my_path2/my_path3/my_node2
Neither Location or Referer nodes have any reference to node/8866
Referer only contains
<p>[view:fanart_view==702]</p>
Location only contains
<p>[view:fanart_view==703]</p>
These use "Insert Views" to include a view in the node None of the items in the view refer to node/8666
Their are 44 linkchecker Reports for this specific cron run, and every single one has
Referrer http://www.mydomain.com/raymond-feist/artist-corner/fan-art/benjamin-munro
Location http://www.mydomain.com/raymond-feist/artist-corner/fan-art/bill-thomas
The only difference is the message
Looking at previous linkchecker runs the Referer and Location are always the same pair for all links for that run
An example from last night which really makes no sense to me (but then I admit I dont fully understand)
Location - http://www.mydomain.com/admin/reports/status/run-cron
Referrer - http://www.mydomain.com/admin/reports/status
Message - Link http://www.mydomain.com/node/207 has changed and needs to be updated.
Comments
Comment #1
hass commentedInstall devel and look into the devel load and devel render tab of your node. The link must be part of your fanart_view content. You might get an idea... I have never tested with views.
Comment #2
Anonymous (not verified) commentedHi Alexander, never used Devel module before, but I think I was looking at the right information
Using the Dev render tab I was able to see the content inserted by the view and for both nodes in the "Recent log entries" :-
Referrer http://www.mydomain.com/raymond-feist/artist-corner/fan-art/benjamin-munro
Location http://www.mydomain.com/raymond-feist/artist-corner/fan-art/bill-thomas
Their were no signs of the "node/8866", which I had suspected, as i use different content types for different needs, and the Referer and Location nodes were of totally different content types. They are for, as you might guess Fan Art, with the other being an FAQ type (NODE/8866).
What does appear odd is that all 44 linkchecker entries in "Recent log entries" had the same information for Referer and Location :-
Referrer http://www.mydomain.com/raymond-feist/artist-corner/fan-art/benjamin-munro
Location http://www.mydomain.com/raymond-feist/artist-corner/fan-art/bill-thomas
Yet the associated message "Link http://www.mydomain.com/node/XXXX has changed and needs to be updated" related to several different content types none of which have anything to do with the urls mentioned
It is as though whatever the first "Link checker" log entry contains , is repeated for all the others for that cron session, But where they come from is a mystery too as the first entry for the session has nothing to do with the error link
Comment #3
hass commentedReferer and Location in Recent log entries have nothing valuable to say. Ignore it. The link must be in the content or in the content the view selects. The module does not create "fun" links... check out if the node/8866 have an alias and if this one is in the content... I don't know what you are doing there in your view and I don't like to guess.
Comment #4
hass commentedComment #5
Anonymous (not verified) commentedJust so you know I havn't forgotton this and the other issues I have raised, I am slowly working my way through activating one content type at a time. One problem i have been finding which is causing things to take longer is that if cron fails to complete, even if i reset the variables in the database, if Links Checker module is active, cron will not run again. So I have to disable Links Checker, reset the cron variables, and get cron to run. Then leave it for about a day, reactivate Links Checker, clearing the tables, and selecting one content type, and start the process again. if i try and reactivate Links Checker too quick, cron immedately fails, and will not run. Its a bit of a mystery, but hopefully I may find the cause soon, as I am fixing any broken links as I progress
Comment #6
hass commentedHaven't you not originally opened this case, while links are not updated automatically? I fixed a bug #425722: Permanently moved links not updated that prevents the automatic update. Hope this helps.
Feel free to close this case.
Comment #7
hass commentedNo feedback for about 5 weeks, marking as solved.