Secret Agency

Ah gotcha, thanks!

Hi @jarryd-long ,

Thanks for the prompt reply!

Just to make sure I am understanding you, are you saying that no matter what, whether a membership has been set up to have a trial period or not, a trial will be created in Stripe? And even though the first payment is billed right away and shown in the payments tab, the $0 invoices (which don’t actually get sent to the customer as far as I know) are just an artifact of the way the API calls are made?

Thanks again!

Thanks @misulicus for the prompt reply!

The site uses Single Music for digital delivery. It’s a bit complicated, but they integrate with Shopify and when a user checks out, they send an email with a link to download the music.

I would be open to other delivery options such as the user getting a password they can use to download their items from a password protected page , or just being redirected to a download page after the sale.

Now that I think about it, it seems like EDD might not be necessary for either of the above. But, I tried EDD in the past and recall it being useful so thought it might be the way to go.

Anyway, thanks again for your help!

Yeah some recent update killed it

This has been a problem for me as well. I think it is to do with WP Total Cache on my site. I have found that by not caching pages with products on them that maybe does the trick? I have yet to find the perfect solution to keep it from occurring in the first place but clearing the cache in the browser, WP Total Cache and SHopWP even if caching is not enabled seems to help.

This is an issue that only started occurring with the new version of the plugin. It has been painful to deal with because it will crop up when the cache has expired and you may not be aware of it. Sometimes two separate tabs of the same page will show different results –?one with products and the other with the error –?if the browser has cached one of the tabs. So even if it seems fixed, it may not be.

I think this is the number one issue with this plugin right now as it is a show-stopping bug that is likely costing users customers and money.

THat’s exactly what I need. Thanks!

Hey Andrew,

Thanks so much for the prompt replies!

I’m looking to limit the quantity of specific products only, if possible.

Thanks again!

I see. That is the expected behavior of the filter.

`select_first_variant?

Allows for selecting the first product variant on page load. This will only work with products that have one “option” to choose from. For example, it will work with a product that provides a color option, but not with products that provide color and size.

Possible values
true
false Default`

OK so, feature request! I’ll write it as a user story.

“Select_Only_Single_Variants”

As a shop owner, I would like customers to be able to quickly add products to their carts with only a single click when those products have variants with only one choice. For example, if I sell a hat that only comes in one color and one size, then clicking “add to cart” should add it to the cart immediately. However, if I sell a t-shirt in multiple sizes, the user should still have to choose a size to prevent them from anciently choosing the wrong size.

Thanks again!

Actually, it looks like it did work. It is just that the variants I have for one-size-fits-all say “undefined” for some reason. But it is choosing that correctly.

I wonder if there is a way to have it only choose a default when there is only one choice though? Because it is choosing a default when there are multiple variants, which is not ideal since someone could add a medium when they want a small, for example.

In any case, thanks again- this is a great start.

Wow thanks Andrew for the quick reply and code! Unfortunately, that actually did kind of the opposite of what I am looking for. That selected a default variant when there was more than one – say Small out of Small, Medium and Large. I am looking for a way to select the only possible variant when thee is only one to choose from. So for example, say I have a hat that only comes in one size – “one size fits all” and one color – black. I want the user to be able to just hit add to cart and have it select the size and color automatically since those variants each only have one choice. Sorry if this was not clear. And thanks again for the prompt reply. 5 stars!

I am also experiencing this issue. Turning off caching in the plugin itself originally fixed it. Then today I saved a change in the settings and it broke again. Updating to the latest version of the plugin did not resolve it, nor did turning off my caching plugin.

Looking in the console under network I see there are no attempts to connect to [my domain].myshopify.com and I get the same 404 as the comment above when trying to load [mydomain.tld]/wp-json/shopwp/v1/query/products.

Hey thanks for the reply. So I am getting ready to migrate the db- but just want to make sure I get all the right tables. Do they all start with PMPRO_ or are there any others I should be aware of? For example, I used the register helper add-on to add extra custom fields. Where would those be found?

Thanks!

Hey thanks for the quick reply!

Yeah, I don’t think it is a good practice to have production code change without the version number changing.

At best it sews confusion. And when security plugins complain about the code changes, people might assume they have been hacked. The changes looked benign to me but a lot of folks won’t know how to tell the difference.

Just a thought – not sure if it’s a good one or not – but, what if you had some sort of public beta option? You could let users opt in and maybe call it something less scary than beta- like “fast track” with the promise that the updates will have been tested before release so they shouldn’t compromise security or break sites. The selling point would be that they provide the latest features, only faster. Then you can gather feedback before pushing to production.

I am not sure how it would work in practice but you would probably need to use a parallel updating mechanism like via GitHub or something a la https://code.tutsplus.com/tutorials/distributing-your-plugins-in-github-with-automatic-updates–wp-34817

On second thought, a free plugin is already kind of a public beta, isn’t it? I mean, if it is free, who are users to complain about frequent updates? Maybe just ignore those complaints?

Anyway, thanks for clarifying and again for the quick reply.

Also very much appreciate the help!

As for my images, I’ll open a separate issue so that people can search for that.