Merge pull request #1067 from cloudinary/uat

3.2.11

Author: bruckercloud

.version

@@ -1 +1 @@
-3.2.10
+3.2.11

languages/cloudinary.pot

@@ -4,7 +4,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Cloudinary STABLETAG\n"
 "Report-Msgid-Bugs-To: https://github.com/cloudinary/cloudinary_wordpress\n"
-"POT-Creation-Date: 2025-05-29 05:42:10+00:00\n"
+"POT-Creation-Date: 2025-06-27 06:59:54+00:00\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -2158,14 +2158,21 @@ msgid ""
 "REST API connection. Ensure your WordPress setup, including multisite or "
 "headless configurations, has the REST API enabled and active for seamless "
 "plugin operation.%1$sFor more information, see %2$sWordPress’s REST API "
-"Handbook%3$s."
+"Handbook%3$s.%1$sTo manually verify your REST API connection, you can "
+"temporarily enable the %5$sCloudinary Cron%6$s feature from %4$sthe "
+"plugin’s Cron admin page%3$s. Once enabled, activate the %8$s task. When "
+"the cron runs for the first time, any connectivity issues will trigger an "
+"admin notice.%1$s%7$s%5$s Important%6$s: Enabling the Cron feature starts a "
+"recurring background process. Unless you’re actively using it for "
+"diagnostics or testing, we %5$sstrongly recommend disabling%6$s this "
+"feature to avoid generating unnecessary requests or load on your site."
 msgstr ""
 
-#: ui-definitions/settings-pages.php:457
+#: ui-definitions/settings-pages.php:462
 msgid "Does Cloudinary work on multilingual sites?"
 msgstr ""
 
-#: ui-definitions/settings-pages.php:461
+#: ui-definitions/settings-pages.php:466
 #. translators: The HTML markup.
 msgid ""
 "Absolutely! Cloudinary is fully compatible with WPML, the leading WordPress "
@@ -2175,37 +2182,37 @@ msgid ""
 "visit %1$sWPML's official page%2$s on Cloudinary compatibility."
 msgstr ""
 
-#: ui-definitions/settings-pages.php:468
+#: ui-definitions/settings-pages.php:473
 msgid ""
 "I'm having an incompatibility issue with a theme, plugin, or hosting "
 "environment, what can I do?"
 msgstr ""
 
-#: ui-definitions/settings-pages.php:473
+#: ui-definitions/settings-pages.php:478
 #. translators: The HTML markup.
 msgid ""
 "We’re compatible with most other plugins so we expect it to work absolutely "
 "fine. If you do have any issues, please %1$scontact our support team%2$s "
 "who will help resolve your issue."
 msgstr ""
 
-#: ui-definitions/settings-pages.php:481
+#: ui-definitions/settings-pages.php:486
 msgid "Can I use the Cloudinary plugin for my eCommerce websites?"
 msgstr ""
 
-#: ui-definitions/settings-pages.php:485
+#: ui-definitions/settings-pages.php:490
 #. translators: The HTML markup.
 msgid ""
 "Yes, the Cloudinary plugin has full support for WooCommerce. We also have "
 "additional functionality that allows you to add a fully optimized "
 "%1$sProduct Gallery%2$s."
 msgstr ""
 
-#: ui-definitions/settings-pages.php:492
+#: ui-definitions/settings-pages.php:497
 msgid "Why are my images loading locally and not from Cloudinary?"
 msgstr ""
 
-#: ui-definitions/settings-pages.php:496
+#: ui-definitions/settings-pages.php:501
 #. translators: The HTML markup.
 msgid ""
 "Your images may be loading locally for a number of reasons:%1$sThe asset "
@@ -2216,21 +2223,21 @@ msgid ""
 "assets in the %5$sWordPress Media Library%4$s.%6$s"
 msgstr ""
 
-#: ui-definitions/settings-pages.php:507
+#: ui-definitions/settings-pages.php:512
 msgid "How do I handle a CLDBind error which is causing issues with lazy loading?"
 msgstr ""
 
-#: ui-definitions/settings-pages.php:509
+#: ui-definitions/settings-pages.php:514
 msgid ""
 "The Cloudinary lazy loading scripts must be loaded in the page head. Ensure "
 "your site or any 3rd party plugins are not setup to move these scripts."
 msgstr ""
 
