CMProduct
Forum Replies Created
-
Excellent, that is great to hear. Thank you for the great plugin!
EDIT: I will leave a review once I have used it some more – just started.
- This reply was modified 1 year, 9 months ago by CMProduct. Reason: To update about review
Wow that is such great news :).
Would it also be possible to allow the customer to choose the template on the gift card product page (like a variation)? So if they want the card to be for a happy birthday or anniversary or congratulations…like you can at a Walmart – they have many styles of gift cards that you can choose from when buying it. Can the customer do that on the product page?
Thanks!
Hi @mewz
Thank you very much for the quick response it’s greatly appreciated.
I have been working on my project and didn’t really have much time to explore this yet. But I have now been able to and it seems it might do what I need it to. Unfortunately, I was struggling with seeing it really work without purchasing (I wasn’t seeing the available amount changing on the product page) and was thinking I just couldn’t get it to work. But I did see you explained in the description the reason is because it is free that we won’t see it. So I took the risk and purchased it. And glad I did, it’s actually more flexible than I thought and believe it will do what I need.
Unfortunately though I did have to contact you with a question and a possible request – hope you don’t mind.
In any case, I’ll mark this thread solved because it is no longer relevant (you’re right, linking by attributes is pretty powerful). But I do thank you again for the quick response, it gave me more confidence in purchasing the paid version.
Forum: Plugins
In reply to: [WooCommerce PayPal Payments] Thousands of empty sessions rowsThank you for that code info. I actually found that I needed to place another forward bracket ( “{” ) after the first one, otherwise it was saying there was an error a few rows down when editing using cPanel file editor. Other than that, it was fine.
So I have been checking the table over the past few days and it seems the “ppcp_fraudnet_session_id” parts of the entry are gone, so that code worked to stop that. Question: why if I have FraudNet disabled that it doesn’t do what the code does that you just gave me? If I have FraudNet disabled in admin, it should disable it in the same way.
But, it does seem like something else may indeed be the culprit – as you say you couldn’t replicate it and maybe it is something with my site because it still seems to be getting spammed with empty cart contents, but I don’t think as much – which is weird.
I’m going to be keeping an eye on the session_ID numbers instead of the amount of rows because now 30 days have past (since I changed the cart session length) so sessions are now also being removed (not just added).
I’ll report back with more findings. But thanks for that code so far, it might be helping to narrow this down.
Forum: Plugins
In reply to: [WooCommerce PayPal Payments] Thousands of empty sessions rowsHello @inpsydekrystian
Any updates on this?
Forum: Plugins
In reply to: [WooCommerce PayPal Payments] Thousands of empty sessions rowsThank you for forwarding this issue. My database as I had mentioned will do, just keeps growing with the exact same rows as I posted in the OP. It is now up to 25k rows and 45mb: https://imgur.com/11yinmn – I’m on track to hit 50mb and 30k rows in 7 days as I mentioned previously. That is not good – that is larger than the rest of my database. Out of all those rows I probably have 15 actual carts. I can tell through a table (CSV) export.
I also have another site running (for 6 weeks now) with the latest WooCommere but this plugin is not installed. That one has 4 rows and each one is a legit cart. So something with this PayPal plugin is causing the “ppcp_fraudnet_session_id” spam.
So again it is much appreciated that this will be investigated. Oh and BTW I’m using:
WordPress: 6.4.3
WooCommerce: 8.6.1
WooCommerce PayPal Payments: 2.5.4
I should also mention I have had “FraudNet” unchecked in the settings.Thank you.
Forum: Plugins
In reply to: [WooCommerce PayPal Payments] Thousands of empty sessions rowsThing is, the records are empty as I posted. There is no cart data. Meaning, no one added anything to the cart – yet it’s still spamming my DB table. If it went with a cart, that would make sense.
Just since I posted this issue 2.5 days ago, that table has doubled and is now 27mb with over 14k rows: https://imgur.com/a/4SftBxh – give it a week and it will be 50mb and 30k rows. A month probably over 500mb and 300k rows. I modified my cart expiration so it expires after 30 days, not the standard 48 hours, so this will build for 30 days. And I A) can’t just delete them because then I clear everyone’s carts & B) that is just insane anyway – I don’t have time for that.
It says right in it ppcp and is related to paypal and this plugin. I had no issues until I added/enabled this plugin. I found the GitHub link here of someone else reporting the exact same issue: https://github.com/woocommerce/woocommerce-paypal-payments/issues/1564 – you and the “Niklas” person are saying disabling this plugin would still cause this issue? So WooCommerce now has FraudNet integrated automatically?
Is there a way to properly stop it from simply recording empty logs of this? It will make my database bloated for no reason and make it tougher to backup (and restore if necessary).
Thank you for your time.
Hm I see. Yeah I put [esi blockname] and that recents element/block doesn’t seem to fully function afterwards – so I guess it’s not compatible as you say. And unfortunately, I have enabled AJAX on that block (it has that option).
I’ll try reaching out to the theme dev and see if maybe they can help somehow to make the block more compatible with caching.
Well thank you very much for your time looking into this it is very appreciated.
Spain? If so, I have unblocked it. I appreciate your time on this.
I geoblock using Cloudflare, but I can temporarily unblock an IP or country. Or if you’d prefer you could use a VPN? If you use a VPN you’d have to choose a server in the US. Or if you’re in the US then you’re good to go.
https://pastebin.com/Nzg4LGg9 – using pastebin because I’ve posted my domain in the past and have had quite a few extra bots hit my site before.
Sorry I’m a stickler for security and not having IPs and such just sent to some system, I hope you understand. I have created a pastebin with my server IP, API keys and domain omitted, everything else is as the report would have sent.
Thank you for your time
Hi @qtwrk
Thank you for your quick response! And you’re good, that was the problem. I remember I had added that vary cookie because of another issue due to crawling but didn’t realize that broke the crawler (in this way). I didn’t notice after I added that vary that the crawler broke – an oversight on my part – my apologies, I should have noticed that.
While I have you here, could you help with one other thing sort of related? The vary cookie I had setup was for a recently viewed product block. I noticed that when the page is crawled, that block (which is in the footer of every page) doesn’t show the product image – it shows a data:image/jpg;base64 instead (and I tried turning off lazy load and responsive placeholder). This causes just a whitespace – which is why I did the cache vary cookie thinking this would work – but I won’t do that if it messes with the crawler. So maybe this is where ESI comes in? I put [esi blockname] but it kind of breaks the block and what does work, the image is still a base64 (white space only). I also tried a cookie exclude (in litespeed cache > excludes) and that just causes the whole page to not cache (says no-cache, esi=on in header) – so I guess that won’t work either? Any way to crawl/cache the pages with that block on it but don’t cache that block?
Thank you again in advance for your time.
Hello @inpsydekrystian
Thank you for your assistance. It seems you were partially correct, the WPBakery was a part of the issue. I guess I was putting the original page checkout “blocks” into a hidden row instead of simply deleting them. If I put just the [woocommerce_checkout] into a WPBakery Page Builder “row” then the checkout (and cart by doing the same thing with [woocommerce_cart]) now work correctly :). The buttons show correctly and the form for the credit card fields work correctly. And it also all works fine with WPBakery Page Builder.
So, my apologies for making such a long-winded topic on something that seems was my own doing. But I very much appreciate your time and assistance in any case, it was a help.
Thanks again!
Hello @inpsydekrystian
So I did more testing (disabled and checked some things) but still no luck. So I decided to just create a brand new WooCommerce/PayPal install.
Anyway, I have 3 plugins on this fresh installation (on WordPress 6.4.3):
-WooCommerce (8.5.2)
-WooCommerce PayPal Payments (2.5.3)
-WPBakery Page Builder (7.4) – I use this to disable Gutenberg so I can modify the pages for classic cart/checkout vs block cart/checkout
That is it. I have not installed anything else. I also want to point out, I have had a PayPal Business account for many years now and have used all these features no problem with Magento + PayPal – so my PayPal account is not “limited” or anything. So through my extensive testing, I have found these have to be bugs with the plugin – not my site.
Just for reference, these are all the smart buttons I am looking for (plus Google Pay/Apple Pay which don’t show here) – and these are all showing on the “Classic Cart/Checkout”:
https://woo.com/document/woocommerce-paypal-payments/#customer-experience
Here are the following issues (per theme/per checkout style, because it seems it matters…):
TWENTYTWENTYFOUR THEME (BLOCK CHECKOUT)
A1) Disabling “Express checkout” for PayPal causes this error: “There are no payment methods available. This may be an error on our side. Please contact us if you need any help placing your order.” Paypal completely disables now.
A2) The buttons do show with “Express Checkout” enabled (except for the debit/credit card form button – this still does not show – and I DO have the “Standard Card Button” enabled).
TWENTYTWENTYFOUR THEME (CLASSIC CHECKOUT)
B1) The “Advanced Card Processing” form will not show; it will show the radio button but it does nothing.
B2) Disabling “Express checkout” for PayPal does not cause paypal to be completely disabled – as long as “Classic Checkout” is enabled in PayPal.
B3) Enabling “Express Checkout” does nothing.
B4) The buttons show ONLY if I have “Express Checkout” enabled. But because “Express Checkout” does not work on “Classic Checkout” there are no buttons only radio selection. Why are the buttons not showing if the “Express Checkout” is disabled? They used to show no problem.
STOREFRONT THEME (BLOCK CHECKOUT)
C1) Same as A1
C2) Same as A2
STOREFRONT THEME (CLASSIC CHECKOUT)
D1) With “Express Checkout” disabled, the “Advanced Card Processing” button still will not show (and I DO have the “Standard Card Button” enabled). It will start to show the radio button while checkout is loading but once page is fully loaded it disappears. Same as before as shown in my video clip.
D2) Same as B2
D3) Same as B3
D4) Same as B4
….
I could probably keep going but this is turning into a mess (+ hours of testing) and a very long post. I think the big issue is stemming from the conversion that WordPress is doing converting everything over to “Blocks”. Because it seems some things work with the “block checkout” but other things don’t/some work with the classic checkout, some don’t. And my live site theme does not support any “block” cart/checkout yet – so I need all to work on the classic cart/checkout.
Overall, can you please do a test yourself? All testing was done with base plugins and up to date (as noted in the beginning). I’d really like to know what you find when you test it on your end.
Thank you for your time, hopefully this can be fixed ASAP because I really need PayPal to work properly (with the “Classic Cart/Classic Checkout”).Thank you for your prompt response.
So it seems as you are mentioning, it may not be the plugin. Figures – that means more digging/debugging – but knowing that it could be a JavaScript conflict may help. I will have to do some more testing when the traffic is low on the site to run more tests. I will repost back here with any new information and may open a ticket if my tests result non-conclusive.