Uncought error with shop checkout

  • Resolved archangelsk1981

    (@archangelsk1981)


    4 years, 10 months ago

    We are using a wordpress installation using woocommerce plugin to have a shop functionality. Since we activated xpress plugin to sync comments to our xenforo bb, we have the problem, that final checkout in woocomerce results in an error.

    Error thrown
    Call to undefined method Pelago\Emogrifier\HtmlProcessor\HtmlPruner::fromHtml()

    We were able to reduce the error to xpress plugin parallely activated to woocommerce, as this error only occurs when xpress is activated.

    Unfortunately it is not possible to get more stacktrace, even with wordpress debug mode. And I even only get the error code, when I have WP Rocket for Caching activated. When this is also deactivted, final checkout occurs in a Black page without any error message.

    And as well, I already checked xpress plugin, they don’t use Emogrifier from a code analysis i performed. I as well created a ticket with xpress, but i am not sure, why this error occurs on plugins site, as the plugin is not relevant in the situation of woocommerce checkout.

    Has anyone a further idea on this?

    Thanks for your support!

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

  • Hello,

    I also have the same problem.

    And similarly, disabling Xpress plugin solved the problem for me. I wrote ticket to them and they said their plugin is not causing the problem, everything going on WordPress/Woocommerce side.

    Hmmmm. I’m also hitting an error with a Xenforo integration (not Xpress) and WC 4.1 and later. Disabling the XF integration solves it, or I can work around it by setting WC to Plain Text emails instead of HTML. Neither is a great solution. Did either of you get any further on this?

    I think I’ve got it. About a year ago, I ran into an issue where WordPress and Xenforo had different versions of Sodium Compat and it was causing fatal errors. I think the same thing is happening here.

    I’ve just tried replacing both XF and WP’s Emogrifier files with the latest and the WordPress errors are gone. I’m not a developer, I could be way off base here, and I’ve got a load more testing to do… but if it seems to check out, I’ll post back with more specifics.

    Ok, everything looks ok, but do your own testing…

    I went to https://github.com/MyIntervals/emogrifier/releases and scrolled down to 3.1.0 (NOT 4.0.0, as that changes filenames). Click Assets and then download the zip.

    For Xenforo, navigate to /src/vendor/pelago/emogrifier, rename that emogrifier folder (in case you want to put the original back) and upload the contents of the zip into a new emogrifier folder.

    For WordPress, navigate to /wp-content/plugins/woocommerce/vendor/pelago/emogrifier and again, rename the emogrifier folder and upload the contents of the zip into a new emogrifier folder.

    In my testing, that appears to solve the issue, but YMMV.

    Thread Starter archangelsk1981

    (@archangelsk1981)

    Oh, this sounds promising. I will try it. Have you tried only updating one installation?

    I tried it on my usual staging site, which stopped throwing errors (but has the actual sending of emails disabled, to save my customers receiving doubles) and then set up a clean install of WP&XF to test it more fully, including actually sending the emails to myself. I can’t push it to my live site this week due to other commitments, but I’m happy enough that I will at the end of the week.

    Thread Starter archangelsk1981

    (@archangelsk1981)

    I tried it today. WooCommerce is already using 3.1 version, as like you wrote, pelago 4.0 is changing the internal API, according to docu.

    So I updated Xenforo’s Pelago installation from 2.1.1 to 3.1 and now everything works fine.

    I will send this XPress support as well, perhaps thy will fix it.
    Perhaps it would be good, if you also update this to XPress support.

    • This reply was modified 4 years, 8 months ago by archangelsk1981. Reason: typo

    > Perhaps it would be good, if you also update this to XPress support.

    I don’t use Xpress (I use a custom bridge) so I doubt they’ll want to hear from me!

    Glad to hear it worked for you too!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Uncought error with shop checkout’ is closed to new replies.