Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Hi,

    A few things commonly cause plugin updates to stop showing. Try these in order:

    1. Force a fresh update check
    Go to Dashboard → Updates and click Check again. If nothing changes, clear the cached update data. With WP-CLI:

    wp eval 'delete_site_transient( "update_plugins" ); wp_update_plugins();'

    Or install a transient-clearing plugin such as WP Crontrol or Transients Manager and delete update_plugins.

    2. Check that your server can reach WordPress.org
    Go to Tools → Site Health → Status and look for errors about REST API, loopback requests, or “communication with WordPress.org”. A firewall, security plugin, or host restriction can block outgoing requests to api.wordpress.org, so the update list never refreshes.

    3. Check wp-config.php
    Look for these lines:

    define( 'DISALLOW_FILE_MODS', true );
    define( 'WP_HTTP_BLOCK_EXTERNAL', true );

    Either one can stop updates from appearing or installing. If WP_HTTP_BLOCK_EXTERNAL is on, WP_ACCESSIBLE_HOSTS must include api.wordpress.org and *.wordpress.org.

    4. Check your PHP version
    WordPress won’t offer a plugin update if your PHP or WordPress version is below what that release requires. Elementor’s newer versions require newer PHP than older ones did. Check the “Requires PHP” line on the plugin’s page in the directory, and compare it with the version shown in Site Health → Info → Server.

    5. Rule out conflicts and caching

    • Temporarily deactivate security, caching, and “update manager” plugins and check again.
    • If you use an object cache (Redis or Memcached), flush it.
    • Make sure the server date and time are correct. A wrong clock can break HTTPS requests.

    6. Manual update as a last resort
    Download the plugin zip from its page in the directory, deactivate it, and replace the folder over FTP or the file manager. Or run wp plugin update elementor.

    If it still doesn’t work, please share:

    • Your WordPress and PHP versions
    • Your hosting type
    • Any errors from Site Health
    • Whether DISALLOW_FILE_MODS or WP_HTTP_BLOCK_EXTERNAL is set

    A separate library plugin. Put your autoloader in its own plugin. Since WordPress 6.5 your other plugins can declare it as a dependency in their header:

    Requires Plugins: example-library

    WordPress then requires the library plugin to be active before the dependents. Details are in the Plugin Handbook under “Header Requirements”. Note that the slug is matched against the WordPress.org directory, so for a private or GitHub-hosted plugin you’d need the wp_plugin_dependencies_slug filter, or check class_exists() yourself on plugins_loaded.

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