=== Safe Headers Scanner ===
Contributors: tohidlo
Donate link: https://tohidlo.com
Tags: headers, scanner, security, plugins, debug
Requires at least: 5.0
Tested up to: 6.8
Stable tag: 1.2
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Scan themes and plugins for potential header issues such as whitespace before/after PHP tags or direct output before headers.

== Description ==
Safe Headers Scanner helps WordPress administrators identify common issues that may cause header-related problems.  
The plugin scans installed themes and plugins for:
* Unnecessary whitespace before `<?php` tags
* Extra whitespace after closing `?>` tags
* Direct output (e.g., `echo`, `print`) before headers are sent

Results are displayed in a clear report, so you can review and fix potential issues easily.

== Installation ==
1. Upload the `safe-headers-scanner` folder to the `/wp-content/plugins/` directory.
2. Activate the plugin through the 'Plugins' menu in WordPress.
3. Go to **Tools > Safe Headers Scanner** to scan your themes or plugins.

== Frequently Asked Questions ==
= Does this plugin automatically fix issues? =  
No. It only scans and reports possible issues. You need to manually review and fix them.

= Will it slow down my website? =  
No. The scan only runs when you request it from the admin panel. It does not affect frontend performance.

== Changelog ==
= 1.0 =
* Initial release.
= 1.1 =
* Fixed path handling by replacing hardcoded WP_CONTENT_DIR references with get_theme_root() and WP_PLUGIN_DIR.  
* Improved asset handling by replacing inline <script> and <style> with wp_register_script(), wp_add_inline_script() and wp_add_inline_style().  
* Added explicit versioning for enqueued resources to comply with WordPress coding standards. 
= 1.2 =
* Replaced WP_PLUGIN_DIR with plugin_dir_path() for improved compatibility with non-standard WordPress setups.