Scans and checks
- When scans runScans run every day, after site changes and when you start one.
- What starts a scanEach reason a scan starts, as History names it, and the site changes that start one.
- Start a scanStart a scan yourself, for example to check a fix.
- Scan stagesThe stages a scan shows while it runs, and what happens in each.
- Scanning a live siteA scan reads and reports, and never changes your site.
- What a scan coveredCoverage shows what the latest scan checked, package by package.
- The file integrity checkHow WP Rooster compares installed files with their published releases, and how serious each difference is.
- Custom and commercial themes and pluginsHow Monitoring checks themes and plugins that are not on WordPress.org.
- No published reference and Comparison incompleteWhat it means when files could not be compared with a reference release.
- Which code is reviewedCode review covers your own custom code, and runs after each scan.
- What code review looks forThe problems code review reports, and where in your code it starts.
- Turn off code analysis for a plugin or themeChoose which plugins and themes WP Rooster analyzes as custom code.
- Code quality gradesHow easy each part of your own code is to maintain, graded by AI.
- Enable or disable a check, or change the scan timeChoose which checks run on a site, what starts a scan and when the daily scan runs.
- Monitoring settingsEvery setting on a site’s Monitoring page, with what it does.
- A scan stopped or takes longWhy a scan can stop before it finishes, and what to do about it.