Is there a reason why Matrix cannot check an anchor point within an asset when generating a Broken Links report? We generate approximately 80 reports a year and it is very time consuming if we have to check each of the anchor points because matrix cannot perform this check. The comment that we recieve is:
Link points to valid asset, but the anchor "online_purchasing" does not exist
We are running 3.6.5
Cheers
If you think the broken links report is not working, log a bug and we'll take a look into it for you.
I can confirm this is happening on the Links Report in v3.9 as well, btw. I was planning on reporting it today.
Good luck with that one. This means that checking for links now involves scanning the content. If you consider external links, that's a killer.
[quote]Good luck with that one. This means that checking for links now involves scanning the content. If you consider external links, that’s a killer.
[right][post=“9618”]<{POST_SNAPBACK}>[/post][/right][/quote]
Maybe to reduce the load, could there be options for selecting the types of links you want to check for, ie, internal or external and whether or not to include anchor point checking.
If this option were added, it would have a few optimising options.
As Greg said, if you need this, file a bug report and it should find its way into a release. If you really need it now, contact sales to book a development job.
I searched bug tracker (for "anchor") and it doesn't appear this was ever logged? Does anyone know?
The Links report is fine for links to anchors on the same page, but for links to anchors on another page it reports that the anchor does not exist.
This is also proving very time consuming for me trawling through our Links reports trying to find the real errors in amongst all these anchor errors.
I think it would be fine to resolve this issue just for internal links and not for external links if that would be problematic. However link checking software, such as Linkbot, doesn't seem to have issues checking anchors in external content?
Sarah
Sorry, I got as far as planning to report it, it seems.
Please report it, so that the developers can take a look at it. 
Hello,
I have reported this enhancement and it is listed under bug #1301.
On a side note we have increased the amount of memory allocated to Squiz Server in path/to/squiz_server/bin/start_server.php and also the amount of memory allocated to PHP to 128Mb each.
However, when viewing the largest of my broken link reports I am still getting the following error indicating a 16Mb allocation:
[quote]Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 1979135 bytes) in /mnt/apps/mysource_matrix/core/include/backend_outputter.inc on line 816[/quote]
Is there somewhere else we need to increase our memory allocation?
Thanks,
Sarah
Try increasing it in /path/to/matrix/core/web/index.php
[quote]Try increasing it in /path/to/matrix/core/web/index.php
[right][post=“9957”]<{POST_SNAPBACK}>[/post][/right][/quote]
Thanks that did the trick
Is that a precaution or have you found it to be a necessity?
Squiz server forks its processes, and in my experience I've never needed a level above 64MB. However, I don't run a lot of report hipos so ymmv ;).
[quote]Squiz server forks its processes, and in my experience I’ve never needed a level above 64MB. However, I don’t run a lot of report hipos so ymmv ;).
[right][post=“9974”]<{POST_SNAPBACK}>[/post][/right][/quote]
I found that Solaris/Oracle requires more memory than usual: for example I was unable to change the root password if I left core/web/index.php at 16mb.
Also in regards to Squiz Server, until bug #1256 is fixed, running out of memory is one of those unannounced error which isn’t great to debug.
[quote]Also in regards to Squiz Server, until bug #1256 is fixed, running out of memory is one of those unannounced error which isn’t great to debug.
[right][post=“9975”]<{POST_SNAPBACK}>[/post][/right][/quote]
Actually, I find running out of memory one of the easiest Squiz Server bugs to identify: If there is nothing in /path/to/matrix/data/private/logs/error.log and there is only a single Squiz Server process (i.e. the fork has died), then it ran out of memory.
But I agree with you – better error reporting to the browser would be very nice.
[quote]Is that a precaution or have you found it to be a necessity?
[right][post=“9973”]<{POST_SNAPBACK}>[/post][/right][/quote]
No not a necessity - we were just playing around to try and get it to work.
We do have one rather large link report that kept running out of memory before completeing so we kept increasing the memory until we realised whatever we needed was actually still stuck back on 16Mb.
We have plenty of memory on that machine so we may just leave it as is rather than reducing the allocation.