o[‘woo-cart-weight’] is undefined

  • Resolved Harm10

    (@harm10)


    2 months, 2 weeks ago

    To cope with WP 6.7.1 textdomain load problems I have set up my own WP test site to check several configurations of sites I maintain.
    One of them uses Woocommerce and your plugin to display the cart weight in shopping cart.
    As there are several sites I have created a WP multi site.

    A very weird thing happens for the site in the multi site set-up.
    This is using WP 6.7.1 Woocommerce 9.5.1 and 1.9.1 from your plugin.
    If I do an order and go to the shopping cart the weight is displayed normally. If I reload the page (browser normal option) the weight is replaced by o[‘woo-cart-weight’] is undefined. Pointing to the fact that the shortcode apparently is no longer there?
    If I refresh the page with Ctrl-F5 (so clearing the cache?) the weight is there again.
    This does not happen on my live site which is not a multi site (but also has somewhat older versions of WP and WC).
    I am not using caching plugins and have activated the plugins on the site level (so no network activation).

    Any idea what is wrong here?

    The page I need help with: [log in to see the link]

Viewing 12 replies - 16 through 27 (of 27 total)
  • Plugin Author grola

    (@grola)

    The plugin does not have a shortcode. We do not generate it.

    Thread Starter Harm10

    (@harm10)

    So what is [‘woo-cart-weight’] part pointing to then? Those brackets look like a shortcode to me?

    Plugin Author grola

    (@grola)

    Our plugin does not add a shortcode. Are you using the block-based checkout? This might be a message from the block-based checkout.

    Thread Starter Harm10

    (@harm10)

    I do not use block based output.
    Yesterday I implemented all new software (with WP 6.7.1) on a live single site.
    As I expected the problem does not occur there (even not in Firefox).

    I tried searching in all your file for the string but that did not help as the text domain has the same name.
    Then I tried searching on the components in the html: div class=”wc-block-components-discounts-meta css-0 e19lxcc00″ p>o[‘woo-cart-weight’] is undefined p>div> (I left out some slashes so you can see the html)
    But that also did not bring any hits.

    Do you have any suggestions on how to find where this error comes from?

    I tried using plugin Check Conflicts but the problem persists even when using WP 2025 theme and only Woocommerce and Cart Weight active.

    • This reply was modified 1 month, 3 weeks ago by Harm10.
    Plugin Author grola

    (@grola)

    The occurrence of the class wc-block-components-discounts-meta in the provided code suggests that some block-based component is generating this message. Could you provide the website address so I can take a look at how it appears?

    Thread Starter Harm10

    (@harm10)

    @grola Thanks for your reply. I think I mentioned this earlier. The problem occurs on my test multi site which is not openly available. And then also solely when using browser Firefox. Browsers Edge and Chrome do not have this problem. I am willing to define some user access to you but then I have the problem on how to tell you this. Obviously I do not want to publish this here.

    On a side note: I never work with blocks and also have no special plug-ins for that active. As reported when using Check Conflicts and switching everything off besides WooCommerce and Cart Weight the problem persisted. Even when I selected WP theme 2025. Could it maybe be something on the server side?

    Plugin Support tograczyk

    (@tograczyk)

    Hi @harm10,

    As for sharing access so we can work out more details, you can write to us directly at https://octolize.com/support/. You can use the Pre-sale question option.

    Best regards,
    Tomek

    Thread Starter Harm10

    (@harm10)

    @tograczyk I submitted the question on that url.

    Plugin Author grola

    (@grola)

    @harm10 thank you. We found the cause. The fix will probably be released tomorrow.

    Thread Starter Harm10

    (@harm10)

    @grola Good to hear! Does this mean you do not need access to my site any more?

    And just out of curiosity: what was wrong?

    Plugin Author grola

    (@grola)

    @harm10 please update to 1.9.4 and let us known if it works now on firefox.

    And just out of curiosity: what was wrong?
    You are using block based checkout. In Firefox, block components appear to behave differently than in other browsers. We have added support for this case.

    Thread Starter Harm10

    (@harm10)

    @grola I can confirm the fix works! Thanks for the support. I will revoke your support access.

Viewing 12 replies - 16 through 27 (of 27 total)
  • You must be logged in to reply to this topic.