Reasons<\/h2>\n
If you notice that some plugins are not being updated by the automated plugin update feature by Staq, below are some reasons why.<\/p>\n
Plugins that live outside of the WordPress plugin\/theme repository<\/h3>\n
If a plugin\/theme does not live in the WordPress repository, that means Staq cannot access the download URL in order to update the plugin\/theme. If that is the case, you’ll see in the Staq updates interface the following message in the orange label:<\/p>\n
Update URL is not available<\/em><\/p>\n Premium plugins often require a valid license key for updates. If a plugin’s license status is not updated on the website due to the absence of a valid license, the plugin may not send an update status check request. This prevents the plugin from being updated automatically. Although the plugin may appear to have an available update in the Staq dashboard, it may not be reflected on the website if the license status check fails.<\/p>\n If a premium license has expired but the plugin still generates a download source URL with the license token in it, it will not update it since the premium license is validated against their system.<\/p>\n This may occur where a Global Plugin inside Staq shows that an update is available but the plugin inside WordPress shows that it isn’t available to be updated.<\/p>\n The reason being is that that particular plugin is not registered if it is a premium plugin.<\/p>\n The reason why it shows inside the Staq interface is due to the fact that if a plugin is set to a Global Plugin, we scan other sites in your account that has that plugin and since a particular site may have that premium plugin registered, we then get the update data to know if a newer plugin is available.<\/p>\n Some plugins do not adhere to the standard update notification methods utilized by WordPress. As a result, these plugins may not be detected or updated automatically by the Staq system. These plugins may still appear in the WordPress Updates section within the WP Admin dashboard but may not be recognized by the Staq Environment Global Manager (EGM) for automatic updates.<\/p>\n Certain plugins manage updates through custom methods, such as custom database tables or non-standard update APIs. In such cases, the Staq system may not be able to detect or process updates for these plugins automatically. The absence of standard update notifications or reliance on custom update management methods can hinder the automatic update process on Staq.<\/p>\n While Staq strives to automate plugin updates to streamline website management, certain factors such as license restrictions, non-standard update notifications, and custom update management methods can affect the automatic update process. Users should be aware of these limitations and be prepared to manually update plugins or address issues related to plugin updates as needed.<\/p>\n","protected":false},"featured_media":0,"parent":0,"template":"","class_list":["post-35996","knowledgebase","type-knowledgebase","status-publish","hentry","categories-plugins-themes-diagnose"],"acf":[],"yoast_head":"\n![\"\"](\"https:\/\/www.wpstaq.com\/wp-content\/uploads\/2024\/04\/update-url-not-available.png\")
<\/p>\nMissing Premium License<\/h3>\n
Expired Premium License<\/h3>\n
Update shows in Staq Platform but not inside WordPress<\/h3>\n
Non-Standard Update Notifications<\/h3>\n
Custom Update Management<\/h3>\n
Conclusion<\/h2>\n