Title: Critical Error with Formidable
Last modified: August 3, 2021

---

# Critical Error with Formidable

 *  Resolved [michaelnewsomejr](https://wordpress.org/support/users/michaelnewsomejr/)
 * (@michaelnewsomejr)
 * [4 years, 10 months ago](https://wordpress.org/support/topic/critical-error-with-formidable/)
 * When I set the server to PHP v7.2, the entire wp-admin dashboard gives the “There
   has been a critical error on this website. Please check your site admin email
   inbox for instructions.”
 * However, if I deactivate Formidable Pro (leaving only Formidable Lite), then 
   the error only appears on the Formidable pages. I am able to access and edit 
   the rest of my dashboard.
 * I have Formidable 4.11.05, PHP v7.2, and WordPress v5.8.
 * Thanks,
    Michael

Viewing 1 replies (of 1 total)

 *  Plugin Support [Njones35](https://wordpress.org/support/users/njones35/)
 * (@njones35)
 * [4 years, 10 months ago](https://wordpress.org/support/topic/critical-error-with-formidable/#post-14733065)
 * Hi [@michaelnewsomejr](https://wordpress.org/support/users/michaelnewsomejr/)
 * Thank you for contacting our support team today. My name is Nathanael and I will
   do my best to help you get this resolved ASAP.
 * Formidable is fully tested and compatible up to PHP 8, so running 7.2, while 
   outdated should not cause any issues at all.
 * I’ve tried to reproduce this issue on my dev site, but have not yet had any success.
   We’ve also not received any reports of similar issues from other users recently.
   I suspect there may be something unique to your setup that is causing this.
 * It would be helpful to test to see if anything on your site is interfering with
   Formidable and causing the issue. Could you please go through the following steps?
   
   [https://formidableforms.com/knowledgebase/what-plugins-are-known-to-cause-conflicts/#kb-how-to-find-a-conflict](https://formidableforms.com/knowledgebase/what-plugins-are-known-to-cause-conflicts/#kb-how-to-find-a-conflict)
 * If the issue doesn’t show up while your website is running under these default
   conditions, you can reactivate your plugins, one at a time, and test after each
   activation to see when the issue reappears. When it does, the last plugin activated
   is the likely source of your problems.
    ———-
 * We understand that testing like this on a live site isn’t always possible, so
   we recommend doing this testing on a copy of the site (a staging site) instead.
   If you put the staging site on staging.yoursite.com or dev.yoursite.com, you 
   won’t need an extra Formidable license to activate it.
 * Some hosts have an easy way to create a staging site. If yours doesn’t, you can
   copy your site using free plugins like
    All in One WP Migration, Duplicator, 
   or any other plugin or system you like. Your host may also be willing to create
   a staging site for you if you ask.
 * Since you are using Pro, and we can only support our Lite plugin here, if you
   need any further assistance could you please open a ticket in our helpdesk? [https://formidableforms.com/new-topic/](https://formidableforms.com/new-topic/)
 * Thank you!

Viewing 1 replies (of 1 total)

The topic ‘Critical Error with Formidable’ is closed to new replies.

 * ![](https://ps.w.org/formidable/assets/icon-256x256.png?rev=2588749)
 * [Formidable Forms - Contact Form Plugin, Survey, Quiz, Payment, Calculator Form & Custom Form Builder](https://wordpress.org/plugins/formidable/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/formidable/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/formidable/)
 * [Active Topics](https://wordpress.org/support/plugin/formidable/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/formidable/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/formidable/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Njones35](https://wordpress.org/support/users/njones35/)
 * Last activity: [4 years, 10 months ago](https://wordpress.org/support/topic/critical-error-with-formidable/#post-14733065)
 * Status: resolved