Global product page settings

Hi @artsoulbrother

Thanks for contacting us. The way it should work is as long as the product doesn’t have any PayPal settings saved, then the global settings will be used. Once you make a product specific PayPal settings change, then those override the global settings.

Are you saying you’re seeing different behavior than that?

Kind Regards

Heya thanks for getting back.

What you described is the behavior I’m seeing now. The previous versions of the plugin ( past 6 months ) the global behavior overwrote the product behavior ( that has been the case for me ).

I should have been more intuitive but got used to things and this last update prioritized product behavior above global.

Ideally, an option to disable product priority would be pretty sweet ( I’ll buy the plug ) but if you have a function in mind that can do this at the moment I would appreciate it.

Thanks

Hi @artsoulbrother

Thanks for the clarification. Yes, when we found that the global setting was overriding the product level we fixed it as we considered that a bug in the plugin. In our view, the product level should always override the global setting as it allows a merchant to fine tune a specific product’s configurations.

Let me take a look at the available filters, there may be a way to achieve this using a simple code snippet where the global settings is used. Do all of your products have PayPal enabled? What about the Pay Later button and Pay Later messaging?

Kind Regards

Ah right, so I’m not dreaming things up ??

Yes, all the products have all available features on, both Stripe and PayPal plugs.

It would be pretty awesome if it’s possible to disable everything on product level, including JS dependencies. I’m trying to fine-tune things, hence minimalizing.

Ah right, so I’m not dreaming things up

There is one more possibility that could cause that. If you edited a product and made a PayPal Settings change then that adds an entry to the database for that product. If you then made copies of that product to make your other products, that means you would have overrides for each of your products.

You could delete all meta keys in the postmeta table with values equal to woocommerce_ppcp_settings. That would force the PayPal plugin to use the global settings rather than the product specific setting.

Kind Regards,

Ah nice, ya I was looking at that entry and was wondering what the outcome of removal would look like.

What about these other entries? : “_stripe_afterpay_options”, “_stripe_googlepay_options”, “_stripe_applepay_options”, “_ppcp_options”, “_stripe_affirm_options”

And just to be clear, you’re talking straight up total annihilation : “DELETE FROM postmeta WHERE meta_key = ‘woocommerce_ppcp_settings'” ?

Again, thanks for all the help!

What about these other entries? : “_stripe_afterpay_options”, “_stripe_googlepay_options”, “_stripe_applepay_options”, “_stripe_affirm_options”

The Stripe prefixed keys are for the Stripe plugin and removing those would have the same affect. The global settings would be used since there is no product specific table entry.

The key _ppcp_options is not one that’s used by our PayPal plugin. Can you provide an example of what it’s table value looks like? It might be a key that another PayPal plugin used (if you were using another PayPal plugin at some point).

And just to be clear, you’re talking straight up total annihilation : “DELETE FROM postmeta WHERE meta_key = ‘woocommerce_ppcp_settings’” ?

Yes. You can simulate a query using phpmyadmin and that will show you the number of affected rows so you can be confident that the correct entries are being deleted.

Kind Regards,