Title: WP version 5.7 incompatibility?
Last modified: March 12, 2021

---

# WP version 5.7 incompatibility?

 *  Resolved [spile](https://wordpress.org/support/users/spile/)
 * (@spile)
 * [5 years, 3 months ago](https://wordpress.org/support/topic/wp-version-5-7-incompatibility/)
 * I have just upgraded to version 5.7 of WordPress and attempting to edit WP resulted
   in a critical error.
    I used FTP to disable my plugins and was then able to access
   the dashboard. I activated each plugin in turn. When I enabled Twentig 1.2.7,
   I got the critical error message and was unable to access the dashboard.

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

 *  Plugin Author [Twentig](https://wordpress.org/support/users/twentig/)
 * (@twentig)
 * [5 years, 3 months ago](https://wordpress.org/support/topic/wp-version-5-7-incompatibility/#post-14173917)
 * Hi [@spile](https://wordpress.org/support/users/spile/),
 * Thanks for your feedback and sorry for the inconvenience. We are not aware of
   any 5.7 incompatibility issues. Could you please copy and paste the error message?
 * Thanks,
    Tom
 *  Thread Starter [spile](https://wordpress.org/support/users/spile/)
 * (@spile)
 * [5 years, 3 months ago](https://wordpress.org/support/topic/wp-version-5-7-incompatibility/#post-14173930)
 * This is the error when the plugin is enabled…
    “There has been a critical error
   on this website. Please check your site admin email inbox for instructions.
 * Learn more about troubleshooting WordPress.”
    -  This reply was modified 5 years, 3 months ago by [spile](https://wordpress.org/support/users/spile/).
 *  Plugin Author [Twentig](https://wordpress.org/support/users/twentig/)
 * (@twentig)
 * [5 years, 3 months ago](https://wordpress.org/support/topic/wp-version-5-7-incompatibility/#post-14174031)
 * Thanks for your reply. Do you have any more info? What are the instructions you
   received in the email? As it’s forbidden for us to ask for any kind of access
   in order to provide support, it’s difficult to diagnose the issue.
 * To be sure, the issue appears when Twentig 1.2.7 is activated, and there are 
   no other plugins activated?
 * Could you please try to install Twentig v1.2.6 to test if there’s the same issue?
   You can download it at the bottom of this page [https://wordpress.org/plugins/twentig/advanced/](https://wordpress.org/plugins/twentig/advanced/)
   under “Please select a specific version to download.”
 *  Thread Starter [spile](https://wordpress.org/support/users/spile/)
 * (@spile)
 * [5 years, 3 months ago](https://wordpress.org/support/topic/wp-version-5-7-incompatibility/#post-14176265)
 * Thank you for a quick response. There was an issue on the server with PHP memory
   limits. These have been increased from 512 M to 1024 M and the plugin is working
   again.
 *  Plugin Author [Twentig](https://wordpress.org/support/users/twentig/)
 * (@twentig)
 * [5 years, 3 months ago](https://wordpress.org/support/topic/wp-version-5-7-incompatibility/#post-14176400)
 * Thanks for the heads-up, glad it solves the issue.
 * If you enjoy Twentig, [please rate it](https://wordpress.org/support/plugin/twentig/reviews/).
   It would really help me out 🙂
 * Tom

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

The topic ‘WP version 5.7 incompatibility?’ is closed to new replies.

 * ![](https://ps.w.org/twentig/assets/icon.svg?rev=2569439)
 * [Twentig Supercharged Block Editor – Blocks, Patterns, Starter Sites, Portfolio](https://wordpress.org/plugins/twentig/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/twentig/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/twentig/)
 * [Active Topics](https://wordpress.org/support/plugin/twentig/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/twentig/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/twentig/reviews/)

 * 5 replies
 * 2 participants
 * Last reply from: [Twentig](https://wordpress.org/support/users/twentig/)
 * Last activity: [5 years, 3 months ago](https://wordpress.org/support/topic/wp-version-5-7-incompatibility/#post-14176400)
 * Status: resolved