Title: Fatal error upon activation
Last modified: February 17, 2019

---

# Fatal error upon activation

 *  [paulinelephew](https://wordpress.org/support/users/paulinelephew/)
 * (@paulinelephew)
 * [7 years, 3 months ago](https://wordpress.org/support/topic/fatal-error-upon-activation-37/)
 * Hi guys, when activating the plugin the entire site crashes with the following
   message, anyone to help please?
    Thank you!
 * Fatal error: Uncaught Error: Call to undefined function pll_get_post() in /htdocs/
   wp-content/plugins/404page/inc/class-404page.php:1332 Stack trace: #0 /htdocs/
   wp-content/plugins/404page/inc/class-404page.php(918): PP_404Page->get_page_id()#
   1 /htdocs/wp-includes/class-wp-hook.php(286): PP_404Page->exclude_404page(Object(
   WP_Query)) #2 /htdocs/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(
   NULL, Array) #3 /htdocs/wp-includes/plugin.php(515): WP_Hook->do_action(Array)#
   4 /htdocs/wp-includes/class-wp-query.php(1634): do_action_ref_array(‘pre_get_posts’,
   Array) #5 /htdocs/wp-includes/class-wp-query.php(3230): WP_Query->get_posts()#
   6 /htdocs/wp-includes/post.php(1763): WP_Query->query(Array) #7 /htdocs/wp-content/
   plugins/contact-form-7-mailchimp-extension/lib/tools.php(119): get_posts(Array)#
   8 /htdocs/wp-content/plugins/contact-form-7-mailchimp-extension/lib/tools.php(
   106): mc_get_latest_item() #9 /htdocs/wp-includes/class-wp-hook.php(286): mce_init_constants(”)#
   10 /htdocs/wp-includes/class-wp-hook.php(310): WP in /htdocs/wp-content/plugins/
   404page/inc/class-404page.php on line 1332

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

 *  [latigresa9653](https://wordpress.org/support/users/latigresa9653/)
 * (@latigresa9653)
 * [7 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-upon-activation-37/#post-11216375)
 * I would like to see a resolution to this error before activation on a CapeOne
   theme ver. 1.0.8 by VelaThemes
 *  [latigresa9653](https://wordpress.org/support/users/latigresa9653/)
 * (@latigresa9653)
 * [7 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-upon-activation-37/#post-11216382)
 * Did you see/read this: Take care that your theme must come with the corresponding.
   mo files (Polylang automatically downloads them when they are available for themes
   and plugins in this repository). If your theme is not internationalized yet, 
   please refer to the Theme Handbook or ask the theme author to internationalize
   it. I am aware that my theme comes “Polylang ready” but still skeptical.
 *  Plugin Author [Chouby](https://wordpress.org/support/users/chouby/)
 * (@chouby)
 * [7 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-upon-activation-37/#post-11219332)
 * Hello,
 * As far as I read the error message, the error is in the plugin “404page”. Please
   check with the support of this plugin to see what’s wrong.
 *  Thread Starter [paulinelephew](https://wordpress.org/support/users/paulinelephew/)
 * (@paulinelephew)
 * [7 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-upon-activation-37/#post-11226670)
 * [@chouby](https://wordpress.org/support/users/chouby/) sorry but even when plugin
   deactivated polylang still breaks my site
    Theme is Bridge and I believe it’s
   translation ready Thank you!
 *  Plugin Author [Chouby](https://wordpress.org/support/users/chouby/)
 * (@chouby)
 * [7 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-upon-activation-37/#post-11227711)
 * What’s the new error message once you have deactivated the plugin “404page”?
 *  [latigresa9653](https://wordpress.org/support/users/latigresa9653/)
 * (@latigresa9653)
 * [7 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-upon-activation-37/#post-11228680)
 * yes
 *  [latigresa9653](https://wordpress.org/support/users/latigresa9653/)
 * (@latigresa9653)
 * [7 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-upon-activation-37/#post-11228688)
 * once the polylang and lingotek plugins are deactivated site is restored
 *  [codestylist](https://wordpress.org/support/users/codestylist/)
 * (@codestylist)
 * [7 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-upon-activation-37/#post-11228919)
 * [@latigresa9653](https://wordpress.org/support/users/latigresa9653/) Just to 
   make sure you understand: When a plugin is deactivated it can not break anything
   of a website because the code will not run. So, the problem comes from somewhere
   else.
 *  [latigresa9653](https://wordpress.org/support/users/latigresa9653/)
 * (@latigresa9653)
 * [7 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-upon-activation-37/#post-11229466)
 * Sorry… What I am saying is that when Polylang is active my site shows only 404
   but deactivate Polylang and all is good
 *  [juanavall](https://wordpress.org/support/users/juanavall/)
 * (@juanavall)
 * [7 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-upon-activation-37/#post-11245745)
 * It looks similar to the [error](https://wordpress.org/support/topic/woocommerce-polylang-pro-hostgator-error-524/)
   that appears when I want to make a new translation with Polylang Pro + Polylang
   for Woocommerce.

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

The topic ‘Fatal error upon activation’ is closed to new replies.

 * ![](https://ps.w.org/polylang/assets/icon-256x256.png?rev=3433336)
 * [Polylang](https://wordpress.org/plugins/polylang/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/polylang/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/polylang/)
 * [Active Topics](https://wordpress.org/support/plugin/polylang/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/polylang/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/polylang/reviews/)

 * 10 replies
 * 5 participants
 * Last reply from: [juanavall](https://wordpress.org/support/users/juanavall/)
 * Last activity: [7 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-upon-activation-37/#post-11245745)
 * Status: not resolved