Debug mode on but no logs? Ensure WordPress or FleekDash logging is configured (e.g. WP_DEBUG_LOG) and the log file path is writable. If the admin has a log viewer, use it to confirm entries are being written. Check file permissions on the server if logs still don't appear.
Performance options missing? The exact options (caching, DB optimization, asset optimization) depend on your FleekDash version and plan. If a section is empty or minimal, check the product docs or release notes for your build.
Labs feature broke something? Disable the Labs feature in Settings → Fleek Labs and save. If the issue persists, clear cache and reload. Report bugs so the team can improve the feature.
Safe for production? Debug mode and verbose logging can expose sensitive data. Use debug on staging or temporarily on production; turn it off when not troubleshooting. Labs features are experimental. Enable only if you accept possible instability. Performance options (caching, DB) are generally safe; always back up before running database operations.
Quick reference
| What | Where |
Debug Settings | Settings → Debug Settings → #/settings/debug (debug mode, logging, log viewer, auto-clear) |
Performance | Settings → Performance → #/settings/performance (caching, DB optimization, assets) |
Fleek Labs | Settings → Fleek Labs → #/settings/labs (experimental feature toggles) |
Save | Per section; click Save in the active panel to apply changes |
Related documentation: Settings Center (overall layout and sections), Integrations Hub (stack and tools that may affect performance).