How to move the active log outside the public web root and manage files safely
Debug logs can contain sensitive technical information. Titanium can preserve an existing private custom path or create its own plugin-specific private location and move the active log there when the server allows the change.
Protect the log and use file actions
- Review the Log location card and check whether the current configured path is inside or outside the public web root.
- If the path is public and wp-config.php is writable, enable Store log outside the public web root.
- After the move, run the Monitoring Self-Test again to verify write and read access at the new location.
- Use Download before destructive cleanup when you may need the old history later.
- Use Rename only when you understand that changing the filename does not change WP_DEBUG_LOG; WordPress can recreate the original configured filename on the next log entry.
- Use Empty Log or Delete File only after confirming the stored history is no longer needed.
