Forum Replies Created

Viewing 8 replies - 1 through 8 (of 8 total)
  • English -South Africa- isn’t being “loaded” from files anymore, it’s stored in the database and WordPress language registry, not just in /wp-content/languages.

    You need to check in database., If you see: en_ZA – Change it to: en_US.

    wp-config.php > define(‘WPLANG’, ‘en_ZA’); -to- define(‘WPLANG’, ‘en_US’); 🙌

    It takes the server about 13–14 seconds to start responding.

    The problem is the server.

    1. Log in to cPanel
    2. Open File Manager
    3. Go to public_html
    4. Go to wp-content
    5. Go to plugins
    6. Inside the plugins folder, rename each plugin folder. Take the plugin name and add “On” at the end.

    Example:

    plugin-name → plugin-name On

    If the issue is caused by a plugin, this method allows you to disable the problematic plugin individually.

    Plugins like “wp-perf-analytics” and “session-manager” are commonly used as backdoors disguised as performance or session tools. They are not part of the official WordPress repository and are often injected after a site is already compromised.

    In most cases, these plugins are:

    • Dropped after an initial breach (not the root cause)

    Used to:

    *Maintain persistent access (backdoor)
    *Inject spam or malicious scripts
    *Create hidden admin users
    *Reinfect the site if cleaned incorrectly

    franrival

    (@franrival)

    A 403 Forbidden means something is actively blocking access, not that the URL is wrong. Plugins like Wordfence or Sucuri can block Requests with unusual headers

    franrival

    (@franrival)

    It sounds like there are two sets of code running at the same time…

    1. The Solene theme

    * Has its own JS for the mobile menu

    * Listens for events (touchstart, click)

    * May use preventDefault() or block events

    2. Elementor (Header Builder)

    * Also waits for those same events

    * Needs the event to reach the button unimpeded

    The theme’s JS “wins” and blocks Elementor’s. Or the other way around (I don’t think so…) 

    Hello,

    This issue with MAMP is common in recent versions of PHP.

    Even though your computer can access WordPress.org via curl, WordPress uses its own HTTP layer (WP_Http),

    and this is where it may fail when trying to connect to SSL, OpenSSL, or PHP.

    Try forcing IPv4 on a WordPress request by placing this code snippet in your functions.php file

    add_action(‘http_api_curl’, function($handle) {
    curl_setopt($handle, CURLOPT_IPRESOLVE, CURL_IPRESOLVE_V4);
    });

    Why?

    This will force WordPress to respond. Don’t paste it into the .config file

    Hi, adenby,

    What you’re describing (a temporary fix after restarting PHP + the slowness returning) clearly points to resource exhaustion or a problem with the processes, not just a conflict between plugins.

    Based on your setup, here’s how I would approach it step by step:

    1. Most likely cause: PHP-FPM / resource saturation

    If restarting PHP temporarily fixes it, that usually means:
    • PHP workers are getting stuck or are overloaded
    • There may be:
    • Long-running queries
    • Delays in external APIs
    • Memory leaks
    • Too many concurrent requests

    Or it could be an issue with a plugin you’ve recently installed. You’ll need to go through them one by one and deactivate them to see if that works.

    Note: For every plugin you deactivate, you’ll need to clear the cache. You can easily do this using LiteSpeedCache.

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