You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by an end user, if viewing the Reports section when inside a subsite, generating this report will show results from all sites. The expected behaviour would be the same as other reports, where they only show results that are relevant for that particular subsite.
I believe the issue stems from the fact that this report runs as a task, which won't have any context of the subsite, unlike other reports that run straight away and have Subsites inject its standard subsite-specific WHERE clauses injected into their queries.
The text was updated successfully, but these errors were encountered:
I believe the issue stems from the fact that this report runs as a task, which won't have any context of the subsite, unlike other reports that run straight away and have Subsites inject its standard subsite-specific WHERE clauses injected into their queries.
That's likely to be true, but we could still provide some context to the job when we trigger it to be run via AJAX
When I try the same, I can only see broken links for the main site, and not for any subsites at all.
The report menu option is not visible to me in the CMS, when I have a subsite is selected. However, I can open the report through the main site in the CMS and then navigate to the subsite via the dropdown. The broken links in the report are only shown for the main site though.
Reported by an end user, if viewing the Reports section when inside a subsite, generating this report will show results from all sites. The expected behaviour would be the same as other reports, where they only show results that are relevant for that particular subsite.
I believe the issue stems from the fact that this report runs as a task, which won't have any context of the subsite, unlike other reports that run straight away and have Subsites inject its standard subsite-specific WHERE clauses injected into their queries.
The text was updated successfully, but these errors were encountered: