Title: PHP warning
Last modified: June 9, 2020

---

# PHP warning

 *  [John](https://wordpress.org/support/users/dsl225/)
 * (@dsl225)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/php-warning-238/)
 * I’m getting this lately:
 * `Warning: "continue" targeting switch is equivalent to "break". Did you mean 
   to use "continue 2"? in /wp-content/plugins/wp-crm/lib/class_default_api.php 
   on line 693`
 * Any clues?

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

 *  Thread Starter [John](https://wordpress.org/support/users/dsl225/)
 * (@dsl225)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/php-warning-238/#post-13034126)
 * Still getting those warnings and now even more for the addons since I activated
   them:
 *     ```
       Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /wp-content/plugins/wp-invoice/addons/wp-invoice-pdf/lib/third-party/dompdf/src/Renderer/Text.php on line 140
   
       Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /wp-content/plugins/wp-invoice/addons/wp-invoice-pdf/lib/third-party/dompdf/src/Css/Stylesheet.php on line 1360
   
       Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /wp-content/plugins/wp-invoice/addons/wp-invoice-pdf/lib/third-party/dompdf/lib/Cpdf.php on line 488
   
       Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /wp-content/plugins/wp-invoice/addons/wp-invoice-pdf/lib/third-party/dompdf/lib/Cpdf.php on line 481
   
       Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /wp-content/plugins/wp-invoice/addons/wp-invoice-pdf/lib/third-party/dompdf/lib/Cpdf.php on line 474
   
       Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /wp-content/plugins/wp-invoice/addons/wp-invoice-pdf/lib/third-party/dompdf/lib/Cpdf.php on line 467
   
       Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /wp-content/plugins/wp-invoice/addons/wp-invoice-pdf/lib/third-party/dompdf/src/Dompdf.php on line 631
   
       Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /wp-content/plugins/wp-invoice/addons/wp-invoice-pdf/lib/third-party/dompdf/src/Dompdf.php on line 610
       ```
   
 *  [Tony](https://wordpress.org/support/users/tmalonemktg/)
 * (@tmalonemktg)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/php-warning-238/#post-13166785)
 * [@dsl225](https://wordpress.org/support/users/dsl225/) I am getting the same 
   warnings and error messages and it seems to be continuously running did you ever
   find a solution or speak with [@usability_dynamics](https://wordpress.org/support/users/usability_dynamics/)?
 *  [thebarkacademy](https://wordpress.org/support/users/thebarkacademy/)
 * (@thebarkacademy)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/php-warning-238/#post-13166871)
 * I have repeatedly asked for help from Usability Dynamics. They do not respond
   to any of our support threads. I went to their website [https://www.usabilitydynamics.com/](https://www.usabilitydynamics.com/)
   and sent a message there. Here is the response I got weeks later:
 * Hey Melissa,
 * Thank You for using our products. We will fix this issue and you can update it
   in next version of plugin.
 * This was sent to me on March 9, 2020 from this email address: [support@udx.io-2.hs-inbox.com](https://wordpress.org/support/topic/php-warning-238/support@udx.io-2.hs-inbox.com?output_format=md)
 * I’m still waiting on the promised update.
 *  [Tony](https://wordpress.org/support/users/tmalonemktg/)
 * (@tmalonemktg)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/php-warning-238/#post-13167721)
 * [@dsl225](https://wordpress.org/support/users/dsl225/) [@thebarkacademy](https://wordpress.org/support/users/thebarkacademy/)
   from research I see that it seems to be an issue from upgrading to the latest
   PHP. I’m on 7.4. I don’t want to scale back down but this error file grows quite
   large in a day.
 * [https://github.com/Automattic/o2/issues/165](https://github.com/Automattic/o2/issues/165)
 * Only issue i’m having is line 693 is blank on my .php file…
 *  Thread Starter [John](https://wordpress.org/support/users/dsl225/)
 * (@dsl225)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/php-warning-238/#post-13167927)
 * [@tmalonemktg](https://wordpress.org/support/users/tmalonemktg/) still getting
   all those errors and I’m on 7.3
 *  [argent41](https://wordpress.org/support/users/argent41/)
 * (@argent41)
 * [5 years, 8 months ago](https://wordpress.org/support/topic/php-warning-238/#post-13178423)
 * Here is what my host did for me.
 * > This error message suggests that the wp-crm plugin is not compatible with PHP
   > 7.4. If it doesn’t break the website, it is possible to ignore this error. 
   > If you want to hide the error message from the website, you should change the
   > following value from:
   >  error_reporting = E_ALL & ~E_STRICT & ~E_NOTICE & ~E_DEPRECATED
   > to error_reporting = 0 in the global php.ini file.
   > We also added the following line to the global php.ini for your account to 
   > disable the displaying of PHP errors:
   > display_errors = 0
 * This worked for me.
 *  Thread Starter [John](https://wordpress.org/support/users/dsl225/)
 * (@dsl225)
 * [5 years, 8 months ago](https://wordpress.org/support/topic/php-warning-238/#post-13178886)
 * [@argent41](https://wordpress.org/support/users/argent41/)
    Thanks for this but
   I would not recommend doing this. First, I’m getting this error on PHP 7.3, so
   it’s not specifically related to version 7.4
 * Then, it is certainly not a good practice hiding errors, as this code simply 
   hides ALL of them but not solving anything. This present notification is simply
   a warning with no serious consequences for the moment but by hiding all errors
   the system might encounter in the future is like one saying to himself “I’m not
   sick” while he suffers from disease…
 *  [argent41](https://wordpress.org/support/users/argent41/)
 * (@argent41)
 * [5 years, 8 months ago](https://wordpress.org/support/topic/php-warning-238/#post-13179015)
 * Yes, I understand the ramifications of turning a blind eye, but what can you 
   do if your site is marred by a scary warning for the world to see and plugin 
   support won’t do anything.
    Stuck between a rock and a hard place – a warning
   to upgrade your insecure PHP version or put up with graffiti on your website.
 *  Thread Starter [John](https://wordpress.org/support/users/dsl225/)
 * (@dsl225)
 * [5 years, 8 months ago](https://wordpress.org/support/topic/php-warning-238/#post-13179051)
 * [@argent41](https://wordpress.org/support/users/argent41/) those warnings don’t
   display on visitors!
    Only admins can see them!
 *  [argent41](https://wordpress.org/support/users/argent41/)
 * (@argent41)
 * [5 years, 8 months ago](https://wordpress.org/support/topic/php-warning-238/#post-13179515)
 * Thanks for the heads up on that John, good to know.
 *  [Tony](https://wordpress.org/support/users/tmalonemktg/)
 * (@tmalonemktg)
 * [5 years, 7 months ago](https://wordpress.org/support/topic/php-warning-238/#post-13365379)
 * Just coming back through to see if there were any updates. Yes while visitor 
   cannot see the error logs, the error logs grow quite large rather quickly on 
   your severe and cause your website to load slower than usual…
 *  [argent41](https://wordpress.org/support/users/argent41/)
 * (@argent41)
 * [5 years, 7 months ago](https://wordpress.org/support/topic/php-warning-238/#post-13365475)
 * Good point Tony, do you know if server admin can delete these logs?
    Best in 
   the long run to find and fix the source of the error messages right?
    -  This reply was modified 5 years, 7 months ago by [argent41](https://wordpress.org/support/users/argent41/).
 *  Thread Starter [John](https://wordpress.org/support/users/dsl225/)
 * (@dsl225)
 * [5 years, 7 months ago](https://wordpress.org/support/topic/php-warning-238/#post-13365492)
 * No updates yet, but those are simple warnings and do not cause any issues.
    You
   can safely delete them by connecting to your site’s root by FTP.
 *  [Tony](https://wordpress.org/support/users/tmalonemktg/)
 * (@tmalonemktg)
 * [5 years, 7 months ago](https://wordpress.org/support/topic/php-warning-238/#post-13366583)
 * [@argent41](https://wordpress.org/support/users/argent41/) yes I have access 
   to my hosting servers via FTP, but I end up having to erase them every 3 or for
   days because it continuously runs up to over 2 megabytes a day.

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

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

 * ![](https://s.w.org/plugins/geopattern-icon/wp-crm_c36510.svg)
 * [WP-CRM - Customer Relations Management for WordPress](https://wordpress.org/plugins/wp-crm/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-crm/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-crm/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-crm/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-crm/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-crm/reviews/)

 * 14 replies
 * 4 participants
 * Last reply from: [Tony](https://wordpress.org/support/users/tmalonemktg/)
 * Last activity: [5 years, 7 months ago](https://wordpress.org/support/topic/php-warning-238/#post-13366583)
 * Status: not resolved