itmustbeboojum

I always like to add a note to old threads when solutions are found.

In this case, the solution was to install Cloudflare’s mod_cloudflare for Apache httpd on my server. Not something everyone might be able to do, but something that certainly sorted this problem out once and for all.

Now my IPs are reported properly, instead of appearing to be Cloudflare IPs! And Jetpack Protect is happy as a result ??

https://www.cloudflare.com/technical-resources/

Haha I thought that was kind of odd, setting that filter to false (as suggested above). I inspected the logic inside class-wc-gateway-stripe.php and then set the filter to true in my functions.php like so:

add_filter( 'wc_stripe_send_stripe_receipt', '__return_true' );

Worked a treat, I get the customer email in the receipt_email field in Stripe, and the integration with Drip works as a result! ??

I’m also seeing a problem with Stripe receipts and also Drip integration, seemingly because “receipt_email” is “null” in my Stripe event.

I’ve ensured receipt emails are enabled in Stripe.

I’ve also added the filter you suggested to my functions.php file:

add_filter( 'wc_stripe_send_stripe_receipt', '__return_false' );

Even with these changes, I’m still not getting any “receipt_email” through the Stripe WooCommerce Gateway into Stripe. Under “metadata”, “Customer Email” records the correct email address, but “receipt_email” continues to be “null”.

How can I get the WooCommerce Stripe Gateway to include the email address in the “receipt_email” field?

I don’t mind using WooCommerce for receipts instead of Stripe, but not sending that email in that field appears to affect other things like my Drip email marketing integration (which gets test charge events sent directly from within Stripe, but not from Stripe when WooCommerce is the one creating the event).

I feel really bad about reopening that ticket yet again, especially as I was told by the support person that he wasn’t sure what else to do for me, other than advising me to turn off Jetpack Protect, which I sadly did for one of my sites. But if you know how to deal with it, that’d be so helpful! I am my own host, so I can likely make the necessary changes too ?? This is a problem I’m having with several sites, so let me give just one of them here, which still has both Jetpack Protect and Cloudflare’s Free plan on it: https://chainsaw.buzz

Thank you so much for your help! I’d love to be able to use Jetpack Protect and Cloudflare’s Free plan together again on all of my sites, without fear of getting locked out because of appearing to be using a blocked CloudFlare IP (rather than my own IP).

Incidentally I am just using CloudFlare’s Free Plan. I’ve seen other threads in this forum mentioning problems with something of theirs called RailGun but that is not something I am using. I am simply using them for their basic protection plus HTTPS rewrites.

Hi,

I contacted your support and it seemed that we got to the bottom of it, but now I’m having troubles with Jetpack Protect blocking me entirely (not even allowing me to solve a math problem) because it’s seeing a (banned) CloudFlare IP address.

I am using CloudFlare, and your support ended up suggesting I turn off Jetpack Protect as the only solution (other than turning off CloudFlare). Is there really no way to have these two services work together? Protect blocks a lot of apparently malicious traffic, and so does CloudFlare; I’d love it if they would work together, rather than getting intermittently locked out entirely from my control panel (intermittent because the CloudFlare IP changes from time to time, so sometimes I can get in, and other times I’m entirely blocked).

Thanks so much!

Thank you so much for posting a reply to this thread. I wish I could report the bug to Facebook, because it’s odd (not to mention embarrassing) to have lost close to 600 shares built up over years!

Unfortunately I cannot appear to report the bug at the link you provided without a Facebook account. I’ve never been on Facebook, but people still shared my website link, hence my reasonable share count (before it mysteriously disappeared right around October 9th-ish).

I suppose there’s nothing to be done, other than record my experience here, in case it helps someone else to know that other sites suddenly lose share counts from years of data overnight with Facebook ??

Never mind somehow Facebook (their actual API or graph or whatever) has equalized the counts to 14 between http and https, losing all my many years worth of shares, almost 600 ?? Oddly, when I checked the links above other day (querying their graph), the shares had flipped, showing 594 on https versus 14 on http (before it was the other way around, and I triple-checked this to make sure I wasn’t going nuts). Too bad they equalized with my lowest count rather than highest, I’m so unhappy about losing so many years’ worth of shares data, but there’s no support of course at Facebook for such a case, and I haven’t read anywhere else on the web of something like this happening. It strikes me as a database error on their part, as for all my other sites there are still more shares on http rather than https. Why they flipped, and then why my share count was mysteriously reset after so many years, I’ve no idea ??

