Caleb Weeks

Hi @janwoostendorp – absolutely no worries at all on your timeline!

I’m amazed at your kind reply amidst a busy end of the week. Feel free to prioritize wherever you need (to mid-November or beyond). ????

• WPML Multilingual CMS: 4.2.9
• WPML Media: 2.5.3
• Default featured image: 1.6.1

Those are the main culprits, I believe. Take whatever time you need. Thanks, again, for even sending a quick note back, and congratulations on all of the work you’ve done in contributing to the WordPress Community – thanks directly and indirectly!

No rush to reply. ??

• This reply was modified 5 years, 1 month ago by Caleb Weeks. Reason: Unordered list for the plugins

Thanks for update, @aljullu! Will report back if we have any issues. ????

Thanks for bringing this up, @oclair! This was exactly what happened to us this morning (all morning!) and our hosts over at Flywheel did an awesome job (as always!) figuring it out.

Though WooCommerce Admin hasn’t reach version 1.0 yet at the time of this post, I couldn’t resist installing it, so I just learned that lesson again, alas, of the risks to using pre-1.0/beta software rather than waiting till it’s officially ready.

“Self-inflicted DDoS/DOS” – that’s exactly what it was!

Thanks, @marius_codeinwp!

Feature Request submitted. Thanks for that tip!

I think it is just a quick edit rather than an entire request, but it may be that the team specifically wanted inch marks instead of quotation marks. Either way, thank you, again! ??

• This reply was modified 5 years, 12 months ago by Caleb Weeks. Reason: Added link to Feature Request on Github

Thanks @jerparx!

Happy to know where this code lives.

Question: Can you think of any way to modify this without directly editing the plugin code? Perhaps via a function of some kind?

YOAST SEO gets regular updates and I would be constantly (manually) editing this, haha.

Thank you for your reply(!), and no expectation on my follow up question here in this note. I know this is a freely supported forum and even getting a reply is kind enough, so no worries.

Thanks, @jerpax! ??

• This reply was modified 6 years ago by Caleb Weeks.

Hi @rubengc – thanks for the quick reply!

That sounds good. We can approach it that way for sure. The fact that you even have that as a possibility is pretty cool. Thank you for that!

You guys are doing some great work with GamiPress – it is supper cool to see it grow.

Here is a screenshot from the early days of Gamipress (August 2017): https://cl.ly/3F2h0f0I3Z3m. It’s been fun to see it grow, and I think it will all the more with the foundation and ongoing, solid work you are all putting into it – I hope it is still fun and encouraging for you! ??

Thanks, again, for working on it so faithfully (and diligently). No need to reply! Thanks, @rubengc. ????

Hi @xguiboy and @rynald0s,

We installed the Disable Cart Fragments plugin which completely removed this code.

This made sense in our case because we were really just using WooCommerce as a “Catalog” with links to external items (no cart or checkout).

Regarding actual full site loading on Pingdom Tools, etc., the cart fragments loads via AJAX so, as far as I know, it won’t actually affect the full site loading time (as I realized after the fact), but it is, at least, one less request.

I know this thread is old, but hopefully it can help in case someone happens upon it.

Thanks, @patjk, for your reply! Ours was cleared up by our hosts (firewall) and we haven’t had any trouble since. In my experience with Postman SMTP, the culprit is often external, so I look to the plugins “Send a Test Email” Session Transcripts (Step 3 in the test email dialogue) and especially the Connectivity Test to understand the error, but I tend to actually find the solution outside of the plugin. Anyhow, thanks again for sharing from your experience as well! It all helps! Onward! ??

Hi @patjk,

We’re you ever able to resolve this? I’ve had a similar issue on only one (of many) sites using Postman SMTP so can’t quite tell yet if it has something to do with Postman or the SMTP server, etc.

If you were able to resolve it (and willing/able to share), what helped?

Thanks for posting to get the conversation started! ??

Hi @ipsofact – were you ever able to resolve this?

Thanks for writing whenever able!

Hi AJ – did you ever hear back from the developer(s) or were you able to contribute to the code to fix the items you mentioned above? Would love to see CSS improvements as well! Thanks for asking/getting it started ????

Hi again, Rogier and vikkiwordpress – WooCommerce 3.0 was released today and the relase notes included the following:

We’ve removed the feature where old orders get access to new downloads on product edit. Looping (potentially) thousands of orders to do this update was too much of a performance burden for some stores and this also could lead to unexpected behaviour. After this update we do however update edited downloads, so editing a file will not prevent purchasers from downloading it.

I’m not sure that last section pertains to our situation(s) yet but it may be worth exploring.

Thanks, again, Rogier for replying as/whenever able! ??

Hi guys,

Rogier – somehow I missed the notification of your initial reply…7 months ago! Please forgive me!

Answers to your question:
1. Do you have hotlink protection active on the server? –?we do not have anything extra setup regarding hotlink protection on the server. WooCommerce, however, doesn’t let us just load the link to the file, so I believe the WooCommerce plugin does “protect” the files.
2. If you load the file directly with the https link in your browser, does that also give the error, or only if you click on the link in the website? –?similar answer here: WooCommerce doesn’t let even the Admin load the link to the file. It is “protected” behind the /wp-content/uploads/woocommerce_uploads/ folder.
3. Do you also have this issue when the redirect is disabled in settings/ssl? –?I did not test this.

Does that help at all?

Thanks for your constant work on this plugin, Rogier, and even more for your involvement here on the forums/support area –?it speaks so much to you and the quality of your work! ??

Thanks, again!

@mikejolley – Hi Mike – this would be helpful for us as well!

Chained Products has this ability (https://cl.ly/2f3q033h3t27) – is it crazy difficult to port a similar ability to Force Sells?

5 min later…

Okay – found mention of this on ideas.woocommerce.com from 2013 (https://ideas.woocommerce.com/forums/133476-woocommerce/suggestions/5193144-force-sells-with-variation-products)…only 7 votes. Hmm…

Well, it might never happen but it’s worth a shot! You guys totally know way more than I and while this topic is more specific to the Force Sells Extension, since Force Sells is identified as being developed by the WooCommerce team I am taking the risk to post here (with no expectation to reply).

I know you have a million other things to do with way more priority than this – thanks so much for basically changing the world (almost!) with WooCommerce! ??

Seriously, thanks, Mike. Amazing what one guy can do (or at least start).

Hello again,

Just a quick update that this turned out to be more complicated that I thought at first! All the previous “Download Links” that were emailed to the Customers no longer worked when I manually replaced https:// with https:// in the File URL of a Downloadable Product.

Would still appreciate your reply/any ideas but for now I had to deactivate (via the force-deactivate.php method) and set the site as if it hadn’t been touched by Really Simple SSL at all.

Perhaps there’s a way and I will learn it soon (would love that!) but if not, we’re okay as it is, I think for now.

Thanks again, Rogier!