Title: php warning
Last modified: October 12, 2020

---

# php warning

 *  Resolved [Merlin Silk](https://wordpress.org/support/users/merlinsilk/)
 * (@merlinsilk)
 * [5 years, 7 months ago](https://wordpress.org/support/topic/php-warning-258/)
 * on updating the above site that uses WP AutoTerms with wp-cli I get the php warning
 * PHP Warning: Constants may only evaluate to scalar values in /home/zen/domains/
   theoctobermagazine.com/public_html/wp-content/plugins/auto-terms-of-service-and-
   privacy-policy/auto-terms-of-service-privacy-policy.php on line 61
 * on updating core, plugins and themes.
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fphp-warning-258%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 3 replies - 1 through 3 (of 3 total)

 *  [WP AutoTerms](https://wordpress.org/support/users/wpautoterms/)
 * (@wpautoterms)
 * [5 years, 7 months ago](https://wordpress.org/support/topic/php-warning-258/#post-13526902)
 * Hi there!
 * We’re aware of the issue, it’s related to the PHP version. If you update PHP 
   on the system, the error would be fix.
 * If you’re not able to update PHP on the system, please contact us so that we 
   send you the plugin next version we have which includes a bug fix for this error.
   We’re testing it fully before we release it officially.
 * [https://www.wpautoterms.com/contact.html](https://www.wpautoterms.com/contact.html)
 *  Thread Starter [Merlin Silk](https://wordpress.org/support/users/merlinsilk/)
 * (@merlinsilk)
 * [5 years, 7 months ago](https://wordpress.org/support/topic/php-warning-258/#post-13529965)
 * Hi – thank you for the answer.
    Here is what happened – just in case somebody
   runs into a similar problem: I have php56 and php74 installed and could (through
   DirectAdmin) select for each website, which of them to use. I had not updated
   fully to 7.4 because some sites use plugins that are not compliant with 7.4. 
   But the default for the system as a whole was still 5.6, so this is what wp-cli
   picked up. /usr/local/bin/php was a link to php56. I changed to that link to 
   the location of my installed php74 and like magic, wp-cli picks up the right 
   PHP and no more warnings from your plugin. Thanks again for you help.
 *  [WP AutoTerms](https://wordpress.org/support/users/wpautoterms/)
 * (@wpautoterms)
 * [5 years, 7 months ago](https://wordpress.org/support/topic/php-warning-258/#post-13529967)
 * Hi there!
 * Thanks for replying back with such detailed information!
 * For anyone else reading this message, we have 2.4.3 lined-up to be released soon.
   If the current version is still 2.4.2, contact us to get the latest version &
   test out that the error no longer appears.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘php warning’ is closed to new replies.

 * ![](https://ps.w.org/auto-terms-of-service-and-privacy-policy/assets/icon.svg?
   rev=3300987)
 * [TermsFeed AutoTerms: Privacy Policy Generator, Cookie Consent, GDPR, CCPA, Terms & Conditions, Disclaimers, Cookies Policy, EULA](https://wordpress.org/plugins/auto-terms-of-service-and-privacy-policy/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/auto-terms-of-service-and-privacy-policy/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/auto-terms-of-service-and-privacy-policy/)
 * [Active Topics](https://wordpress.org/support/plugin/auto-terms-of-service-and-privacy-policy/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/auto-terms-of-service-and-privacy-policy/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/auto-terms-of-service-and-privacy-policy/reviews/)

## Tags

 * [PHP Warning](https://wordpress.org/support/topic-tag/php-warning/)
 * [wp autoterms](https://wordpress.org/support/topic-tag/wp-autoterms/)

 * 3 replies
 * 2 participants
 * Last reply from: [WP AutoTerms](https://wordpress.org/support/users/wpautoterms/)
 * Last activity: [5 years, 7 months ago](https://wordpress.org/support/topic/php-warning-258/#post-13529967)
 * Status: resolved