In case someone else finds this post and is looking to do the same thing (if you have large listings in your menus and wish to reduce Storefront’s default menu item padding). Here’s the tweaked Sass/CSS to add a 0.5s delay to the closing of menus and submenus (also works fine on touch-devices at this media breakpoint too). I put this in my Storefront child theme, the bit that’s being overwritten is in storefront > sass > components > _menu.scss

@media screen and (min-width: 768px) {
  .main-navigation,
  .secondary-navigation {

    ul {
      display: block;
      visibility: visible;
      transition-delay: 0s;

      li {
        &:hover,
        &.focus {
          > ul {
            display: block;
            visibility: visible;
            transition-delay: 0s;
          }
        }
      }

      ul {
        display: block;
        visibility: hidden;
        transition: visibility 0s 0.5s;

        ul {
          left: 100%;
          top: 0;
        }
      }
    }
  }
}

Ah, ok, that makes sense. I’m writing a child theme for Storefront, so yes, I did change the size of the dropdown menu items (I know super-large menus are the trend right now, but when you’ve lots of items in a menu for, say, categories on a photo portfolio site, the menu padding needs trimming in that case). Perhaps I can add a delay for usability with CSS animations?

So I found the spot to change with help from another thread I found searching. But it seems unwise security-wise to strip the URL encoding?

wp-content/plugins/woocommerce/includes/abstracts/abstract-wc-order.php

Changed line 2074 from 'email' => urlencode( $this->billing_email ) to 'email' => $this->billing_email

Now my email download links work, at least! But how should this be working, I ask myself?

So the problem is that the email links all include %40 in place of the @ sign… is that something I can change?

When I change %40 to @ manually in the URL copied from the email download link, then the product download works just fine.

I’ve read in other support threads that the @ sign is supposed to be encoded in this way with %40 but it breaks for me ??

Any ideas for how to get the email download links working, can I override that encoding somewhere? This is the only thing holding me back from taking my new WooCommerce site live!

Thank you for taking the time to upload a screenshot of the setting in question. I am (obviously) somewhat unfamiliar still with WordPress. I need to spend some time exploring all the settings on my local test install!

In any case, this resolved my issue for the moment, letting me display product thumbnails on the Cart page at least ??

I’d like to see product thumbs appear to the left of each product description on the Cart page, as well as in the Your Order section of the Checkout page above/next to each product description.

It would be nice (though less important) to have product thumbs show up on the Order Summary available to customers in My Account too.

How do I enable the full-width page template? I see it in the php files. I’m an html5/css/sass person with far less php knowledge!

Thanks in advance ??

I fixed it! Back to my proper share count in Facebook (I lost the 5 shares in the interim unavoidably though). Here’s how I solved it, in case others find this thread.

First, I queried Facebook’s API directly with the following special links. Here I discovered that Facebook is treating the “http” and “https” versions of my site as separate entities within their sharing “graph”:
https://api.facebook.com/restserver.php?method=links.getStats&urls=https://savebees.org
https://api.facebook.com/restserver.php?method=links.getStats&urls=https://savebees.org

I took a quick refresher on Open Graph tags, and installed this plugin: “Facebook Open Graph, Google+ and Twitter Card Tags (1.5.2)” I did this because I found out that what I wanted was to get an “og:url” meta tag on my page, which Facebook (and other sharing networks) see as the canonical URL for a given page. The deal is that one wants the og:url tag to point to the well-shared version of one’s site (in my case the “http” version). Then one can let the 301 redirect in the .htaccess (which sends all http requests to https) do its thing.

I then changed my WordPress General Settings back for WordPress URL and Site Address URL to “http” rather than “https”, because that’s what the plugin uses to set the link in the meta tag “og:url”. I had originally changed them to “https” because I wanted to make it easy on myself in the future when uploading images in posts/pages for those image sources to be https rather than http (to avoid those mixed-content security messages). Well, I’ll just edit those in the source of future posts manually until I find another way to set the “og:url” tag separately from modifying the General Settings in WordPress. For now, I’m just happy to have my many FB shares back!

Odd that Twitter didn’t have this issue with its share count (more sensibly seeing the “http” and “https” versions of my site as one and the same sharing object). It irritates me to change the way I wish to do something simply for Facebook. If only I’d setup my site to be https at the very beginning! For now this works though, and I’m happy to move onto other things. If anyone has a better suggestion, feel free to post it ??