Title: PHP 7.0 Compatibility Error
Last modified: June 30, 2018

---

# PHP 7.0 Compatibility Error

 *  Resolved [hikingdog](https://wordpress.org/support/users/hikingdog/)
 * (@hikingdog)
 * [7 years, 11 months ago](https://wordpress.org/support/topic/php-7-0-compatibility-error-2/)
 * FILE: /nas/content/live/sectionhiker/wp-content/plugins/fast-velocity-minify/
   inc/functions.php
    ———————————————————————————————- FOUND 1 ERROR AFFECTING 1
   LINE ———————————————————————————————- 198 | ERROR | The constant “PHP_OS_FAMILY”
   is not present in PHP version 7.1 or earlier ———————————————————————————————-

Viewing 1 replies (of 1 total)

 *  Plugin Author [Raul P.](https://wordpress.org/support/users/alignak/)
 * (@alignak)
 * [7 years, 11 months ago](https://wordpress.org/support/topic/php-7-0-compatibility-error-2/#post-10450523)
 * That is probably some compatibility tool you are running, but you can safely 
   ignore it.
    That tool detects that the code exists, but it doesn’t know what 
   it does or how it’s used.
 * The plugin works fine with php 5.6, 7.0, 7.1 and 7.2.
 * The constant “PHP_OS_FAMILY”, while not present in PHP version 7.1 or earlier,
   will only be used if you have PHP 7.1, but ignored if you don’t.

Viewing 1 replies (of 1 total)

The topic ‘PHP 7.0 Compatibility Error’ is closed to new replies.

 * ![](https://ps.w.org/fast-velocity-minify/assets/icon-128x128.jpg?rev=1440946)
 * [Fast Velocity Minify](https://wordpress.org/plugins/fast-velocity-minify/)
 * [Support Threads](https://wordpress.org/support/plugin/fast-velocity-minify/)
 * [Active Topics](https://wordpress.org/support/plugin/fast-velocity-minify/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/fast-velocity-minify/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/fast-velocity-minify/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Raul P.](https://wordpress.org/support/users/alignak/)
 * Last activity: [7 years, 11 months ago](https://wordpress.org/support/topic/php-7-0-compatibility-error-2/#post-10450523)
 * Status: resolved