Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Yes, getting the same issue as well.

    I contacted Strip about this – because I initially thought it was a Stripe issue. They investigated the charge being created – it initially starts and creates a source, but doesn’t follow up with creating the charge.

    Here’s a quote from the support chat I had with Stripe:

    “It looks like the integration has changed how they’re sending the information over to Stripe, and aren’t completing the charge”

    Hoping WooCommerce fixes this asap!

    I’ve had this issue as well.

    After testing each option, can confirm it is the:

    Google Tag Manager for WordPress options > Integration > WooCommerce > Track enhanced e-commerce (beta) option

    Unticking that option will fix the issue (but obviously no longer track ecommerce).

    Hi @tacoverdo,

    Although it looks like this is a done deal, I just wanted to add my disappointment about this decision as well.

    I’ve used this feature on tons of sites, and to just remove it has resulted in a really poor user experience for me.

    I have some Yoast Premium plugins (so I am a paying customer, not someone who’s never paid a cent and complains about items in a free version), but this decision just feels like a way of forcing me to upgrade to Premium on more sites.

    I can understand some of your technical points in your earlier response about why you decided to do this, but honestly, they come across as lame justifications. If there’s a performance issue associated with using the feature, then by all means mention this and recommend we don’t use the feature. But to just remove it… you’ve caused additional work for us, especially if I want to remove an existing one. Really disappointing.

    My request would be that you please reconsider this decision and restore the functionality.

    Thanks.

    I’ve been having this issue for the last few days, no idea why it suddenly started.

    Finally seemed to have fixed it temporarily by:
    – going to the Plugins page, selecting all plugins, and Deactivate (by bulk action). Note you must choose ALL plugins, don’t try to deactivate them individually
    – browse to site, refresh a few pages (they will still all give an error)
    – go back to Plugins, select all plugins, Activate (by Bulk Action)
    – visit site again, all pages working again

    However, if I go the Permalinks setting, and click Save again (without changing the setting – it is still set as /%postname%/) the issue returns (ie page errors).

    So, make sure you set the permalinks setting first, then go through and to the process above.

    Hope this helps.

    This may help:
    In WooCommerce > Settings > Pages
    make sure you DON’T have the My Account page and the Logout page pointing to the same thing.
    eg make a special, separate page to use as your Logout page.

    I’ve had this aswell – on posts that have hundreds of comments (using disqus) it would hang if I had W3 enabled (disabled it was fine). It was especially bad in IE. FF and Chrome seem to handle it better.
    To get around the issue I just enabled pagination in disqus settings so that only 20 comments are loaded initially.
    I note Mashable do this aswell.
    I also have the disqus Javascript option enabled.

Viewing 6 replies - 1 through 6 (of 6 total)