-#: ui-definitions/settings-pages.php:523
+#: ui-definitions/settings-pages.php:528
 msgid "Debug log"
 msgstr ""
 
-#: ui-definitions/settings-pages.php:530
+#: ui-definitions/settings-pages.php:535
 msgid "Edit asset"
 msgstr ""
 

package.json

@@ -143,5 +143,5 @@
     "webpack-cli": "^4.2.0",
     "webpackbar": "^5.0.2"
   },
-  "version": "3.2.10"
+  "version": "3.2.11"
 }

php/class-cron.php

@@ -99,7 +99,7 @@ public function __construct() {
 	 */
 	public function add_settings( $settings ) {
 
-		$enabled                     = apply_filters( 'cloudinary_feature_cron_manager', false );
+		$enabled                     = apply_filters( 'cloudinary_feature_cron_manager', true );
 		$settings[ self::CRON_SLUG ] = array(
 			'page_title'          => __( 'Cron System', 'cloudinary' ),
 			'requires_connection' => true,
@@ -115,16 +115,16 @@ public function add_settings( $settings ) {
 					array(
 						'type'    => 'on_off',
 						'title'   => __( 'Enable Cron', 'cloudinary' ),
-						'default' => 'on',
+						'default' => 'off',
 						'slug'    => 'enable_cron',
 					),
 					array(
 						'type'    => 'cron',
 						'slug'    => 'tasks',
 						'default' => array(
-							'update_asset_paths' => 'on',
-							'rest_api'           => 'on',
-							'check_status'       => 'on',
+							'update_asset_paths' => 'off',
+							'rest_api'           => 'off',
+							'check_status'       => 'off',
 						),
 						'cron'    => $this,
 					),

readme.txt

@@ -146,6 +146,13 @@ Your site is now setup to start using Cloudinary.
 
 == Changelog ==
 
+= 3.2.11 (30 June 2025) =
+
+Fixes and Improvements:
+
+* Cron jobs now disabled by default to reduce unnecessary requests
+* Updated REST API in FAQ to support enabling/disabling the cron jobs
+
 = 3.2.10 (24 June 2025) =
 
 Fixes and Improvements:

ui-definitions/settings-pages.php

@@ -446,10 +446,15 @@
 					'collapsible' => 'closed',
 					'content'     => sprintf(
 						// translators: The HTML markup.
-						__( 'To function correctly, the Cloudinary plugin requires an active WordPress REST API connection. Ensure your WordPress setup, including multisite or headless configurations, has the REST API enabled and active for seamless plugin operation.%1$sFor more information, see %2$sWordPress’s REST API Handbook%3$s.', 'cloudinary' ),
+						__( 'To function correctly, the Cloudinary plugin requires an active WordPress REST API connection. Ensure your WordPress setup, including multisite or headless configurations, has the REST API enabled and active for seamless plugin operation.%1$sFor more information, see %2$sWordPress’s REST API Handbook%3$s.%1$sTo manually verify your REST API connection, you can temporarily enable the %5$sCloudinary Cron%6$s feature from %4$sthe plugin’s Cron admin page%3$s. Once enabled, activate the %8$s task. When the cron runs for the first time, any connectivity issues will trigger an admin notice.%1$s%7$s%5$s Important%6$s: Enabling the Cron feature starts a recurring background process. Unless you’re actively using it for diagnostics or testing, we %5$sstrongly recommend disabling%6$s this feature to avoid generating unnecessary requests or load on your site.', 'cloudinary' ),
 						'<br><br>',
 						'<a href="https://developer.wordpress.org/rest-api/" target="_blank" rel="noopener noreferrer">',
-						'</a>'
+						'</a>',
+						'<a href="' . add_query_arg( array( 'page' => 'cloudinary&section=cron_system' ), admin_url( 'admin.php' ) ) . '">',
+						'<strong>',
+						'</strong>',
+						'<span style="color: #b0b000; font-size: 18px">&#9888;</span>',
+						'<span style="background: #e8e9e8; padding-inline: 2px;">rest_api</span>'
 					),
 				),
 				array(