Title: Critical error
Last modified: December 24, 2023

---

# Critical error

 *  Resolved [boabo](https://wordpress.org/support/users/boabo/)
 * (@boabo)
 * [2 years, 5 months ago](https://wordpress.org/support/topic/critical-error-634/)
 * After deactivating several plugins due to a critical error and because i couldn’t
   update any text with elementor anymore (server error), i finally found that by
   deactivating only litespeed 6.0.0.1 solved all issues. I’m using WP 6.4.2.

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

 *  Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/)
 * (@qtwrk)
 * [2 years, 5 months ago](https://wordpress.org/support/topic/critical-error-634/#post-17299896)
 * when it shows critical error, please check the PHP error log , it will give more
   information about what exactly was that critical error , please share the relevant
   log
 *  Thread Starter [boabo](https://wordpress.org/support/users/boabo/)
 * (@boabo)
 * [2 years, 5 months ago](https://wordpress.org/support/topic/critical-error-634/#post-17300274)
 * Can i send login credentials privately? In fact it’s very strange: as soon as
   i deactivate only 1 plugin, critical error vanished but i cannot edit/update 
   pages with elementor.
 * This said, I close this for now and will wait for 1 plugin to update from wp 
   6.3 to 6.4
 *  Moderator [Jan Dembowski](https://wordpress.org/support/users/jdembowski/)
 * (@jdembowski)
 * Forum Moderator and Brute Squad
 * [2 years, 5 months ago](https://wordpress.org/support/topic/critical-error-634/#post-17300436)
 * > Can i send login credentials privately?
 * If you do then qtwrk could be banned and the plugin here closed.
 * Had [@qtwrk](https://wordpress.org/support/users/qtwrk/) asked for that (_and
   they did not ask for that and are **NOT** in trouble in anyway at all_) then 
   this would be my reply.
 * While I know you have the best of intentions, it’s forum policy that you _not_
   ask users for admin or server access. Users on the forums aren’t your customers,
   they’re your open source collaborators, and requesting that kind of access can
   put you and them at high risk.
 * If they _are_ paying customers (such as people who bought a premium service/product
   from you) then by all means, direct them to your official customer support system.
   But in all other cases, you need to help them here on the forums.
 * Thankfully are other ways to get information you need:
    - Ask the user to install the [Health Check plugin](https://wordpress.org/support/plugin/health-check/)
      and get the data that way.
    - Ask for a link to the [http://pastebin.com/](http://pastebin.com/) or [https://gist.github.com](https://gist.github.com)
      log of the user’s web server error log.
    - Ask the user to create and post a link to their `phpinfo();` output.
    - Walk the user through [enabling WP_DEBUG and how to log that output to a file and how to share that file.](https://wordpress.org/support/article/debugging-in-wordpress/)
    - Walk the user through basic troubleshooting steps such and disabling all other
      plugins, clear their cache and cookies and try again (the Health Check plugin
      can do this without impacting any site vistors).
    - Ask the user for the step-by-step directions on how they can reproduce the
      problem.
 * You get the idea.
 * We know volunteer support is not easy, and this guideline can feel needlessly
   restrictive. It’s actually there to protect you as much as end users. Should 
   their site be hacked or have any issues after you accessed it, you could be held
   legally liable for damages. In addition, it’s difficult for end users to know
   the difference between helpful developers and people with malicious intentions.
   Because of that, we rely on plugin developers and long-standing volunteers (like
   you) to help us and uphold this particular guideline.
 * When you help users _here_ and in public, you also help the next person with 
   the same problem. They’ll be able to read the debugging and solution and educate
   themselves. That’s how we get the next generation of developers.
 * **NOTE:** The plugin support person never asked for that and again, is NOT is
   trouble in any way at all. I’m just explaining.
 *  Thread Starter [boabo](https://wordpress.org/support/users/boabo/)
 * (@boabo)
 * [2 years, 5 months ago](https://wordpress.org/support/topic/critical-error-634/#post-17300470)
 * Calm down [@jdembowski](https://wordpress.org/support/users/jdembowski/) … it
   was my own initiative but thanks for the reminder to keep the forum safe.

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

The topic ‘Critical error’ is closed to new replies.

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

 * 4 replies
 * 3 participants
 * Last reply from: [boabo](https://wordpress.org/support/users/boabo/)
 * Last activity: [2 years, 5 months ago](https://wordpress.org/support/topic/critical-error-634/#post-17300470)
 * Status: resolved