Title: PHP Fatal error: Uncaught ValueError: Path cannot be empty
Last modified: June 7, 2024

---

# PHP Fatal error: Uncaught ValueError: Path cannot be empty

 *  [Stefano Lissa](https://wordpress.org/support/users/satollo/)
 * (@satollo)
 * [2 years ago](https://wordpress.org/support/topic/php-fatal-error-uncaught-valueerror-path-cannot-be-empty/)
 * Hi, running on a local env I get the fatal error:
 * [07-Jun-2024 13:04:05 UTC] PHP Fatal error: Uncaught ValueError: Path cannot 
   be empty in wp-content\plugins\plugin-check\vendor\squizlabs\php_codesniffer\
   src\Reporter.php:160
 * but the analysis of a plugin still continue (the error is triggered by one of
   the ajax calls). I don’t know if I missed some configuration or if the xampp 
   env is not ok to use it.

Viewing 1 replies (of 1 total)

 *  [Pascal Birchler](https://wordpress.org/support/users/swissspidy/)
 * (@swissspidy)
 * [1 year, 11 months ago](https://wordpress.org/support/topic/php-fatal-error-uncaught-valueerror-path-cannot-be-empty/#post-17865255)
 * Hi there,
 * Do you perhaps have any steps to reproduce for us, which plugin is this happening
   for?

Viewing 1 replies (of 1 total)

The topic ‘PHP Fatal error: Uncaught ValueError: Path cannot be empty’ is closed
to new replies.

 * ![](https://ps.w.org/plugin-check/assets/icon.svg?rev=3166100)
 * [Plugin Check (PCP)](https://wordpress.org/plugins/plugin-check/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/plugin-check/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/plugin-check/)
 * [Active Topics](https://wordpress.org/support/plugin/plugin-check/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/plugin-check/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/plugin-check/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Pascal Birchler](https://wordpress.org/support/users/swissspidy/)
 * Last activity: [1 year, 11 months ago](https://wordpress.org/support/topic/php-fatal-error-uncaught-valueerror-path-cannot-be-empty/#post-17865255)
 * Status: not resolved