Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter TrulineGraphics

    (@trulinegraphics)

    Sorry I just saw this reply, still fighting this issue.

    I had reached out to official WC support before I posted this question because after 2 back and forth emails they were clueless and suggested I post here. I suspect the change was made here:

    = 8.9.3 2024-06-10 = **WooCommerce** * Security – Prevent HTML & JS injection attacks on registration and checkout forms when the Order Attribution is enabled.

    That doesn’t specifically say it was changed but it’s extremely illogical to add sql injection prevention on the payment form where customers are trying to pay for their order. This page is only accessed with a unique direct link that is sent to them via email or text. The only thing I could do is revert back to a much older version of the plugin. If I can’t get the WooCommerce team to even admit they changed this, there’s no way I’m finding a work around or fix for the issue. I think it’s because they would publicly admit there was a vulnerability. I just have to accept defeat and lose more orders because of a bad coding policy I guess lol, there’s nothing I can do at this point.

    Thread Starter TrulineGraphics

    (@trulinegraphics)

    darkallman, for the password are you referring to the fallback email menu? I know that screen in the settings has a username/password field but those are blank on mine. I never setup the fallback email failure stuff up. Is that possible issue?

    For my site I did a connectivity test and it does the following:
    api.mailgun.net:25 = Service Not Available
    api.mailgun.net:465 = Service Not Available
    api.mailgun.net:587 = Service Not Available
    Mailgun API – api.mailgun.net:443 – OPEN

    Not sure if the lack of connection with the other ports are a problem? It seems like there’s definitely something missing. For credentials I don’t know what “password” I would need.

    Thread Starter TrulineGraphics

    (@trulinegraphics)

    I have removed the email addresses from the code below. This is the transcript from the test email that failed. It’s the same every time.

    https://api.mailgun.net:443
    
    Your credentials are incorrect.
    
    --Raw message follows--
    
    Array
    (
        [from] => SEND TO EMAIL REMOVED
        [to] => Array
            (
                [0] => MY EMAIL REMOVED
            )
    
        [subject] => Postman SMTP Test (heyloumedia.com)
        [h:X-Mailer] => //www.ads-software.com/plugins/post-smtp/)
        [h:Content-Type] => multipart/alternative
        [h:Sender] => EMAIL REMOVED
        [cc] => 
        [bcc] => 
        [h:message-id] => [email protected]
        [text] => Hello!
    
    Sent by Postman 2.0.20 - https://www.ads-software.com/plugins/post-smtp/
    
    Thread Starter TrulineGraphics

    (@trulinegraphics)

    I did not, just the PostSMTP plugin. I used the API secret key Mailgun gives me like I normally do. I setup all the MX, CNAME and subdomains per Mailgun’s instruction and their dashboard confirms everything is good on that side. Mailgun itself is a little confusing because their menus have API menus for each “domain” as well as the main account. I tried both API keys just for giggles, neither worked.

    For the record, the site is Divi based and I’m just using the Divi form. But the errors are showing up just using the “Send a test” function from inside the PostSMTP plugin.

    Thread Starter TrulineGraphics

    (@trulinegraphics)

    FYI, the Breeze caching plugin wasn’t even activated. I went ahead and deleted it because it wasn’t in use. That was ruled out.

    I did some more digging and the plugin called TM WooCommerce Extra Product Options was causing the issue. As soon as I disabled that, bingo the items added to the cart again. I should have known to try disabling that plugin since it directly related to the cart. Once I flushed cache from my SSL and deactivated the plugin BINGO. So the plugin doesn’t always tell you when it needs updates and the author doesn’t let you updated through the WP plugin panel, manual FTP upload BLEEH.

    At any rate I think we have it fixed. Bad plugin to ruin the day. Thanks for the replies!

    Thread Starter TrulineGraphics

    (@trulinegraphics)

    The multiple calls to JQuery was the problem. Each page was set to include the JQuery JS library in the WP page editor. The Thesis theme calls to Google’s library for JQuery, so unchecking that option on the page corrected the issue. it immediately began working.

    Thank you so much for the help. We will seriously consider buying the pro version as it has some cool options!

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