Forum Replies Created

Viewing 15 replies - 1 through 15 (of 224 total)
  • Thread Starter Zade

    (@nothin7)

    P.S. In case this is useful to anyone else, here’s a temporary workaround. This plugin uses the list name as the checkbox label, but I don’t have multiple lists, so I wanted a simple checkbox label: “Subscribe to our newsletter”.

    // Move Constant Contact opt in before Post Comment (submit) button with clean HTML
    function pd_cc_optin() {
    if ( ! function_exists( 'constant_contact' ) ) return;
    $settings = constant_contact()->get_settings();
    // Remove from 'comment_form' (fires after submit button)
    remove_action( 'comment_form', [ $settings, 'optin_form_field_comment' ] );
    // Prepend clean opt-in HTML before the submit button (works for both logged-in and logged-out)
    add_filter( 'comment_form_submit_field', function( $submit_field ) use ( $settings ) {
    // Respect the plugin's own "show on comment form" setting and API connection check
    if ( ! $settings->check_if_optin_should_show( 'comment_form' ) ) {
    return $submit_field;
    }
    if ( ! constant_contact()->get_api()->is_connected() ) {
    return $submit_field;
    }
    // Get configured lists
    $list_ids = constant_contact_get_option( '_ctct_optin_list', [] );
    if ( empty( $list_ids ) ) {
    return $submit_field;
    }
    // Get the label (falls back to default)
    $label = constant_contact_get_option( '_ctct_optin_label', '' );
    if ( empty( $label ) ) {
    $label = __( 'Subscribe to our newsletter', 'constant-contact-forms' );
    }
    // Build clean HTML with first configured list
    $list_id = reset( $list_ids );
    $html = sprintf(
    '<p class="ctct-optin-wrapper">
    <label for="ctct_optin_%1$s">
    <input type="checkbox" value="%1$s" class="checkbox" id="ctct_optin_%1$s" name="ctct_optin_list[]">
    %2$s
    </label>
    </p>',
    esc_attr( $list_id ),
    esc_html( $label )
    );
    return $html . $submit_field;
    });
    }
    add_action( 'init', 'pd_cc_optin', 20 );
    Thread Starter Zade

    (@nothin7)

    Nice sleuthing! Well this is interesting; I just confirmed my FP license is Active (https://a.cl.ly/5zuELrmR) but something about NF being active is causing FP’s Cloud Optimizer to return an “Invalid license key” response:

    Array
    (
    [headers] => WpOrg\Requests\Utility\CaseInsensitiveDictionary Object
    (
    [data:protected] => Array
    (
    [date] => Tue, 14 Apr 2026 20:28:55 GMT
    [content-type] => text/html; charset=utf-8
    [content-length] => 19
    [cf-ray] => 9ec575a79c416d20-LAX
    [cf-cache-status] => DYNAMIC
    [cache-control] => public, max-age=2592000
    [etag] => W/"13-3ktx/mMbgtvokNAWQkFsrYhtsGs"
    [server] => cloudflare
    [vary] => Accept-Encoding
    [x-powered-by] => Express
    [report-to] => {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=dwI3nS4UErjmFpMB6DniOHeFmpjCgCVzv2ejve5cHKrB%2FU0syHEeUZMZQyus6%2FG35nNQ3TLy8H9b%2BCBEEggToa73nV0jKg2kHau3WrmlZOU2PXCjKavr8zXMHEwNpKx5q%2FXX6h910OkYoAb%2Blcv%2F9Q%3D%3D"}]}
    [nel] => {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
    )

    )

    [body] => Invalid license key
    [response] => Array
    (
    [code] => 403
    [message] => Forbidden
    )

    [cookies] => Array
    (
    )

    [filename] =>
    [http_response] => WP_HTTP_Requests_Response Object
    (
    [data] =>
    [headers] =>
    [status] =>
    [response:protected] => WpOrg\Requests\Response Object
    (
    [body] => Invalid license key
    [raw] => HTTP/1.1 403 Forbidden
    Date: Tue, 14 Apr 2026 20:28:55 GMT
    Content-Type: text/html; charset=utf-8
    Content-Length: 19
    Connection: close
    CF-Ray: 9ec575a79c416d20-LAX
    CF-Cache-Status: DYNAMIC
    Cache-Control: public, max-age=2592000
    ETag: W/"13-3ktx/mMbgtvokNAWQkFsrYhtsGs"
    Server: cloudflare
    Vary: Accept-Encoding
    X-Powered-By: Express
    Report-To: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=dwI3nS4UErjmFpMB6DniOHeFmpjCgCVzv2ejve5cHKrB%2FU0syHEeUZMZQyus6%2FG35nNQ3TLy8H9b%2BCBEEggToa73nV0jKg2kHau3WrmlZOU2PXCjKavr8zXMHEwNpKx5q%2FXX6h910OkYoAb%2Blcv%2F9Q%3D%3D"}]}
    Nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}

    Invalid license key
    [headers] => WpOrg\Requests\Response\Headers Object
    (
    [data:protected] => Array
    (
    [date] => Array
    (
    [0] => Tue, 14 Apr 2026 20:28:55 GMT
    )

    [content-type] => Array
    (
    [0] => text/html; charset=utf-8
    )

    [content-length] => Array
    (
    [0] => 19
    )

    [cf-ray] => Array
    (
    [0] => 9ec575a79c416d20-LAX
    )

    [cf-cache-status] => Array
    (
    [0] => DYNAMIC
    )

    [cache-control] => Array
    (
    [0] => public, max-age=2592000
    )

    [etag] => Array
    (
    [0] => W/"13-3ktx/mMbgtvokNAWQkFsrYhtsGs"
    )

    [server] => Array
    (
    [0] => cloudflare
    )

    [vary] => Array
    (
    [0] => Accept-Encoding
    )

    [x-powered-by] => Array
    (
    [0] => Express
    )

    [report-to] => Array
    (
    [0] => {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=dwI3nS4UErjmFpMB6DniOHeFmpjCgCVzv2ejve5cHKrB%2FU0syHEeUZMZQyus6%2FG35nNQ3TLy8H9b%2BCBEEggToa73nV0jKg2kHau3WrmlZOU2PXCjKavr8zXMHEwNpKx5q%2FXX6h910OkYoAb%2Blcv%2F9Q%3D%3D"}]}
    )

    [nel] => Array
    (
    [0] => {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
    )

    )

    )

    [status_code] => 403
    [protocol_version] => 1.1
    [success] =>
    [redirects] => 0
    [url] => https://page-optimizer.flyingpress.com/optimizer/
    [history] => Array
    (
    )

    [cookies] => WpOrg\Requests\Cookie\Jar Object
    (
    [cookies:protected] => Array
    (
    )

    )

    )

    [filename:protected] =>
    )

    )
    Thread Starter Zade

    (@nothin7)

    P.S. To help with diagnosis, I’ve uploaded both plugin folders to https://github.com/zaderade/FPNFpluginsTemp/

    Thread Starter Zade

    (@nothin7)

    Thanks so much for looking into it.

    I have changed this ticket back to “not resolved” to accurately reflect the status of this bug. If you believe marking this ticket “resolved” before it’s resolved is the more honest and helpful behavior, kindly explain your reasoning.

    Thread Starter Zade

    (@nothin7)

    Well done, I am now able to see UTM parameters in DebugView with FlyingPress!

    By the way, I further narrowed the conflict to FlyingPress’ Cloudflare Page Caching feature. With that feature disabled, I’m able to see UTM parameters with or without your filter. But I definitely want to use Page Caching to reduce server load and TTFB.

    Thanks! No need to reply.

    Thread Starter Zade

    (@nothin7)

    Thanks @aurangajeb ! I no longer see ALTER queries in wp-admin.

    Yes, @tooni , this appears to be resolved in version 4.9.0.

    Agreed, great plugin, and I have the same issue. Running MariaDB 10.6.19 with WordPress/WooCommerce up to date.

    Sometimes it’s both those tables; other times it’s just wp_woocommerce_order_itemmeta. It’s interesting to see these tables both in the “Convert keys” section as well as the “Revert keys” section simultaneously. I’m assuming if a converted table appears next to “Convert keys” it’s worth converting again?

    Can I help debug this?

    Thread Starter Zade

    (@nothin7)

    Yes, the site uses MariaDB.

    Zade

    (@nothin7)

    Dear Facebook for WooCommerce plugin authors,

    I have the same problem. Will this be addressed in your next plugin update?

    Thanks,

    Zade

    Thread Starter Zade

    (@nothin7)

    Hi @devmich,

    Thanks for confirming that you’re seeing utm_source in DebugView. I dug deeper and discovered this is a conflict between your plugin and FlyingPress, even when I’ve disabled all relevant FlyingPress optimizations (screenshot) and purged the entire cache. Somehow Site Kit by Google is able to work with FlyingPress but MonsterInsights does not. Let me know if you’re able to figure out what’s different.

    Before you respond with a link to FlyingPress’ documentation on Ignored Query Parameters, remember that these ignored GA4 parameters do work with Google’s Site Kit plugin. I’m also aware that adding utm_source to FlyingPress’ Separate Cache for Query Parameters setting might fix the problem, but this isn’t ideal for performance reasons. As mentioned in FlyingPress’ documentation on Customize Ignored Query Parameters, “Ignoring them prevents duplicate cache entries and improves cache efficiency.”

    Cheers,

    Robert

    Zade

    (@nothin7)

    Hi @im_niloy,

    I have the same warnings, which have been clogging my error log for quite a while:

    [29-Oct-2025 00:15:42 UTC] PHP Warning:  Trying to access array offset on value of type bool in /wp-content/plugins/woo-product-gallery-slider/includes/product-image.php on line 103
    [29-Oct-2025 00:15:42 UTC] PHP Warning: Trying to access array offset on value of type bool in /wp-content/plugins/woo-product-gallery-slider/includes/product-image.php on line 104
    [29-Oct-2025 00:15:42 UTC] PHP Warning: Trying to access array offset on value of type bool in /wp-content/plugins/woo-product-gallery-slider/includes/product-image.php on line 103
    [29-Oct-2025 00:15:42 UTC] PHP Warning: Trying to access array offset on value of type bool in /wp-content/plugins/woo-product-gallery-slider/includes/product-image.php on line 104
    [29-Oct-2025 00:15:43 UTC] PHP Warning: Trying to access array offset on value of type bool in /wp-content/plugins/woo-product-gallery-slider/includes/product-image.php on line 103
    [29-Oct-2025 00:15:43 UTC] PHP Warning: Trying to access array offset on value of type bool in /wp-content/plugins/woo-product-gallery-slider/includes/product-image.php on line 104
    [29-Oct-2025 00:15:43 UTC] PHP Warning: Trying to access array offset on value of type bool in /wp-content/plugins/woo-product-gallery-slider/includes/product-image.php on line 103
    [29-Oct-2025 00:15:43 UTC] PHP Warning: Trying to access array offset on value of type bool in /wp-content/plugins/woo-product-gallery-slider/includes/product-image.php on line 104
    [29-Oct-2025 00:15:45 UTC] PHP Warning: opendir(/wp-content/cache/db/remaining//948): Failed to open directory: No such file or directory in /wp-content/plugins/w3-total-cache/Util_File.php on line 158
    [29-Oct-2025 00:15:45 UTC] PHP Warning: opendir(/wp-content/cache/db/singletables//690/fe6): Failed to open directory: No such file or directory in /wp-content/plugins/w3-total-cache/Util_File.php on line 158
    [29-Oct-2025 00:15:45 UTC] PHP Warning: opendir(/wp-content/cache/db/singletables//048/300): Failed to open directory: No such file or directory in /wp-content/plugins/w3-total-cache/Util_File.php on line 158
    [29-Oct-2025 00:15:51 UTC] PHP Warning: Trying to access array offset on value of type bool in /wp-content/plugins/woo-product-gallery-slider/includes/product-image.php on line 103
    [29-Oct-2025 00:15:51 UTC] PHP Warning: Trying to access array offset on value of type bool in /wp-content/plugins/woo-product-gallery-slider/includes/product-image.php on line 104
    [29-Oct-2025 00:15:51 UTC] PHP Warning: Trying to access array offset on value of type bool in /wp-content/plugins/woo-product-gallery-slider/includes/product-image.php on line 103
    [29-Oct-2025 00:15:51 UTC] PHP Warning: Trying to access array offset on value of type bool in /wp-content/plugins/woo-product-gallery-slider/includes/product-image.php on line 104
    [29-Oct-2025 00:18:44 UTC] PHP Warning: Trying to access array offset on value of type bool in /wp-content/plugins/woo-product-gallery-slider/includes/product-image.php on line 103
    [29-Oct-2025 00:18:44 UTC] PHP Warning: Trying to access array offset on value of type bool in /wp-content/plugins/woo-product-gallery-slider/includes/product-image.php on line 104
    [29-Oct-2025 00:19:48 UTC] PHP Warning: Trying to access array offset on value of type bool in /wp-content/plugins/woo-product-gallery-slider/includes/product-image.php on line 103
    [29-Oct-2025 00:19:48 UTC] PHP Warning: Trying to access array offset on value of type bool in /wp-content/plugins/woo-product-gallery-slider/includes/product-image.php on line 104
    [29-Oct-2025 00:19:48 UTC] PHP Warning: Trying to access array offset on value of type bool in /wp-content/plugins/woo-product-gallery-slider/includes/product-image.php on line 103
    [29-Oct-2025 00:19:48 UTC] PHP Warning: Trying to access array offset on value of type bool in /wp-content/plugins/woo-product-gallery-slider/includes/product-image.php on line 104
    [29-Oct-2025 00:19:48 UTC] PHP Warning: Trying to access array offset on value of type bool in /wp-content/plugins/woo-product-gallery-slider/includes/product-image.php on line 103
    [29-Oct-2025 00:19:48 UTC] PHP Warning: Trying to access array offset on value of type bool in /wp-content/plugins/woo-product-gallery-slider/includes/product-image.php on line 104

    They’re hard to replicate, but easy to fix. Just add the null coalescing operator with an empty string (?? ”) to the end of lines 103 and 104, as follows:

    'data-zoom_src'    => wp_get_attachment_image_src( $attachment_id, apply_filters( 'gallery_slider_zoom_image_size', 'full' ) )[0] ?? '',
    'data-large_image' => wp_get_attachment_image_src( $attachment_id, apply_filters( 'gallery_slider_zoom_image_size', 'full' ) )[0] ?? '',

    Would you be willing to include this fix in the next update of your plugin?

    Once this is resolved, I might have time to discuss potential causes. I suspect it might be a conflict with the W3 Total Cache plugin. I can see the problem visually at https://wellaligned.com/product/poop-for-chiro-onesie/ (screenshot: https://a.cl.ly/5zulZv44). This visual anomaly was fixed by simply clicking Edit Product and then clicking Update without making any changes (I haven’t yet cleared the cache for this page). But I only mention this for later reference. First step is to fix the problem 🙂

    Thanks!

    Thread Starter Zade

    (@nothin7)

    Much appreciated.

    Triggering those other warnings would probably involve reverting to the oldest version of W3TC that integrated Cloudflare, then authorizing. In other words, it’s something that’s fixed for new installations and is a remnant that only affects early adopters. I can understand if that’s not worth fixing.

    No need to reply, but feel free to let me know when the next update has been released, and I’ll mark this ticket as resolved.

    Thread Starter Zade

    (@nothin7)

    I’d prefer to keep this public so it benefits others as well.

    In your screenshot, I don’t see “Source” in the “Name” column (if it were there, it should have a Value of “mi_test”). The only place I see it is in the Page Location—that’s not a UTM parameter.

    Also, for this to be a realistic test, please remove parameters like “gtm_debug” that would not be included when a customer clicks an ad. I provided step-by-step instructions; instead of moving us in new directions perhaps you could repeat the test I did using GA4’s DebugView tool?

    Thread Starter Zade

    (@nothin7)

    Sorry; I was working on something else. The site is loading again now.

    Thread Starter Zade

    (@nothin7)

    Yes, this fixes the line 484 warning. Thanks! Will this change be incorporated into the next update of your plugin?

    The 13 warnings that appear only when viewing the Performance Dashboard can be resolved by reauthorizing Cloudflare. This will be annoying to do for 100+ sites but at least it’s possible. Any chance of somehow automating this or updating the code so reauthorizing isn’t needed?

Viewing 15 replies - 1 through 15 (of 224 total)