I'm trying to get an accurate Report on how many pages are is a site from the users's point of view. I tried the following report and would like advice on whether it looks reasonable or looks like it left anything obviopus out.
In a Structured Asset Report I selected pages and documents that are live, up for review or under safe edit. These are all the ‘real’ pages and downloadable documents that a user might see from the front end. I left out assets or images that are nested into ‘real’ pages.
The asset types I selected were:
Standard Page
MS Excel Document
File
MS PowerPoint Document
MS Word Document
News Item
Asset Listing Page
Custom Form
Related Asset Listing Page
Site Map
Whats New
PDF File
RTF File
Text File
Hey Richard
Please define 'real pages'. Are you looking to just generate a report (asset listing) of all assets that you think a public user might be able to see from a browser?
If so it might be less intensive to run a custom DB query (use DB Data Source) and asset list from that. Something like 'get all assets underneath site asset X that are status A,B,C and have plublic read permission' then create an asset listing from those results and format to suite.
You could even format the asset listing to generate output suitable for Excel.
Id suggest having a chat with your local Technical Consultant / Project Manager / Accounts Manager for implementation support if needed.