jon

As OP said, this plugin is conflicting with other plugins within the plugin list page (wp-admin/plugins.php). It is somehow injecting it’s settings link to every other plugin within the list.

https://imgur.com/6sCQsxd

I am also experiencing issues with this. Only exif data captured is author, date and copyright. No camera data is captured. This is testing with jpg and webp (using code snippet from previous support thread).

Onboarding was easy enough. However, ability to exclude categories was missing. Products, prices (not including quantity discounts), descriptions and imagery seemed to be exported just fine.

Not directly an issue with this plugin but Google’s merchant center is unable to replicate our shipping table rates (some individual products have shipping included, but most are based on quantity and depending on whether we can deliver ourselves, free above a certain total cart amount) so ultimately this was a worthless exercise.

This would definitely be a useful feature – a lot of spam registrations use domain formats like: subsubdomain.subdomain.mailguard.space. Just blocking *.mailguard.space would be more effective as subdomains and sub-subdomains rarely used again.

• This reply was modified 1 year, 8 months ago by jon.

For our frontend adjustments, I copied woocommerce/archive-product.php to yourtheme/woocommerce/taxonomy-pwb-brand.php.

@paddyuboot install Advanced Custom Fields, create a field group for
the second Brands taxonomy. Display this field in your template by following the ACF documentation.

Never mind. I’ve resorted to editing the plugin directly. Whilst I am pleased to see some presentation moved to overridable template files, too much is still in the class files.

I personally appreciate that this is a free plugin but for commercial applications there are some aspects that I’d like to see improved, with a view to eventually paying for a pro version. I think you deserve it.

• This reply was modified 2 years, 4 months ago by jon.

Hi, @olafatorwp

Could you share a bit more on your methods for solving this with ACF fields?

Thanks!

Thank you for the confirmation. We’ve been running this plugin for a month now so I assume Paypal’s email is just a generic email and not specifically because they’ve spotted non-3DS transactions from us.

Having disabled direct credit card payments for now, I am disappointed to see the issue occurs with the black Debit or Credit Card button for Paypal Checkout too. This really needs to be addressed asap – cancelled orders are piling up.

I think we’re getting the same issue. Submitting a credit card payment through the checkout page results in a successful payment but the checkout page does not redirect to the order received page, being stuck on a an infinite loading wheel of death. Manually refreshing the page clears the cart as expected following a successful payment.

Refunding a payment via backend > Woocommerce > Orders > Refund x.xx via Paypal Card Processing also results in a long ajax loading wheel but does eventually complete – this is with the 60 second http request timeout hack from @bakertronics.

We have all IPN ip addresses whitelisted on our server. There just seems to be a terrible communication issue here with Paypal.

I’ll need a couple of days to set up a clone whilst removing customer personal data – I’ll send you the info next week.

Thank you.

Whilst I can’t help with any of your issues, I’m interested in the solution you came up with to change the order of the payment options (I have a similar thread open: https://www.ads-software.com/support/topic/checkout-page-payment-options-order/). I’m currently of the mind to change the order with javascript once the credit card iframe has been loaded from Paypal’s servers.

That’s what I’m wondering too – on the checkout page load, the only two visible payment options are Paypal and Pay over the Phone. The iframe takes a second to load after that. I think it needs a container that exists in the DOM that it loads in to, to ensure the order is adhered to – currently it appears to just slot itself in at the end.

If we could at least get that fixed, it’d be better. Thanks for your continued attention to this problem.

‘Credit card’ refers to ‘Paypal Card Processing’, which is defined as ‘Pay with Credit Card’ in the Title field.

Two screenshots:

Woocommerce > Settings > Payments
Checkout Page