Title: getting Fatal error
Last modified: January 22, 2023

---

# getting Fatal error

 *  Resolved [Md Babul Islam](https://wordpress.org/support/users/developmenttestphp/)
 * (@developmenttestphp)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/getting-fatal-error-34/)
 * WP_User_Query->__construct(Array) #3 /home/mortujbi/public_html/projects/qwikleaf/
   wp-content/plugins/wordpress-seo/inc/sitemaps/class-author-sitemap-provider.php(
   237): get_users(Array) #4 /home/mortujbi/public_html/projects/qwikleaf/wp-content/
   plugins/wordpress-seo/inc/sitemaps/class-author-sitemap-provider.php(45): WPSEO_Author_Sitemap_Provider-
   >update_user_meta() #5 /home/mortujbi/public_html/projects/qwikleaf/wp-content/
   plugins/wordpress-seo/inc/sitemaps/class-sitemaps.php(392): WPSEO_Author_Sitemap_Provider-
   >get_index_links(1000) #6 /home/mortujbi/public_html/projects/qwikleaf/wp-content/
   plugins/wordpress-seo/inc/sitemaps/class-sitemaps.php(346): WPSEO_Sitemaps->build_root_map()#
   7 /home/mortujbi/public_html/projects/qwikleaf/wp-content/plugins/wordpress-seo/
   inc/sitemaps/class-sitemaps.php(261): WPSEO_Sitemaps->build_sitemap(‘1’)
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fgetting-fatal-error-34%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

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

 *  [Suwash Kunwar](https://wordpress.org/support/users/suascat_wp/)
 * (@suascat_wp)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/getting-fatal-error-34/#post-16398831)
 * [@developmenttestphp](https://wordpress.org/support/users/developmenttestphp/)
 * Often, we see problems occur in combination with another plugin or theme. The
   fastest way to rule out any conflict is to **deactivate all non-Yoast plugins
   and switch to a standard theme** like [Twenty Twenty](https://wordpress.org/themes/twentytwenty/).
 * Please test this on your development or staging site if you have one. If not,
   we recommend using the [Health Check & Troubleshooting](https://wordpress.org/plugins/health-check/)
   plugin. This plugin has a troubleshooting mode, which **does not affect normal
   visitors to your site**.
 * If you’re unfamiliar with checking for conflicts, we’d like to point you to a
   step-by-step guide that will walk you through the process: [How to check for plugin conflicts](https://yoast.com/help/how-to-check-for-plugin-conflicts/)
 * If you feel uncomfortable doing this yourself or if this does not solve your 
   issue, our [Yoast SEO Premium plugin](https://yoast.com/wordpress/plugins/seo/)
   comes with one year of (technical) support.
 *  [Jeroen Rotty](https://wordpress.org/support/users/jeroenrotty/)
 * (@jeroenrotty)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/getting-fatal-error-34/#post-16410421)
 * This thread was marked resolved due to a lack of activity, but you’re always 
   welcome to re-open the topic. Please read [this post](https://wordpress.org/support/topic/read-this-before-your-post/)
   before [opening a new request](https://wordpress.org/support/plugin/wordpress-seo#new-post).

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

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

 * ![](https://ps.w.org/wordpress-seo/assets/icon-256x256.gif?rev=3419908)
 * [Yoast SEO - Advanced SEO with real-time guidance and built-in AI](https://wordpress.org/plugins/wordpress-seo/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordpress-seo/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordpress-seo/)
 * [Active Topics](https://wordpress.org/support/plugin/wordpress-seo/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordpress-seo/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordpress-seo/reviews/)

 * 2 replies
 * 3 participants
 * Last reply from: [Jeroen Rotty](https://wordpress.org/support/users/jeroenrotty/)
 * Last activity: [3 years, 3 months ago](https://wordpress.org/support/topic/getting-fatal-error-34/#post-16410421)
 * Status: resolved