Forum Replies Created

Viewing 15 replies - 1 through 15 (of 18 total)
  • Thread Starter frensis

    (@frensis)

    Ok… I got it!
    In WFC > Connection issues I clicked on “Retry Connection” and all connection steps has marked as solved.
    Right now the site is connected.

    My suggestion to anyone see “Checking connection…” stucked is to take a look in Connection Issues and then Retry.

    Thread Starter frensis

    (@frensis)

    Hi @sebd86 unfortunately I didn’t test cause I have no time till now.
    To make it work on my project I made a “not-so-elegant” workaround: I made a custom endpoint which create a mirror cart with user addresses and return shipping packages/methods to frontend.
    Once user select shipping options (method and/or extra fees like insurance) I send right data to the backend only when user place order, so totals are calculated only one time at the end of shopping flow.

    It’s a bit longer but it seems to work.

    For my first release I think I will go with this setup…. waiting to have time to test your new branch or someone else do it! =)

    Thread Starter frensis

    (@frensis)

    Hi SΓ©bastien… thank you for your quick response.
    I’m a little busy right now, I will test it next week.

    Thread Starter frensis

    (@frensis)

    UPDATE: I just made a simple test to send or reset customer data.

    async function resetCustomer() {
    try {
    const config = useRuntimeConfig()
    const endpointBase = config.public.endpoint_api
    const endpoint =
    ${endpointBase}cocart/v2/cart/update
    const cartKey = useCookie('cart_key').value
    if (!cartKey) {
    console.error('⚠️ cart_key not found')
    return
    }
    // Send dummy data to CoCart
    const emptyPayload = {
    first_name: "11",
    last_name: "22",
    email: "[email protected]",
    phone: "99",
    company: "",
    address_1: "33",
    address_2: "44",
    city: "55",
    state: "88",
    country: "77",
    postcode: "66",
    // Shipping data
    s_first_name: "1010",
    s_last_name: "1111",
    s_company: "",
    s_address_1: "1212",
    s_address_2: "1313",
    s_city: "1414",
    s_state: "1717",
    s_country: "1616",
    s_postcode: "1515",
    ship_to_different_address: true
    }
    const response = await $fetch(endpoint, {
    method: 'POST',
    query: {
    cart_key: cartKey,
    namespace: 'update-customer'
    },
    body: emptyPayload,
    headers: {
    'Content-Type': 'application/json'
    }
    })
    console.log('βœ… Customer reset done. Backend response:', response)
    await logCustomer()
    } catch (err) {
    console.error('Reset customer error:', err)
    }
    }

    What I see when I log customer data after reset is that shipping_country and shipping_state aren’t update. What I missed?

    So I suppose that shipping cost calculation is forced on shipping_country…. and shipping_country is coupled with billing_country only for the first assignment.

    Thread Starter frensis

    (@frensis)

    My 5-star review will come on my retirement day, when I can truly take stock of my life with Woocommece πŸ˜‰β€‹

    Thread Starter frensis

    (@frensis)

    You are great Lourens! It works.
    How nice it would be if everything could be resolved so simply and quickly!
    Five stars for you.

    Thread Starter frensis

    (@frensis)

    Hi Sai, thank you for your quick reply which confirm in part what I suppose.

    Just a little misunderstand: I’m talking about Woo Analytics reports in backend =)
    Of course I logged-in as admin in my backend WP installation, where I manage all kind of content (post/page/products).
    That said, no data is shown in Woo Report and probably it is because report try to fetch the “wrong domain” (frontend).

    WordPress settings are:
    define( 'WP_SITEURL', 'http://domain-backend.test' );
    define( 'WP_HOME', 'http://domain-frontend.test' );


    It seems that this kind of configuration results in a wrong routing for some woocommerce backend activity (also a bottom left snackbar alert is shown with a “generic error”).

    Thread Starter frensis

    (@frensis)

    ### WordPress Environment ###

    WordPress address (URL): http://domain-backend.test

    Site address (URL): http://domain-frontend.test

    WC Version: 10.1.2

    Legacy REST API Package Version: Il plugin API REST legacy non Γ¨ installato in questo sito.

    Action Scheduler Version: βœ” 3.9.3

    Log Directory Writable: βœ”

    WP Version: 6.8.2

    WP Multisite: –

    WP Memory Limit: 512 MB

    WP Debug Mode: βœ”

    WP Cron: βœ”

    Language: it_IT

    External object cache: –

    ### Server Environment ###

    Server Info: nginx/1.23.3

    Server Architecture: Darwin 23.6.0 arm64

    PHP Version: 7.4.33

    PHP Post Max Size: 512 MB

    PHP Time Limit: 30

    PHP Max Input Vars: 5000

    cURL Version: 7.87.0

    (SecureTransport) OpenSSL/1.1.1s

    SUHOSIN Installed: –

    MySQL Version: 5.7.23

    Max Upload Size: 512 MB

    Default Timezone is UTC: βœ”

    fsockopen/cURL: βœ”

    SoapClient: βœ”

    DOMDocument: βœ”

    GZip: βœ”

    Multibyte String: βœ”

    Remote Post: βœ”

    Remote Get: βœ”

    ### Database ###

    WC Database Version: 10.1.2

    WC Database Prefix: 1Gr3P_

    Dimensione totale database: 17.54MB

    Dimensione dati database: 10.19MB

    Dimensione indice database: 7.35MB

    1Gr3P_woocommerce_sessions: Dati: 0.02MB + indice: 0.02MB + motore InnoDB

    1Gr3P_woocommerce_api_keys: Dati: 0.02MB + indice: 0.03MB + motore InnoDB

    1Gr3P_woocommerce_attribute_taxonomies: Dati: 0.02MB + indice: 0.02MB + motore InnoDB

    1Gr3P_woocommerce_downloadable_product_permissions: Dati: 0.02MB + indice: 0.06MB + motore InnoDB

    1Gr3P_woocommerce_order_items: Dati: 0.02MB + indice: 0.02MB + motore InnoDB

    1Gr3P_woocommerce_order_itemmeta: Dati: 0.06MB + indice: 0.03MB + motore InnoDB

    1Gr3P_woocommerce_tax_rates: Dati: 0.02MB + indice: 0.06MB + motore InnoDB

    1Gr3P_woocommerce_tax_rate_locations: Dati: 0.02MB + indice: 0.03MB + motore InnoDB

    1Gr3P_woocommerce_shipping_zones: Dati: 0.02MB + indice: 0.00MB + motore InnoDB

    1Gr3P_woocommerce_shipping_zone_locations: Dati: 0.02MB + indice: 0.03MB + motore InnoDB

    1Gr3P_woocommerce_shipping_zone_methods: Dati: 0.02MB + indice: 0.00MB + motore InnoDB

    1Gr3P_woocommerce_payment_tokens: Dati: 0.02MB + indice: 0.02MB + motore InnoDB

    1Gr3P_woocommerce_payment_tokenmeta: Dati: 0.02MB + indice: 0.03MB + motore InnoDB

    1Gr3P_woocommerce_log: Dati: 0.02MB + indice: 0.02MB + motore InnoDB

    1Gr3P_actionscheduler_actions: Dati: 0.02MB + indice: 0.16MB + motore InnoDB

    1Gr3P_actionscheduler_claims: Dati: 0.02MB + indice: 0.02MB + motore InnoDB

    1Gr3P_actionscheduler_groups: Dati: 0.02MB + indice: 0.02MB + motore InnoDB

    1Gr3P_actionscheduler_logs: Dati: 0.02MB + indice: 0.03MB + motore InnoDB

    1Gr3P_cocart_carts: Dati: 0.25MB + indice: 0.02MB + motore InnoDB

    1Gr3P_commentmeta: Dati: 0.02MB + indice: 0.03MB + motore InnoDB

    1Gr3P_comments: Dati: 0.02MB + indice: 0.09MB + motore InnoDB

    1Gr3P_icl_background_task: Dati: 0.02MB + indice: 0.00MB + motore InnoDB

    1Gr3P_icl_content_status: Dati: 0.02MB + indice: 0.02MB + motore InnoDB

    1Gr3P_icl_core_status: Dati: 0.02MB + indice: 0.02MB + motore InnoDB

    1Gr3P_icl_flags: Dati: 0.02MB + indice: 0.02MB + motore InnoDB

    1Gr3P_icl_languages: Dati: 0.02MB + indice: 0.03MB + motore InnoDB

    1Gr3P_icl_languages_translations: Dati: 0.20MB + indice: 0.17MB + motore InnoDB

    1Gr3P_icl_links_post_to_post: Dati: 0.02MB + indice: 0.02MB + motore InnoDB

    1Gr3P_icl_links_post_to_term: Dati: 0.02MB + indice: 0.02MB + motore InnoDB

    1Gr3P_icl_locale_map: Dati: 0.02MB + indice: 0.00MB + motore InnoDB

    1Gr3P_icl_message_status: Dati: 0.02MB + indice: 0.03MB + motore InnoDB

    1Gr3P_icl_mo_files_domains: Dati: 0.02MB + indice: 0.02MB + motore InnoDB

    1Gr3P_icl_node: Dati: 0.02MB + indice: 0.00MB + motore InnoDB

    1Gr3P_icl_reminders: Dati: 0.02MB + indice: 0.00MB + motore InnoDB

    1Gr3P_icl_strings: Dati: 2.52MB + indice: 4.27MB + motore InnoDB

    1Gr3P_icl_string_batches: Dati: 0.02MB + indice: 0.00MB + motore InnoDB

    1Gr3P_icl_string_packages: Dati: 0.02MB + indice: 0.00MB + motore InnoDB

    1Gr3P_icl_string_positions: Dati: 0.06MB + indice: 0.02MB + motore InnoDB

    1Gr3P_icl_string_status: Dati: 0.02MB + indice: 0.02MB + motore InnoDB

    1Gr3P_icl_string_translations: Dati: 1.52MB + indice: 0.38MB + motore InnoDB

    1Gr3P_icl_translate: Dati: 0.09MB + indice: 0.02MB + motore InnoDB

    1Gr3P_icl_translate_job: Dati: 0.02MB + indice: 0.02MB + motore InnoDB

    1Gr3P_icl_translations: Dati: 0.02MB + indice: 0.06MB + motore InnoDB

    1Gr3P_icl_translation_batches: Dati: 0.02MB + indice: 0.00MB + motore InnoDB

    1Gr3P_icl_translation_downloads: Dati: 0.02MB + indice: 0.00MB + motore InnoDB

    1Gr3P_icl_translation_status: Dati: 0.05MB + indice: 0.03MB + motore InnoDB

    1Gr3P_links: Dati: 0.02MB + indice: 0.02MB + motore InnoDB

    1Gr3P_options: Dati: 2.06MB + indice: 0.08MB + motore InnoDB

    1Gr3P_postmeta: Dati: 0.16MB + indice: 0.14MB + motore InnoDB

    1Gr3P_posts: Dati: 0.27MB + indice: 0.06MB + motore InnoDB

    1Gr3P_termmeta: Dati: 0.02MB + indice: 0.03MB + motore InnoDB

    1Gr3P_terms: Dati: 0.02MB + indice: 0.03MB + motore InnoDB

    1Gr3P_term_relationships: Dati: 0.02MB + indice: 0.02MB + motore InnoDB

    1Gr3P_term_taxonomy: Dati: 0.02MB + indice: 0.03MB + motore InnoDB

    1Gr3P_usermeta: Dati: 0.02MB + indice: 0.03MB + motore InnoDB

    1Gr3P_users: Dati: 0.02MB + indice: 0.05MB + motore InnoDB

    1Gr3P_wc_admin_notes: Dati: 0.05MB + indice: 0.00MB + motore InnoDB

    1Gr3P_wc_admin_note_actions: Dati: 0.02MB + indice: 0.02MB + motore InnoDB

    1Gr3P_wc_category_lookup: Dati: 0.02MB + indice: 0.00MB + motore InnoDB

    1Gr3P_wc_customer_lookup: Dati: 0.02MB + indice: 0.03MB + motore InnoDB

    1Gr3P_wc_download_log: Dati: 0.02MB + indice: 0.03MB + motore InnoDB

    1Gr3P_wc_orders: Dati: 0.02MB + indice: 0.11MB + motore InnoDB

    1Gr3P_wc_orders_meta: Dati: 0.02MB + indice: 0.03MB + motore InnoDB

    1Gr3P_wc_order_addresses: Dati: 0.02MB + indice: 0.06MB + motore InnoDB

    1Gr3P_wc_order_coupon_lookup: Dati: 0.02MB + indice: 0.03MB + motore InnoDB

    1Gr3P_wc_order_operational_data: Dati: 0.02MB + indice: 0.03MB + motore InnoDB

    1Gr3P_wc_order_product_lookup: Dati: 0.02MB + indice: 0.08MB + motore InnoDB

    1Gr3P_wc_order_stats: Dati: 0.02MB + indice: 0.05MB + motore InnoDB

    1Gr3P_wc_order_tax_lookup: Dati: 0.02MB + indice: 0.03MB + motore InnoDB

    1Gr3P_wc_product_attributes_lookup: Dati: 0.02MB + indice: 0.02MB + motore InnoDB

    1Gr3P_wc_product_download_directories: Dati: 0.02MB + indice: 0.02MB + motore InnoDB

    1Gr3P_wc_product_meta_lookup: Dati: 0.02MB + indice: 0.11MB + motore InnoDB

    1Gr3P_wc_rate_limits: Dati: 0.02MB + indice: 0.02MB + motore InnoDB

    1Gr3P_wc_reserved_stock: Dati: 0.02MB + indice: 0.00MB + motore InnoDB

    1Gr3P_wc_tax_rate_classes: Dati: 0.02MB + indice: 0.02MB + motore InnoDB

    1Gr3P_wc_webhooks: Dati: 0.02MB + indice: 0.02MB + motore InnoDB

    1Gr3P_wpml_mails: Dati: 1.52MB + indice: 0.02MB + motore InnoDB

    1Gr3P_yoast_indexable: Dati: 0.02MB + indice: 0.09MB + motore InnoDB

    1Gr3P_yoast_indexable_hierarchy: Dati: 0.02MB + indice: 0.05MB + motore InnoDB

    1Gr3P_yoast_migrations: Dati: 0.02MB + indice: 0.02MB + motore InnoDB

    1Gr3P_yoast_primary_term: Dati: 0.02MB + indice: 0.03MB + motore InnoDB

    1Gr3P_yoast_seo_links: Dati: 0.02MB + indice: 0.03MB + motore InnoDB

    ### Post Type Counts ###

    acf-field: 212

    acf-field-group: 4

    acf-ui-options-page: 1

    attachment: 6

    nav_menu_item: 16

    page: 21

    post: 3

    product: 4

    revision: 43

    shop_order_placehold: 30

    ### Security ###

    Secure connection (HTTPS): ❌

    Il tuo negozio non utilizza HTTPS. Scopri di piΓΉ su HTTPS e certificati SSL .

    Hide errors from visitors: ❌I messaggi di errore non saranno mostrati ai visitatori.

    ### Active Plugins (16) ###

    Advanced Custom Fields Multilingual: di OnTheGoSystems – 2.1.5

    Advanced Custom Fields PRO: di WP Engine – 6.5.1

    CoCart API - Headless eCommerce API for Developers: di CoCart Headless

    LLC – 4.7.0

    Classic Editor: di Contributori WordPress – 1.6.7

    CoCart CORS Support: di CoCart Headless

    LLC – 1.0.7

    Yoast Duplicate Post: di Enrico Battocchi & Team Yoast – 4.5

    JWT Authentication for WP-API: di Enrique Chavez – 1.4.0

    Mailgun: di Mailgun – 2.1.9

    WPML Multilingual CMS: di OnTheGoSystems – 4.8.1

    WooCommerce Multilingual & Multicurrency: di OnTheGoSystems – 5.5.2

    WooCommerce: di Automattic – 10.1.2

    Yoast SEO: di Team Yoast – 25.9

    WP Mail Logging: di WP Mail Logging Team – 1.15.0

    WPML SEO: di OnTheGoSystems – 2.2.3

    Traduzione di stringhe Wpml: di Onthegosystems – 3.4.0

    Yoast Test Helper: di Team Yoast – 1.18

    ### Inactive Plugins (1) ###

    Contact Form 7 Multilingual: di OnTheGoSystems – 1.3.2

    ### Settings ###

    Legacy API Enabled: –

    Force SSL: –

    Currency: EUR (€)

    Currency Position: left_space

    Thousand Separator: .

    Decimal Separator: ,

    Number of Decimals: 2

    Taxonomies: Product Types: external (external)

    grouped (grouped)

    simple (simple)

    variable (variable)

    Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)

    exclude-from-search (exclude-from-search)

    featured (featured)

    outofstock (outofstock)

    rated-1 (rated-1)

    rated-2 (rated-2)

    rated-3 (rated-3)

    rated-4 (rated-4)

    rated-5 (rated-5)

    Connected to WooCommerce.com: –

    Enforce Approved Product Download Directories: βœ”

    HPOS feature enabled: βœ”

    Order datastore: Automattic\WooCommerce\Internal\DataStores\Orders\OrdersTableDataStore

    HPOS data sync enabled: –

    Enabled Features: analytics

    marketplace

    order_attribution

    site_visibility_badge

    email_improvements

    point_of_sale

    custom_order_tables

    ### Logging ###

    Enabled: βœ”

    Handler: Automattic\WooCommerce\Internal\Admin\Logging\LogHandlerFileV2

    Retention period: 30 giorni

    Level threshold: –

    Log directory size: 2 KB

    ### WC Pages ###

    Shop base: #298 - /shop/

    Carrello: #299 - /cart/ - Contiene il blocco woocommerce/cart

    Pagamento: #300 - /checkout/ - Contiene il blocco woocommerce/checkout

    Il mio account: #301 - /my-account/ - Contiene lo shortcode [woocommerce_my_account]

    Termini e condizioni: ❌ La pagina non è impostata

    ### Theme ###

    Name: Headless by Frensis

    Version: (aggiornamento alla versione 0 disponibile)

    Author URL:

    Child Theme: ❌ – Se stai modificando WooCommerce o un tema genitore che non hai costruito personalmente

    ti consigliamo di utilizzare un tema child. Vedi: Come creare un tema child

    Theme type: Tema classico

    WooCommerce Support: ❌ Non dichiarato

    ### Templates ###

    Overrides: –

    ### Admin ###

    Enabled Features: activity-panels

    analytics

    product-block-editor

    coupons

    core-profiler

    customize-store

    customer-effort-score-tracks

    import-products-task

    experimental-fashion-sample-products

    shipping-smart-defaults

    shipping-setting-tour

    homescreen

    marketing

    mobile-app-banner

    onboarding

    onboarding-tasks

    pattern-toolkit-full-composability

    product-custom-fields

    remote-inbox-notifications

    remote-free-extensions

    payment-gateway-suggestions

    printful

    shipping-label-banner

    subscriptions

    store-alerts

    transient-notices

    woo-mobile-welcome

    wc-pay-promotion

    wc-pay-welcome-page

    launch-your-store

    add-to-cart-with-options-stepper-layout

    Disabled Features: product-data-views

    experimental-blocks

    experimental-iapi-mini-cart

    experimental-iapi-runtime

    coming-soon-newsletter-template

    minified-js

    product-pre-publish-modal

    settings

    async-product-editor-category-field

    product-editor-template-system

    use-wp-horizon

    experimental-wc-rest-api

    Daily Cron: βœ” Next scheduled: 2025-09-12 08:59:15 +02:00

    Options: βœ”

    Notes: 59

    Onboarding: -

    ### Action Scheduler ###

    Completato: 24

    Oldest: 2025-09-10 09:45:50 +0200

    Newest: 2025-09-12 10:30:45 +0200

    Operazione non riuscita: 10

    Oldest: 2025-07-02 11:01:45 +0200

    Newest: 2025-09-11 10:18:05 +0200

    In attesa: 11

    Oldest: 2025-09-12 11:02:15 +0200

    Newest: 2025-09-27 10:03:15 +0200

    ### CoCart ###

    Version: 4.7.0

    Database Version: 4.7.0

    Install Date: 10 July 2025

    Cart Sessions:

    Carts in Session: 135

    Carts Active: 135 out of 135 in session.

    Carts Expiring Soon: 39 out of 135 in session.

    Carts Expired: 0 out of 135 in session.

    Carts Created (by CoCart): 134

    Carts Created (by Web): 1

    Carts Created (by Other): 0

    ### Status report information ###

    Generated at: 2025-09-12 10:50:14 +02:00
    Thread Starter frensis

    (@frensis)

    Of course… my request is just to centralize speed optimization in one place (WPFC).

    Thread Starter frensis

    (@frensis)

    Yeah, I suppose is a kind of that.
    Something like:
    <link rel="dns-prefetch" href="//use.typekit.net">
    <link rel="preconnect" href="https://use.typekit.net" crossorigin>

    I don’t have enough skill to tell you which is the best for performance….. I only saw it in one of your competitor plugin =)

    Thread Starter frensis

    (@frensis)

    Hi Peter, thank you for your clarification.
    “Local changes” status was due to slightly differences like spaces in notification emails list.

    Anyway I didn’t know “Review changes” feature… I got it!

    Thread Starter frensis

    (@frensis)

    Hello there… I only get back into this right now, sorry for the delay.
    After few tests I found something which could cause an issue about styling credit cards fields: I’m using a child theme for Storefront and I started style from scratch dequeuing parent templates:

    add_action( 'wp_enqueue_scripts', 'sf_child_theme_dequeue_style', 999 );
    function sf_child_theme_dequeue_style() {
    wp_dequeue_style( 'storefront-style' );
    wp_dequeue_style( 'storefront-woocommerce-style' );
    }

    If I comment these lines, credit cards fields inherit some style and they look better.
    But for me isn’t possible to apply default Storefront style cause I will loose tons of ready-made work.

    Is there a way to get style only for woopayments iframe? Or dequeue all except checkout payment fields?

    Thread Starter frensis

    (@frensis)

    Hi @shameemreza, thank you for your reply… I will check with Storefront (parent) and deactivating other plugins.
    Anyway, I read somewhere that I need to wait 24h to see changes: is it right?
    If so, is it possible to force changes to see it quickly?

    Thread Starter frensis

    (@frensis)

    I’m replying just to subscribe to future updates because no-one solution found on these pages works for me.
    Everyone link these pages:
    https://woocommerce.com/document/stripe/customization/style-payment-form/
    https://woocommerce.com/document/woopayments/customization-and-translation/customize-payments-appearance/

    No changes appear to me, no matter what I did.
    Clear transient via the code below broke the site:
    delete_transient( 'wcpay_upe_appearance' );
    delete_transient( 'wcpay_wc_blocks_upe_appearance' );

    Is’t easier and less time-consume for everyone to post an how-to video?

    Folks just asking for 3 simple options:

    • font color
    • fields background
    • fields borders

    I suppose these things are easier then collecting payments all over the world in different currencies, from different methods 😘
    Please help lot of wp developer!

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