linkcheck.php

Next topic

Author	Message
Kenneth Colwell	Friday 14 May 2004 7:07:25 am Hey I think it's great that there is a cronjob script to check for broken links. However, it would be much more useful if it actually told you what article on the site contains the bad link. Thanks, Ken Colwell for example here is some output: check-http://www.dsc.edu/library/index.html invalid check-http://wwwlib.uncfsu.edu/ invalid check-http://www.hsc.edu/fac/lib invalid check-http://www.king.edu/library/gdoct.htm invalid check-http://www.lib.lfc.edu/ invalid check-http://www.lclark.edu/~refdesk/resources/subject/webgov.html invalid
Mark Marsiglio	Monday 17 May 2004 7:19:04 pm In the admin, click on the setup tab. Then the URL Management section provides an interface for seeing valid and invalid links. If you look at the invalid list, you can click on a link (click on the URL part) and it will tell you where it points and what content object(s) use it. http://www.thinkcreative.com Turning Ideas Into Strategic Solutions

Author

Message

Friday 14 May 2004 7:07:25 am

Hey I think it's great that there is a cronjob script to check for broken links. However, it would be much more useful if it actually told you what article on the site contains the bad link.

Thanks,
Ken Colwell

for example here is some output:

check-http://www.dsc.edu/library/index.html invalid
check-http://wwwlib.uncfsu.edu/ invalid
check-http://www.hsc.edu/fac/lib invalid
check-http://www.king.edu/library/gdoct.htm invalid
check-http://www.lib.lfc.edu/ invalid
check-http://www.lclark.edu/~refdesk/resources/subject/webgov.html invalid

Mark Marsiglio

Monday 17 May 2004 7:19:04 pm

In the admin, click on the setup tab. Then the URL Management section provides an interface for seeing valid and invalid links.

If you look at the invalid list, you can click on a link (click on the URL part) and it will tell you where it points and what content object(s) use it.

http://www.thinkcreative.com
Turning Ideas Into Strategic Solutions

eZ debug

Timing:	Jan 18 2025 15:19:36
Script start
Timing:	Jan 18 2025 15:19:36
Module start 'layout'
Timing:	Jan 18 2025 15:19:36
Module start 'content'
Timing:	Jan 18 2025 15:19:36
Module end 'content'
Timing:	Jan 18 2025 15:19:36
Script end

Main resources:

Total runtime	0.0159 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0058	587.7891	152.6094
Module start 'layout'	0.0058	0.0029	740.3984	39.4141
Module start 'content'	0.0088	0.0050	779.8125	89.2891
Module end 'content'	0.0137	0.0022	869.1016	30.3047
Script end	0.0159		899.4063

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0027	16.6657	14	0.0002
Check MTime	0.0011	7.2209	14	0.0001
Mysql Total
Database connection	0.0008	4.9492	1	0.0008
Mysqli_queries	0.0026	16.2299	3	0.0009
Looping result	0.0000	0.0884	1	0.0000
Template Total	0.0018	11.0	1	0.0018
Template load	0.0009	5.7654	1	0.0009
Template processing	0.0008	5.1993	1	0.0008
Override
Cache load	0.0006	3.8007	1	0.0006
General
dbfile	0.0002	1.5529	8	0.0000
String conversion	0.0000	0.0629	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs