Hello,
We're currently testing the module in our development environment, and have already spidered everything on the site to "trigger" the module. However, our site has many customizations done to it and believe that it may affecting the module's performance in our instance. We've noticed while looking in the reports generated by the Views Auditor, it does not specify the node ID, rather it displays this type of result.
We understand that this will require modifications to the module, which we will gladly do ourselves if necessary. We'd just appreciate it if you could point us in the right direction towards reaching that solution.
Thanks in advance!
| Comment | File | Size | Author |
|---|---|---|---|
| drupal_views_usage_audit.png | 90.97 KB | eleiter |
Comments
Comment #2
alanmackenzie commentedThis was a deliberate design decision as capturing unique paths for a site with 500,000 unique URLs might pose a scalability problem.
I can see why it would be useful for smaller sites though, making this change to the module would require modification to a large % of the modules codebase, not a trivial change unfortunately.