From d2366d8967be7973a51939052a5fe97fd5fd9a80 Mon Sep 17 00:00:00 2001 From: Tim Carr Date: Fri, 24 Jul 2026 16:37:44 +0800 Subject: [PATCH] Settings: Post: Defaults: Use `0` instead of blank string MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This mirrors how settings are saved when adding/editing a Page, Post or CPT in WordPress and setting Landing Page, Add a Tag and/or Member Content functionality to ‘None’ / ‘Don’t restrict’, which would store these settings as 0, not a blank string. --- includes/class-convertkit-post.php | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/includes/class-convertkit-post.php b/includes/class-convertkit-post.php index 58d1a4ab8..b13cf01b2 100644 --- a/includes/class-convertkit-post.php +++ b/includes/class-convertkit-post.php @@ -314,9 +314,9 @@ public function get_default_settings() { $defaults = array( 'form' => '-1', // -1: Plugin Default Form, 0: No Form, 1+: Specific Form ID on ConvertKit. - 'landing_page' => '', - 'tag' => '', - 'restrict_content' => '', + 'landing_page' => '0', // 0: None, 1+: Specific Landing Page ID. + 'tag' => '0', // 0: None, 1+: Specific Tag ID. + 'restrict_content' => '0', // 0: None, form_ / tag_ / product_: restrict to that resource. ); /**