Running 3.18.8 on Debian, without a Squiz server with a PHP memmory limit of 96MB
It looks like I can only generate a link report for a maximum number of pages / or links (50 pages / 600 links ok, the section it fails on is 70 pages /10,000 links, )
If I exceed that
[codebox]arning: count() [function.count]: Node no longer exists in /data/matrix3188/fudge/dev/dev.inc on line 51
PHP Warning
File: [SYSTEM_ROOT]/packages/cms/reports/report_links/report_links_edit_fns.inc Line: 1274
Message: SimpleXMLElement::__construct() [function.SimpleXMLElement—construct]: [SYSTEM_ROOT]/data/private/assets/report_links/0006/11958/report.xml:15502: parser error : Input is not proper UTF-8, indicate encoding !
Bytes: 0xA0 0xA0 0x5D 0x5D
Backtrace: Show
Warning: count() [function.count]: Node no longer exists in /data/matrix3188/fudge/dev/dev.inc on line 51
PHP Warning
File: [SYSTEM_ROOT]/packages/cms/reports/report_links/report_links_edit_fns.inc Line: 1274
Message: SimpleXMLElement::__construct() [function.SimpleXMLElement—construct]: <html><![CDATA[http://www.slwa.wa.gov.au/pdf/battye/pods/1903/ ]]></html>
Backtrace: Show
Warning: count() [function.count]: Node no longer exists in /data/matrix3188/fudge/dev/dev.inc on line 51
PHP Warning
File: [SYSTEM_ROOT]/packages/cms/reports/report_links/report_links_edit_fns.inc Line: 1274
Message: SimpleXMLElement::__construct() [function.SimpleXMLElement—construct]: ^
Backtrace: Show
Fatal error: Uncaught exception 'Exception' with message 'Unable to parse report file "/data/matrix3188/data/private/assets/report_links/0006/11958/report.xml": String could not be parsed as XML' in /data/matrix3188/packages/cms/reports/report_links/report_links_edit_fns.inc:1276 Stack trace: #0 /data/matrix3188/core/include/asset_edit_interface.inc(1989): Report_Links_Edit_Fns->processExport(Object(Report_Links), Object(Backend_Outputter), 'report_links_11…') #1 /data/matrix3188/core/include/asset_edit_interface.inc(1729): Asset_Edit_Interface->processInline(Object(Report_Links), Object(Backend_Outputter), false, 'details') #2 /data/matrix3188/core/include/asset.inc(4376): Asset_Edit_Interface->process(Object(Report_Links), Object(Backend_Outputter), false) #3 /data/matrix3188/core/include/asset_manager_edit_fns.inc(189): Asset->processBackend(Object(Backend_Outputter), Array) #4 /data/matrix3188/core/include/asset_manager.inc(8027): Asset_Manager_Edit_Fns->paintBackend() #5 /data/matrix3188/core/include/backend.inc(13 in /data/matrix3188/packages/cms/reports/report_links/report_links_edit_fns.inc on line 1276[/codebox]
From what I can see round the forum, the report generation problem is related to memory.
Can anyone confirm that memory is the likely culprit? and any recommendations for what it should be set to get a single report of 1000 pages and 15,000 links? Or is there away to block certain folders from the link report (the difficult section is buried 4 levels deep)?
Link report failing
[quote]
From what I can see round the forum, the report generation problem is related to memory.
Can anyone confirm that memory is the likely culprit? and any recommendations for what it should be set to get a single report of 1000 pages and 15,000 links? Or is there away to block certain folders from the link report (the difficult section is buried 4 levels deep)?
[/quote]
Hi,
I'm keen to see if this has been resolved?
We've been having the same problem on 3.16.(1-7)and have our web memory set to 256 meg.
The only way we have successfully created large size link reports is by setting the Run on squiz server to "no" under the HIPO configuration.
We are also undergoing an upgrade to 3.22.6 at the moment and I'm hoping it has been fixed in the newer version.
Thanks.